claude-code-config

Score way matching (embedding and BM25), analyze vocabulary, and validate frontmatter. Use when testing how well a way matches prompts, checking cosine similarity or BM25 scores, inspecting the embedding engine status, or validating way files.

Check how much context window remains in this session. Use when you want to know token budget, context usage, or how much room is left before compaction. Also use proactively when working on long tasks to gauge remaining capacity.

Cite governance controls and justifications when making recommendations about code quality, security, commits, or documentation. Use when justifying why a practice matters, when a user asks "why do we do this?", when reviewing code against standards, or when recommending practices that align with NIST, OWASP, ISO, SOC 2, CIS, or IEEE controls.

Ship current work through the branch → commit → push → PR → merge → cleanup flow. Picks up wherever you are in the cycle. Use when the user says "ship it", "land this", "merge this", or invokes /ship.

Review what changed in Claude Code upstream and compare against this project's commits and ADRs. Surfaces opportunities, gaps, and ADR status drift. Discovery conversation, not compliance dashboard.

Strategy selector for structured reasoning. Lists available thinking frameworks and invokes the right one. Use when facing complex decisions, trade-offs, or when stuck.

Self-Consistency reasoning — run multiple independent reasoning paths and take consensus. Use for high-stakes decisions where reasoning errors are costly.

ReAct reasoning — explicit reason-act-observe cycle for investigation and debugging. Use when you need to interleave reasoning with tool actions systematically.

Step-Back reasoning — abstract to general principles, then apply back to the specific problem. Use when stuck or when the solution is not obvious from the specifics.

Tree of Thoughts reasoning — explore multiple approaches, branch, evaluate, prune, and select the best. Use when there are multiple viable solutions and you need to compare them systematically.

Trilemma reasoning — balance three competing objectives through satisficing. Use when you cannot optimize all dimensions simultaneously and need to find an acceptable trade-off.

Set up direnv/.envrc for per-project Claude Code environments — switch API keys, providers, models, and feature flags automatically when entering a directory. Use when the user wants to manage multiple Claude accounts, switch between Anthropic/Bedrock/Vertex per project, or configure per-directory environment variables.

Send and receive files, directories, or text between computers using magic-wormhole. Guides the user through the transfer interactively. Use when the user says "wormhole", "send a file", "receive a file", or invokes /wormhole.

Manage Architecture Decision Records using the project's ADR CLI tool. Use when the user wants to create, list, view, lint, or index ADRs, or when working with docs/architecture/ files. Triggers on "create an ADR", "new ADR", "list ADRs", "lint ADRs", "what ADRs exist", "ADR domains".