Menu
Choose when to use Claude Code built-in commands before adding FCC-specific workflow.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Recall project state without prompt replay. Use when resuming work, checking prior decisions, or needing context from earlier sessions.
Update the compact FCC handoff at the end of meaningful work or before compaction.
Choose the FCC model tier for a task using `.fcc/router.yml`.
Recall project state without prompt replay. Use when resuming work, checking prior decisions, or needing context from earlier sessions.
Update the compact FCC handoff at the end of meaningful work or before compaction.
| name | claude-command-router |
| description | Choose when to use Claude Code built-in commands before adding FCC-specific workflow. |
Use this skill when a user asks which Claude Code command to run, when a task looks like a known Claude Code workflow, or when you are about to add FCC-specific orchestration.
Prefer Claude Code built-ins when they already fit:
/init to create or refresh CLAUDE.md; use fcc-bootstrap-context only for FCC hooks, handoff files, subagents, and retrieval policy./context all to inspect usage, then /compact <focus> when the session should continue with less history./diff for inspection, /code-review for correctness, and /security-review for security-specific risk./batch when independent worktree units make sense; otherwise plan in the main session and use FCC subagents only for bounded research or review./doctor, /debug, /status, or fcc context doctor depending on whether the problem is Claude Code, provider/proxy, or FCC scaffold./run or /verify when a user-facing app change needs live validation./config, /theme, /statusline, /terminal-setup, or /tui fullscreen.Do not rewrite an explicit slash command. Let commands such as /init, /compact, and /context all pass through unchanged.
If no built-in command fits, continue with the normal FCC workflow: use project context, subagents only when they reduce risk or noise, and run the repository checks before finalizing code changes.