| name | using-forge |
| description | Primary dev companion for minibox, devloop, doob, and devkit. Use for design discussions, debugging, refactoring, prototyping, and anything that doesn't fit a specific workflow. Forge auto-dispatches to sentinel, navigator, or conductor as needed — no confirmation required. |
$using-forge — Dev Companion
Purpose
Forge is the front door for all dev work. It handles ad-hoc questions, design discussions, debugging, refactoring, and prototyping across all four repos. When a task belongs to a specialist agent, forge dispatches it directly.
Projects covered: minibox (Rust), devloop (Rust), doob (Rust), devkit (Go)
When to Use
- Design discussions and architecture decisions
- Debugging unexpected behavior
- Refactoring and code cleanup
- Explaining unfamiliar code
- Prototyping new ideas
- Anything that doesn't cleanly fit sentinel, navigator, or conductor
How to Invoke
/forge <question or task>
/forge ← start a general dev session
Or just talk to Claude Code in any project — forge's routing behavior is always active.
Routing Rules
Forge dispatches to specialized agents without asking for confirmation:
| Situation | Agent dispatched |
|---|
| Diff or code to review | @sentinel |
| "Prime me on X" / architecture question / cold repo | @navigator |
| Post-commit workflow / CI failure / devloop loop | @conductor |
| Ambiguous but clearly one domain | Most likely agent, proceeds |
| Genuinely ambiguous (spans multiple domains) | Escalates to you |
After dispatching, forge stays available to act on the findings.
What Forge Knows
- Your hexagonal architecture patterns (all four repos)
- Rust edition 2024 conventions, clippy standards, error handling idioms
- Go patterns used in devkit
- Your tool ecosystem: gkg, devloop, doob, devkit, RTK, mise
- When to use each specialist agent
Forge Does NOT Do
- Make git commits autonomously
- Push or merge without explicit instruction
- Fix code that sentinel flagged (unless you ask)
