Agents stop talking their way out of the work
Every skill ships a table of the exact excuses an agent makes to skip a step - “I’ll add tests later,” “this is too simple to spec” - each one rebutted inline. The shortcut is closed before it’s taken.
Encode the workflows, quality gates, and judgment senior engineers bring to production - packaged so your agent follows them consistently across every phase, from first idea to live deploy.
npx skills add addyosmani/agent-skills Eight slash commands map to the way software actually gets built. Each one activates the right skills for the moment - designing an API pulls in contract-first design, building UI pulls in accessibility, and so on.
/spec /plan /build /test /review /ship /spec Define what to build Spec before code /plan Plan how to build it Small, atomic tasks /build Build incrementally One slice at a time /test Prove it works Tests are proof /review Review before merge Improve code health /webperf Audit web performance Measure before you optimize /code-simplify Simplify the code Clarity over cleverness /ship Ship to production Faster is safer Not prompts - structured workflows with steps, checkpoints, and exit criteria. Reach for one directly, or let the meta-skill route you.
One-question-at-a-time interview that extracts what you actually want.
Write a PRD covering objectives, structure, style, testing and boundaries - before code.
Thin vertical slices - implement, test, verify, commit. Rollback-friendly changes.
Red-Green-Refactor, the test pyramid, DAMP over DRY, the Beyoncé Rule.
Adversarial fresh-context review of every non-trivial decision, in-flight.
Component architecture, design systems, state, responsive, WCAG 2.1 AA accessibility.
Five-axis review, ~100-line change sizing, severity labels, review-speed norms.
OWASP Top 10 prevention, auth patterns, secrets, dependency auditing.
Measure-first - Core Web Vitals targets, profiling, bundle analysis, N+1 fixes.
Pre-launch checklists, feature-flag lifecycle, staged rollouts, rollback procedures.
Left alone, agents skip specs, tests, and reviews - the practices that make software reliable. Four mechanisms hold the line.
Every skill ships a table of the exact excuses an agent makes to skip a step - “I’ll add tests later,” “this is too simple to spec” - each one rebutted inline. The shortcut is closed before it’s taken.
Each skill ends with exit criteria: tests passing, build output, real runtime data. Nothing is “done” on vibes. Verification is the whole point, not a nicety bolted on at the end.
/ship fans out to a code-reviewer, security-auditor, test-engineer and web-performance-auditor in parallel, then merges their findings into a single go / no-go decision.
A three-tier eval framework checks structure, routing (no two skills collide on the words users say), and real execution traces - some of it in CI. The catalog is held to its own standard.
/ship runs a pre-launch checklist and fans
out to four specialist personas in parallel. Each brings a different
perspective; their findings merge into one honest go / no-go.
Five-axis code review with a "would a staff engineer approve this?" standard.
Test strategy, coverage analysis, and the Prove-It pattern.
Vulnerability detection, threat modeling, and OWASP assessment.
Core Web Vitals audit with Quick/Deep modes and a metric-honesty rule. Run via /webperf.
One command installs all 24 skills into 70+ agents.
npx skills add addyosmani/agent-skills