itsvedantkumar/keystatic-passkeys

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

component-registry

Use before hand-writing any UI component in a React/Tailwind repo - pull a vetted, accessible primitive from a shadcn-compatible registry (npx shadcn add); hand-roll only what no registry has.

create-verification-skill

No scripted way to prove this repo's UI, CLI, or service actually works. Generates an executable .claude/verify.sh gate plus a verify-<app> skill and feature map. Use for 'add verification here'.

grill-me

Use when the user floats a plan, design or decision and wants it stress-tested, or says grill me, poke holes, what am I missing, or tear this apart. A round-based interview before code.

impeccable

Use when building or polishing any UI where visual quality matters: production-grade typography, motion, spacing, and brand-vs-product design modes beyond the stock frontend-design bar.

interrogate

Use before merging or shipping a change that only one reviewer (or none) has seen, especially auth, payments, or agent-written code, and on "tear this apart", "stress test this", "what am I missing".

swarm

Use when work splits into independent parts or approaches should be raced — 'in parallel', 'at once', 'all of these', 'try N ways'. Fans out N agents in ONE batched message, returns one table.

ui-iterate

Use after editing any UI file (.tsx/.jsx/.css/.vue/html) when a dev server runs: screenshot 375/768/1440px, self-critique hierarchy, spacing, states, fix and re-shoot before claiming done.

maintain-verification-skill

A repo's verification skill, feature map, or .claude/verify.sh gate has drifted from the app. Audits every feature from source and live, ships proven fixes. Use for 'audit the verify skill'.

principle-prove-it-works

Apply before declaring any task or fix done. Verify the real artifact — run it, read the actual value, inspect the diff — not a self-report, proxy, or 'it compiles.'

principle-type-system-discipline

Apply when designing types or a function signature in TypeScript, Rust, Go, or other statically-typed code. Make illegal states unrepresentable; never lie to the compiler.

technical-writing

Use when writing or reviewing docs, RFCs, READMEs, PR descriptions, or commit messages: applies Diátaxis structure, Google developer style, STE instruction rules, and Global English syntax.

unslop

Cut AI tells and add human voice to any text you write: docs, comments, commit messages, replies. Must always apply.