Plugin Claude Code
Plugin marketplace listing 1 plugin: capstone.
Plugin Claude Code
Plugin marketplace listing 1 plugin: capstone.
Plugin Claude Code
Architecture reference generator: a lean docs/capstone/ index plus topic files stamped to the commit they were derived at, built and kept current by one command, map. Companion commands: doctor, an opt-in two-sided review, a greenfield pipeline from mockup to running code with a frontend-design stage, and a…
Instructions file Gemini CLI
Instructions for GentBajko/capstone: @./skills/core/references/dispatcher.md.
Hook
Runs when a session starts, executing init-config.sh via bash with --global. From GentBajko/capstone.
Hook
Runs to expand your prompt before the agent sees it for capstone:help tool calls, executing help-hook.sh via bash. From GentBajko/capstone.
Skill Claude CodeCodex
Use when designing a new/greenfield project's architecture - exhaustive persisted one-question-at-a-time interview, then the full prescriptive reference.
Skill Claude CodeCodex
Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.
Skill Claude CodeCodex
Use when the capstone docs area needs a consistency check or repair - torn writes, done markers without ledger entries, voided plan approvals, index rows pointing at missing files, absorption gaps - reports findings with their owning rules, then applies only the repairs the user approves.
Skill Claude CodeCodex
Use when the user wants one feature taken from idea to working code - "add a feature", "build X end to end", "take X from idea to shipped" - runs the feature chain groom -> plan -> implement consecutively, detecting the feature's stage and resuming at the first incomplete one. For the whole-product greenfield pipeline…
Skill Claude CodeCodex
Use when starting work on a feature or change for a project that already has capstone docs - "new feature", "add a feature", "implement X", "build X", "design a feature", "spec it out", "flesh out", "refine this idea", "let's work on X" - a doc-grounded one-question-at-a-time interview producing a traceable feature…
Skill Claude CodeCodex
Use when asked what the capstone plugin can do - prints the usage block.
Skill Claude CodeCodex
Use when an approved feature plan is ready to become code - executes plan.md task by task with verification, in subagents or inline as you pick, reviews the diff recursively until no new findings survive, then refreshes the affected reference chapters.
Skill Claude CodeCodex
Use when pinning down an app's business logic scenario by scenario - triggers, exact rules, branches, unhappy paths, state transitions, invariants - via a depth-first interview, one file per scenario in docs/capstone/logic/.
Skill Claude CodeCodex
Use when asked to build, refresh, update, or check a codebase's architecture reference docs - "map the codebase", "document this repo", "are the docs current", "bring the docs in line with the code" - writes a docs/capstone/ index plus topic chapters, the logic/ business-logic map and the uiux/ surface map, then on…
Skill Claude CodeCodex
Use when defining a new product idea - adaptive purpose/business-plan/scenarios interview persisted to a file, then a traceable markdown mockup.
Skill Claude CodeCodex
Use when a groomed feature spec needs an implementation plan - studies the chapters the spec cites, writes a task-by-task TDD plan an engineer with zero context could execute, gated on user approval.
Skill Claude CodeCodex
Use when asked for an opinionated review of the codebase - architecture/backend findings, UI findings against the project's own design docs, or both - severity-ranked with evidence, written to docs/capstone/review.md. Bare "review" does both sides; "review backend" or "review frontend" does one. Opt-in judgment; never…
Skill Claude CodeCodex
Use when picking the concrete libraries, packages, and paid services for a designed project - researches current options per capability, presents pros/cons/license/pricing, and records the user's picks into the dependencies chapter.
Skill Claude CodeCodex
Use when capturing how code must be written in this project - typing strictness, library-vs-build posture, paradigm, error handling, testing style, git and commit discipline, and what an AI assistant must never do here - via an interview, producing a normative standards doc that outranks generic best practice. Binding…
Skill Claude CodeCodex
Use when the user says just "capstone" with nothing else, or asks to start or continue the capstone pipeline - runs the greenfield chain one stage at a time (mockup -> logic -> uiux -> architecture -> standards -> stack -> build), detecting completed stages and resuming at the first incomplete one.
Skill Claude CodeCodex
Use when deciding how the product's UI should look and how its UX should behave, from the mockup and logic docs - visual direction, design system, and per-screen design chapters via an interview, using capstone's own vendored design method.