npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

seasoned-skills

v0.0.7

Published

Seasoned's skills to orchestrate the full product cycle with AI agents

Readme

seasoned-skills

Seasoned's skills to orchestrate the full product cycle with AI agents.

This package carries one complete way of working, run inside Claude Code, Anthropic's coding agent: how an idea becomes a shaped project (one written down and thought through before any build starts), how AI agents build it end to end, with everything that needs taste running on Fable, the strongest Claude model, and how the lessons learned along the way are kept. A project adopts it by installing the package and answering an interview once. From then on, everything the workflow needs inside the project is generated from the installed version: the standing instructions, the skills, the small supporting tools. The project commits only its configuration and its own content, and staying current means upgrading a version.

We built it because we were maintaining the same way of working in three repositories, by hand. Every lesson was learned once but taught to only one project, and the copies quietly drifted apart. Now a lesson written once reaches every project on its next upgrade, a new project costs an install instead of an afternoon of copying and pruning, and differences between projects are configuration, never forks.

Where this is going

We are building toward one thing: AI agents doing all the work of product development. Pulling requirements out of meetings, issues, user feedback, and the running product's behavior. Shaping, building, releasing, and watching what ships. Today we still bring the ideas and rule on the quality. Real autonomy means agents decide what to shape and shape it themselves, then decide what ships, to which audience, and how fast the rollout goes. Feedback from the outside world — the running product observed, users talking to the AI itself — starts the next shaping session on its own. Two doors stay open to us for good: anyone can start a shaping session, and every shaping document waits for human review before the build starts. But coming up with the work stops being something only we do.

Find your way in

This repository

This repository is consumer number zero: the workflow it ships is installed here from the package itself, so the repo works under the very rules it distributes. It holds itself to the same adopter's bar the docs state, in the form that applies to a command-line package: its own CI runs both test tiers as required checks.

License

MIT.