Skip to Content
Skillsnav-init

nav-init

Bootstraps the Navigator .agent/ documentation structure, config, and templates in a project so sessions and other skills have somewhere to read from and write to.

Triggers

Natural-language phrases that auto-invoke the skill:

  • “initialize navigator”
  • “init navigator”
  • “set up navigator”
  • “create navigator structure”
  • “bootstrap navigator”
  • “start navigator project”

What it does

  • Checks for an existing .agent/ directory and refuses to overwrite it (safe to re-run).
  • Detects project name and tech stack from package.json, pyproject.toml, go.mod, Cargo.toml, and similar, falling back to the directory name.
  • Creates the .agent/ tree: tasks/, system/, sops/ (integrations, debugging, development, deployment), and grafana/.
  • Copies and customizes templates — DEVELOPMENT-README.md, .nav-config.json, and the Grafana metrics stack — substituting project name, stack, and date.
  • Appends Navigator sections to an existing CLAUDE.md or creates one, and adds .gitignore entries (each only if absent) for context markers, temp files, the hook-runtime session state (.agent/.nav-runtime-state.json and .lock), the personal config override (.agent/.nav-config.local.json) and the legacy .agent/onboarding/ dir.
  • Relies on the plugin manifest for lifecycle hooks (SessionStart, PreCompact, Stop, etc.); it does not write hooks into .claude/settings.json.

Example

"Initialize Navigator in this project"

The .agent/ structure is created with project-specific docs and config, after which you start working via “Start my Navigator session”. A restart is required to activate the plugin’s hooks.

nav-startnav-onboard