The catalog

24 skills, one per job

Each skill is a structured workflow - steps, verification gates, and anti-rationalization tables - not a loose prompt. Filter by phase or search by what you’re doing.

npx skills add addyosmani/agent-skills
/

Meta

using-agent-skills

Maps incoming work to the right skill and defines shared operating rules.

Starting a session or deciding which skill applies.
Define

interview-me

One-question-at-a-time interview that extracts what you actually want.

The ask is underspecified, or you invoke "interview me" / "grill me".
Define

idea-refine

Structured divergent/convergent thinking to sharpen a vague concept.

You have a rough idea that needs exploration and stress-testing.
Define /spec

spec-driven-development

Write a PRD covering objectives, structure, style, testing and boundaries - before code.

Starting a new project, feature, or significant change.
Plan /plan

planning-and-task-breakdown

Decompose specs into small, verifiable tasks with acceptance criteria and ordering.

You have a spec and need implementable units.
Build /build

incremental-implementation

Thin vertical slices - implement, test, verify, commit. Rollback-friendly changes.

Any change touching more than one file.
Build /test

test-driven-development

Red-Green-Refactor, the test pyramid, DAMP over DRY, the Beyoncé Rule.

Implementing logic, fixing bugs, or changing behavior.
Build

context-engineering

Feed agents the right information at the right time - rules files, context packing, MCP.

Starting a session, switching tasks, or when output quality drops.
Build

source-driven-development

Ground every framework decision in official docs - verify, cite, flag the unverified.

You want authoritative, source-cited code for any framework or library.
Build

doubt-driven-development

Adversarial fresh-context review of every non-trivial decision, in-flight.

Stakes are high, code is unfamiliar, or verifying now beats debugging later.
Build

frontend-ui-engineering

Component architecture, design systems, state, responsive, WCAG 2.1 AA accessibility.

Building or modifying user-facing interfaces.
Build

api-and-interface-design

Contract-first design, Hyrum’s Law, the One-Version Rule, error semantics.

Designing APIs, module boundaries, or public interfaces.
Verify

browser-testing-with-devtools

Chrome DevTools MCP for live runtime data - DOM, console, network, profiling.

Building or debugging anything that runs in a browser.
Verify

debugging-and-error-recovery

Five-step triage: reproduce, localize, reduce, fix, guard. Stop-the-line rule.

Tests fail, builds break, or behavior is unexpected.
Review /review

code-review-and-quality

Five-axis review, ~100-line change sizing, severity labels, review-speed norms.

Before merging any change.
Review /code-simplify

code-simplification

Chesterton’s Fence, the Rule of 500 - cut complexity while preserving behavior.

Code works but is harder to read or maintain than it should be.
Review

security-and-hardening

OWASP Top 10 prevention, auth patterns, secrets, dependency auditing.

Handling user input, auth, data storage, or external integrations.
Review /webperf

performance-optimization

Measure-first - Core Web Vitals targets, profiling, bundle analysis, N+1 fixes.

Performance requirements exist or you suspect regressions.
Ship

git-workflow-and-versioning

Trunk-based development, atomic commits, ~100-line changes, commit-as-save-point.

Making any code change (always).
Ship

ci-cd-and-automation

Shift Left, Faster is Safer, feature flags, quality-gate pipelines.

Setting up or modifying build and deploy pipelines.
Ship

deprecation-and-migration

Code-as-liability mindset, compulsory vs advisory deprecation, zombie-code removal.

Removing old systems, migrating users, or sunsetting features.
Ship

documentation-and-adrs

Architecture Decision Records, API docs, inline standards - document the why.

Making architectural decisions, changing APIs, or shipping features.
Ship

observability-and-instrumentation

Structured logging, RED metrics, OpenTelemetry tracing, symptom-based alerting.

Adding telemetry, or shipping anything that runs in production.
Ship /ship

shipping-and-launch

Pre-launch checklists, feature-flag lifecycle, staged rollouts, rollback procedures.

Preparing to deploy to production.