The skills I use
These are the agent skills I use while building real products. I keep optimizing them as better practices show up. Each one is a SKILL.md file that teaches a coding agent a repeatable workflow. Install the package to use them, or read the source and write your own.
Star the repo to follow along as these skills get better.
Star on GitHubInstall the npm package
Add the package, then sync its skills into your agent.
@aayushchugh/skills
npm install @aayushchugh/skillsnpx skills experimental_sync
All skills
Cases to runUse when asked for test cases, QA coverage, or how to test a flow by hand. Not for writing the test code or a security audit.Go or stopUse when asked if a change is ready to ship, or for a go or no-go. Not for deploying.No slopUse when writing or changing code, including a test that was asked for. Not for docs, a review, or a design.One shapeUse when asked to refactor, clean up, or standardize a repo. Not for a security audit or a single pull request.Open doorsUse when asked for a security audit or a pentest-readiness review. Not for a live attack or a normal code review.Plain paperUse when asked for a PRD, spec, flow, API reference, runbook, guide, or README. Not for code or a system design.Red penUse when asked to review a diff, a pull request, or a change. Not for a security audit, a refactor, or writing tests.The causeUse when asked to diagnose, debug, or find why something fails. Not for writing the fix or the test.The mapUse when asked for a system design, an architecture review, or a scale or performance improvement. Not for writing code or a PRD.What's nextUse when asked what's pending, what's next, or the status of the current work. Not for starting the work or changing the plan.Which skillUse when a request could match more than one skill, or needs several skills in a row.