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.

Install the npm package

Add the package, then sync its skills into your agent.

@aayushchugh/skills

npm install @aayushchugh/skills
npx skills experimental_sync

All skills

Cases to runWrite a small, risk-based set of test cases from a spec, diff, or bug report. Use when the user asks for test cases or QA coverage. Do not write test code or audit security.Go or stopDecide if a change is ready to ship, with a go or no-go, what to watch, and how to roll back. Use when the user asks for a release check. Do not deploy.No slopWrite the smallest readable code that reuses existing code, installed utilities, and repo patterns, and fixes bugs at the root cause. Use when implementing, fixing, or reviewing code. Do not use for docs.One shapeAudit a repo for duplication, divergent flows, dead code, over-engineering, waste, and standards drift, then apply approved steps. Use when the user asks to refactor or clean up a codebase. Do not audit security.Open doorsReview application code, APIs, dependencies, secrets, and deploy config for injection, web attacks, and DDoS controls. Use when the user asks for a security audit. Never attack a live target.Plain paperWrite a spec or other documentation from the request, the code, and relevant sources. Use when the user asks for a PRD, spec, flow, API reference, runbook, guide, or README. Do not change code.Red penReview a diff or pull request for bugs, regressions, broken callers, missing tests, and unmet requirements. Use when the user asks for a code review. Do not audit security, refactor, or write tests.The causeFind a bug's root cause from the report, the code path, and the evidence. Use when the user asks to diagnose or debug a failure. Do not write the fix or the regression test.The mapMap, propose, or improve a system's design like a senior engineer, grounding the recommendation in real usage and activity. Use when the user asks for a system design, architecture review, or scale or performance improvement. Do not write code.Which skillPick and run the right skill, or a chain of skills, for a request. Use when unsure which skill applies or when a task spans several steps.