agent-skills

Use when reviewing a blueprint (PRD, spec, implementation plan, design/architecture doc, or product scope and technical decisions from the current session) right after it is written or before implementation, to check whether its implementation cost is economical and rational. Not for reviewing already-implemented code.

Use when reviewing a blueprint (PRD, spec, implementation plan, design/architecture doc, or product scope and technical decisions from the current session) right after it is written or before implementation, to check whether its implementation cost is economical and rational. Not for reviewing already-implemented code.

Use for frontend architecture boundaries: code ownership, directory roles, file placement, import direction, UI/component extraction, API/data contracts, fetching/query, URL state, mappers/schemas/DTOs, hooks/stores, architecture docs, and tool enforcement. Also use before agent-initiated architecture-enforcement changes in lint, CI, import-boundary checks, or similar automation—even without a user request—and for small UI changes that may leak business rules or external data into lower-level code.

Use for frontend architecture boundaries: code ownership, directory roles, file placement, import direction, UI/component extraction, API/data contracts, fetching/query, URL state, mappers/schemas/DTOs, hooks/stores, architecture docs, and tool enforcement. Also use before agent-initiated architecture-enforcement changes in lint, CI, import-boundary checks, or similar automation—even without a user request—and for small UI changes that may leak business rules or external data into lower-level code.

Establish or reuse an isolated Git worktree for new work or a named branch, PR, tag, or commit. Use whenever the user asks to create or enter a worktree or separate Git checkout, wants parallel work without disturbing the current checkout, or another workflow requires Git checkout isolation.

Establish or reuse an isolated Git worktree for new work or a named branch, PR, tag, or commit. Use whenever the user asks to create or enter a worktree or separate Git checkout, wants parallel work without disturbing the current checkout, or another workflow requires Git checkout isolation.

Just Do It

Question

keep-it-down

Keep it down — use terse, clear, and action-first responses for the rest of the session. Remove filler and tangents, preserve technical precision, track multi-step progress, and end with one concrete next action. Use when the user wants compact communication; disable with `stop ssh` or `normal mode`.

Guardrails for writing, modifying, reviewing, or refactoring code. Use whenever a task involves code to clarify ambiguous requirements before implementation, avoid over-engineering and speculative abstractions, and keep changes minimal and scoped.

Guardrails for writing, modifying, reviewing, or refactoring code. Use whenever a task involves code to clarify ambiguous requirements before implementation, avoid over-engineering and speculative abstractions, and keep changes minimal and scoped.

Turn the current conversation into an idea document — no interview, just synthesis of what you've already discussed.

Use when React component or custom hook work may involve extracting hooks, changing hook responsibilities, or hiding dependencies behind custom hooks