Agent Skills

git-workflow-and-versioning

Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.

idea-refine

Use when an idea is vague, alternatives need expanding, assumptions need stress-testing, or the user wants to refine an idea before committing to a plan.

incremental-implementation

Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

interview-me

Use when a request is underspecified, important requirements are ambiguous, or the user asks to be interviewed or grilled before planning or implementation.

observability-and-instrumentation

Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

performance-optimization

Use when an application has performance requirements, regressions, slow pages or queries, poor Core Web Vitals, N+1 patterns, or measured bottlenecks that need optimization.

planning-and-task-breakdown

Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

security-and-hardening

Use when code handles untrusted input, authentication, sessions, sensitive data, external integrations, dependency vulnerabilities, or needs a security review against common attack classes.

shipping-and-launch

Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

source-driven-development

Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

spec-driven-development

Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.

test-driven-development

Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

using-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. This is the meta-skill that governs how all other skills are discovered and invoked.