Skills from addyosmani/agent-skills: 25 agent skills

• api-and-interface-design — Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface.
• browser-testing-with-devtools — Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser.
• ci-cd-and-automation — Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines.
• code-review-and-quality — Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human.
• code-simplification — Simplifies code for clarity. Use when refactoring code for clarity without changing behavior.
• constraint-driven-development — Establishes a project's quality bar as a written contract and stops agents quietly lowering it.
• context-engineering — Optimizes agent context setup.
• debugging-and-error-recovery — Guides systematic root-cause debugging.
• deprecation-and-migration — Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another.
• documentation-and-adrs — Records decisions and documentation.
• doubt-driven-development — Subjects every non-trivial decision to a fresh-context adversarial review before it stands.
• frontend-ui-engineering — Builds production-quality, accessible, responsive user-facing UIs.
• git-workflow-and-versioning — Structures git workflow practices. Use when making any code change.
• idea-refine — Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking.
• incremental-implementation — Delivers changes incrementally in thin, verifiable slices.
• interview-me — Extracts what the user actually wants instead of what they think they should want.
• observability-and-instrumentation — Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting.
• performance-optimization — Optimizes application performance across frontend, backend, queries, and databases.
• planning-and-task-breakdown — Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks.
• security-and-hardening — Hardens code against vulnerabilities.
• shipping-and-launch — Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping.
• source-driven-development — Grounds every implementation decision in official documentation.
• spec-driven-development — Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet.
• test-driven-development — Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior.
• using-agent-skills — Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand.