Skills

Only the description of each skill loads every session; the body loads when a task needs it.

adopt

Use BEFORE editing AGENTS.md / CLAUDE.md to shrink them or reduce per-session context, and when moving an existing project onto agent-kit — measure, map every section, move procedures into skills, area rules into folder CLAUDE.md files and facts into .knowledge/, one section at a time. Triggers: "adopt agent-kit", "slim AGENTS.md", "too many tokens", context over budget.

• Origin: plugin (every project)

commit

Use BEFORE any git commit — whenever the user says "commit", "commit message", "save this work", or a spec/feature is done. Runs preflight, reviews what goes in, writes a Conventional Commit message (type(scope) subject, English), validates it with commitlint, then commits within the project's git flow (or hands the user the exact command when git is read-only).

• Origin: plugin (every project)

decide

Record an architecture or design decision (ADR) in the right scope — project decisions in .knowledge/decisions, cross-project ones in global meta. Use when a choice with lasting impact is made or asked about ("let's go with…", "we decided…", "should we use X or Y" once settled), or when an earlier decision is replaced.

• Origin: plugin (every project)

feature

Use BEFORE making any small code change — a fix, a tweak, a small UI addition (≤3 files, no schema, permission or money change). Opens a work/features file with goal, tasks and evidence so the work survives session restarts. Triggers: "fix", "tweak", "small change", "change X to Y", "add X to the page". Bigger or riskier work → spec skill.

• Origin: plugin (every project)

knowledge

Read and write the scoped knowledge base — business concepts, environment facts, stack conventions, UI/UX rules, cross-project meta rules. Use before working in an unfamiliar area ("how do we…", "what is…"), and whenever a lasting fact, rule or convention comes up that a future session must know ("remember…", "from now on…", "the rule is…").

• Origin: plugin (every project)

preflight

Pre-merge check of the current branch — migrations to apply or wrongly edited, new env vars, new dependencies, possible secrets, debug leftovers, grants to anon/authenticated, undocumented scripts, and (SDD + TDD) changed logic without a test. Use before a PR or merge, when a spec/feature is closing, or when the user asks "what do I need to do to ship this?".

• Origin: plugin (every project)

retro

Retrospective that turns experience into durable setup — repeated corrections become knowledge or hook rules, reused scratch scripts get promoted, unused things get pruned. Use when the user says "retro", "what did we learn", "improve the setup", after finishing a spec, or about once a month.

• Origin: plugin (every project)

scripts

Decide, find, build, document, test and run scripts so they are reused instead of rewritten. Use before writing ANY script or helper program (test helpers, data checks, generators, "write a script that…"), before re-creating an earlier ad-hoc script, and when keeping or documenting scripts. Searches existing scripts and skills first.

• Origin: plugin (every project)

spec

Spec-driven lane (SDD × TDD) for big or risky work — a new module or page set, schema/RPC changes, permissions, money, anything over ~3 files. Opens a change (proposal + delta specs), gets approval, implements test-first, verifies every scenario and merges into the living specs. Use when the user says "spec", "plan this", "new module", or the work exceeds the fast-track lane.

• Origin: plugin (every project)
• Files: references/notation.md, templates/delta.md, templates/plan.md, templates/proposal.md, templates/tasks.md

start

Guided kickoff for a new project or a big new piece of work — asks plain questions (what, for whom, which pages or features, look and feel, content) and turns the answers into the first spec. Use when the user says "start", "I want to build…", "new site/app/project", or when work/ is empty and the request is open-ended.

• Origin: plugin (every project)

tdd

Use BEFORE writing or changing logic when the user asks for TDD, "test first" or tests, or the project method is SDD + TDD. Red → green → refactor one behaviour at a time, test cases chosen with ZOMBIES, related tests run compactly with tdd.mjs. Also when preflight reports logic without tests.

• Origin: plugin (every project)

stack-nuxt-content-site

Use BEFORE adding or changing pages, texts, navigation, colours, images or components in this Nuxt Content site (content/*.md, app/, nuxt.config.ts). Conventions for Markdown pages, frontmatter, ordering, styling tokens, MDC components, SEO and the static build.

• Origin: template (installed in .claude/skills/ of projects on that stack)

stack-nuxt-supabase

Use BEFORE adding or changing pages, components, server routes (apps/*/server/api), auth, Zod schemas, SQL migrations, RPCs or test data in the Nuxt 4 + shadcn-vue + Tailwind v4 + Supabase monorepo (apps/web, apps/app, apps/docs, packages/ui, packages/shared). Conventions and patterns, details in references/.

• Origin: template (installed in .claude/skills/ of projects on that stack)
• Files: references/bff.md, references/migrations.md, references/monorepo.md, references/test-data.md, references/ui.md