derive-conventionsDerives a host repository's unwritten conventions — naming, error-handling shape, docstring format, CLI voice — from its own code, presents each inferred rule with its evidence for accept/edit/reject, and writes the approved set to CONVENTIONS.md so craft's review agents stop re-deriving them every
design-by-storiesDesign or redesign an artifact's shape — a schema, template, data model, config format, note type, or API surface — by modeling its actors and user stories first, then deriving the shape from the stories. One fork at a time, human adjudicates every fork. Distinct from interrogate-model (critiques an
diagnoseDisciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression. Adapted f
domain-modelingBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an NDR decision that surfaces while modelling. Adapted from mattpocock/skills (MIT, © 2026 Matt Pocock). - Read - Grep - Glob - Write - Edit - Skill
grill-with-docsGrill a plan against this repo's CONTEXT.md glossary and NDR atoms, sharpen terminology, and update CONTEXT.md inline as decisions crystallise. Use when stress-testing a plan against project vocabulary, locking in a domain term, or surfacing drift between code naming and the glossary. Adapted from m
grillGrill the user relentlessly about a plan, decision, or idea — one question at a time, walking the design tree until you reach a shared understanding. Use when the user says "grill me", "grill this", "grill me on this plan", or asks to be interviewed hard about something before acting on it. Adapted
grokBuild durable, supersession-aware understanding of a codebase across multiple sessions — grounded in the repo's real sources rather than parametric guesses, explained one subsystem at a time, and persisted as vault records that graduate into CONTEXT.md and NDR atoms. Bash(obsidian-cli *), Write, Rea
improve-codebase-architectureFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions surfaced via NDR atoms. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
infra-reviewReviews an AWS Terraform pull request whose plans are produced by Atlantis, from a local checkout. This skill should be used when the user runs `/infra-review <pr-number-or-url>`, says "review this terraform PR", "infra review", "review the atlantis plan", "review this infrastructure change", or ask
interrogate-modelHolistic representability review of a domain model taken as a whole — an authorization scheme, permission table, state machine, data model, or tenancy model. Enumerates the legitimate scenarios the model must serve, marks which are unrepresentable or only-via-overreach, surfaces emergent cross-axis
lucid-architecture-diagramCreate, review, or edit AWS cloud architecture diagrams in Lucid (lucidchart) via the Lucid MCP server. This skill should be used when the user mentions Lucid by name, asks to create/edit a cloud architecture diagram, shares a Lucid URL, asks to review or critique an existing architecture diagram, o
prototypeBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like. Adapted from mattpocock/skills (MIT, © 2026 Matt Pocock). - Read - Grep - Glob - Write - Edit
quiz-meOpt-in active-recall comprehension check on code or a concept just explained. Predict-then-verify, one question at a time, pitched at the why and the mental model rather than syntax recall. - Read - Grep - Glob - AskUserQuestion
resolve-conflictsResolve an in-progress merge, rebase, or jj conflict by recovering each side's original intent before picking a resolution. Detects git vs jj and follows that VCS's own mechanics. Use when the user says "resolve these conflicts", "fix the merge conflicts", "this rebase is conflicted", "jj log shows
screen-critiqueCritique a UI screen design — a mockup, a design-tool board, or a built screen — in a fixed order: purpose, then structure, then copy, then consistency. Use when a screen "doesn't feel right", before iterating on a board, or when asked to review or critique a screen's design. - Read - Grep - Glob
tddTest-driven development — the red-green loop, done so the tests are worth keeping. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", wants integration tests, or asks for test-first development. Adapted from mattpocock/skills (MIT, © 2026 Matt Pocock). -
wait-whatRe-pitch a message that did not land, with enough context to follow — in Simplified Technical English, using the repo's own vocabulary. Adapted from mattpocock/skills (MIT, © 2026 Matt Pocock).
wizardGenerate an interactive bash wizard that walks a human through the steps only they can perform — provisioning infrastructure, capturing credentials or CI secrets, clicking through an unfamiliar third-party dashboard, or running a one-off migration or cutover. Use when the user says "write me a wizar
zoom-outGive broader context or a higher-level perspective — map how code fits into the bigger picture. Adapted from mattpocock/skills (MIT, © 2026 Matt Pocock). - Read - Grep - Glob