Slash Commands
Navigator runs in hybrid mode: every operation has a natural-language
trigger that auto-invokes a skill, and a subset also has a legacy /nav:*
slash command. Both forms work and route to the same skills, so use whichever
you prefer — natural language is the primary interface.
The plugin ships as skills, not standalone command files. The /nav:* forms
are kept for muscle memory and map directly onto skills.
Command map
| Slash command | What it does | Natural-language trigger | Skill |
|---|---|---|---|
/nav:init | Initialize Navigator’s .agent/ structure and CLAUDE.md in a project | ”Initialize Navigator in this project” | nav-init |
/nav:start | Load the navigator, current task context, and profile to begin a session | ”Start my Navigator session” | nav-start |
/nav:marker | Create a context save point before a break, risky change, or compaction | ”Create a context marker”, “Save my progress” | nav-marker |
/nav:compact | Clear conversation context while preserving knowledge via a marker | ”Clear context and preserve markers”, “Done with this task” | nav-compact |
/nav:stats | Show session efficiency: token savings, cache performance, recommendations | ”Show my stats”, “How efficient am I?“ | nav-stats |
Notes
- Both forms are equivalent.
/nav:startand “Start my Navigator session” invoke the samenav-startskill with the same behavior. - Natural language is preferred. It is more discoverable and covers the full skill set — most skills (e.g. nav-task, nav-graph, nav-upgrade) are reached only by natural-language triggers, not a slash command.
- Session start is mandatory. Begin every session with
/nav:startor “Start my Navigator session” so the navigator and task context load before any work.
For the complete catalog of skills and their triggers, see the skills overview.