Skills
The Kit ships 24 skills: 9 core workflow skills that carry a project from requirements to shipped feature, plus 15 supporting skills invoked as needed across design, review, delivery, ideation, and continuity. Each reads the memory layer first and writes its findings or decisions back, so nothing drifts. Every skill is a slash command - "how to use it" is simply typing its name.
Spec-driven, not free-floatingEvery skill anchors in claude/srs.md and claude/context.md before it acts, and records outcomes in the memory layer (design-decisions.md, context.md, or CHANGELOG.md). They extend the SDLC; they never bypass it.
Core workflow
The spine of the SDLC - run them roughly in order. Each gates the next: you cannot plan before the spec is frozen, or build before the plan is written.
/spec-initScaffold the project tree inside an existing Claude session. Use when starting a new project or adopting the Kit in an empty directory./spec-requirementsCross-questions you across five mandatory categories, then freezes claude/srs.md with BDD acceptance scenarios. Use first, before any design or code; refuses to proceed on empty load-bearing categories./spec-designExtracts a design system from your references or infers one from the SRS - never fabricates brand colors. Use after requirements, before building UI./spec-planProduces an 8-10 step build plan, each stage standalone, testable, and runnable. Use after the SRS is frozen; refuses while load-bearing open questions remain./spec-featureRuns the full 6-phase feature cycle (requirements → architecting → product specs → tech specs → planning → code). Use to build any feature end-to-end./spec-refactorCleans only the files changed in the current cycle, writing an audit trail. Use right after a feature cycle - never for repo-wide cleanups./spec-bugReproduction-first bug workflow: recipe → failing regression test → smallest fix → CHANGELOG entry. Use when something is broken; refuses without a reproduction./spec-docsReconciles README and memory files against the actual code; never touches source. Use when docs have drifted from reality./spec-syncReconciles context.md against the repo and compresses any memory file past 1,500 lines with an audit trail. Use when memory has drifted or grown large.Design
Shape the structure before code is written. These decide what is allowed to know about what.
/spec-architectDesigns module, service, and layer boundaries from the forces most likely to change. Defaults to a modular monolith until measured evidence earns a split, and records every non-obvious choice as a 5-line ADR in design-decisions.md./spec-db-designDesigns and reviews the database schema - keys, foreign keys, constraints, and indexes for the real query shapes. Enforces invariants in the schema, not the app, and keeps every migration reversible and additive.Review
Six lenses on a change, each labelling findings by severity and reviewing only the diff.
/spec-reviewMulti-axis review across correctness, readability, architecture, security, and performance. Modes: code, pr, frontend, backend, and comments (which also rewrites drifted or verbose comments)./spec-code-qualityRaises quality on code you write and runs a simplification pass - hierarchy of correct → honest → changeable → consistent, then small. Reports defects as input → wrong behavior → consequence./spec-securityThreat-models each trust boundary with STRIDE, then verifies the always-do controls. Gates new auth, data, or integration changes behind explicit human approval./spec-performanceMeasurement-first: no optimization without a number, no “faster now” without a second number. Checks the database first, where the time usually is./spec-testJudges tests by whether they would catch a regression, not by coverage percent. Flags missing edge and error cases and treats flakiness as a defect./spec-uxReviews usability and WCAG 2.1 AA accessibility against the SRS users and jobs-to-be-done - including the four states (empty, loading, error, populated) every data view needs.Delivery
Move verified change safely from a branch to production.
/spec-cicdReviews and sets up the quality-gate pipeline - lint, types, tests, build, audit - wired to the project’s real commands. No gate is skippable./spec-launchPromotes across dev → staging → production behind feature flags, with staged-rollout thresholds and a written rollback plan. Every launch is reversible, observable, and incremental./spec-gitAtomic commits, short-lived branches, and semantic-version releases where the tag is the source of truth. Scans for secrets before every commit.Ideation
Widen the option space and bring the outside world in - before committing.
/spec-brainstormDiverges to 3-6 genuinely different approaches, then converges on a recommendation scored by fit, cost, risk, and reversibility. Never silently picks one./spec-suggestSurfaces evidence-backed improvements ranked by leverage (impact vs effort), split into Now / Soon / Later. Advisory only - the owning skill does the work./spec-researchGathers external knowledge or market intelligence with a cite-or-flag rule: every claim is either sourced or explicitly marked inference. Modes: knowledge and market.Continuity
Survive an interruption without losing the thread.
/spec-resumeRestores work stopped by a crash, dropped connection, lost context, or usage limits from a resumption brief in claude/resume.md - leading with the next action and never redoing verified work.ModesSkills with modes take the mode as an argument, e.g. /spec-review frontend or /spec-research market. Omit it to get the default (code review, knowledge research).