Manage Boxd VM lifecycle via ssh boxd.sh — list, stop, start, fork, destroy VMs, or fork from a golden source. Use when the user says "boxd", "list my vms", "stop boxd", "pause boxd", "wake up X", "fork from golden", "destroy vm", or asks about Boxd VM status. Does NOT launch Claude sessions (use /launch-remote for…
Create a new Claude Code skill with correct structure, progressive disclosure, and token-efficient design. Use when the user wants to turn a workflow into a skill, says 'make this a skill', or asks to create/write a skill. Also triggered by /deep-reflect when it identifies a missing skill.
Deep audit of Claude session history. Analyzes JSONL logs for mistakes, failed patterns, token waste, and missed opportunities. Writes findings to memory.
Structured design exploration for open-ended technical questions. Combines codebase analysis, external research, strategy generation, and adversarial debate to produce a decision-ready report saved to docs/research/. Use when facing 'how should we...', 'what's the best way to...', 'deep think about', or any design…
Improve a skill based on how it just performed. Analyzes conversation for friction, corrections, wasted tokens, and missed steps, then patches the skill. Auto-invoke after any skill completes. Also triggered by /deep-reflect when it identifies skills that were used.
Systematic investigation of a production bug or performance issue. Traces symptoms to root cause through code analysis, hypothesis testing, and empirical validation.
Implementation and verification phase. Runs implement → sweep → review → prove-it → complete. Takes a validated feature file from /plan-work and delivers a green PR. Use when the plan is ready and you just need to build it.
Metacognitive checkpoint — analyze user intent before executing. Use standalone or let orchestrate/plan invoke it. Forces critical thinking about what the user actually wants.
Classify work as bug/feature/refactor, run planning, create tasks from every acceptance criterion, then hand off to implementation. The task list is the contract.
Research and planning phase for features. Runs intent → plan → challenge → readiness gate. Produces a validated feature file ready for /deliver-work. Use before implementation when the problem needs thinking, not just coding.
Prove implementation correctness by mapping every acceptance criterion to concrete evidence (passing tests, command output, code grep). Use after /review passes, before marking a PR ready. Also use standalone when you want proof that work is actually done — not just 'I think it works.'.
Run parallel code reviews: principles-reviewer (SRP/design), hygiene-reviewer (reuse/patterns/idioms), test-reviewer (pyramid/coverage), and security-reviewer (PII/secrets). Surfaces conflicts for human decision.
★not rated 2 4mo agoA53 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: