
nav-init
by dkyazzentwatwa
Superpowers + Navigator For Claude Code = ๐คฏ
SKILL.md
name: nav-init description: Initialize SuperNavigator (OS + App layers) documentation structure in a project. Auto-invokes when user says "Initialize SuperNavigator", "Initialize Navigator", "Set up SuperNavigator", etc. allowed-tools: Write, Bash, Read, Glob version: 6.0.0 triggers:
- "initialize supernavigator"
- "init supernavigator"
- "set up supernavigator"
- "setup supernavigator"
- "initialize navigator"
- "init navigator"
- "set up navigator"
- "setup navigator"
- "create navigator structure"
- "bootstrap navigator"
- "start navigator project"
SuperNavigator Initialization Skill
Purpose
Creates the SuperNavigator documentation structure (.agent/) in a new project, copies templates, and sets up initial configuration for both OS Layer (Navigator context management) and App Layer (Superpowers workflows).
When This Skill Auto-Invokes
- "Initialize SuperNavigator in this project"
- "Set up SuperNavigator"
- "Initialize Navigator in this project" (legacy, still works)
- "Create .agent folder for SuperNavigator"
- "Bootstrap SuperNavigator for my project"
SuperNavigator Layered Architecture
This skill initializes both layers:
- OS Layer (Navigator): Context management, Theory of Mind, session persistence
- App Layer (Superpowers): TDD workflows, code review, systematic debugging
Both layers communicate via shared .agent/ data store with implicit integration.
What This Skill Does
- Checks if already initialized: Prevents overwriting existing structure
- Creates
.agent/directory structure:.agent/ โโโ DEVELOPMENT-README.md โโโ .nav-config.json โโโ tasks/ โโโ system/ โโโ sops/ โ โโโ integrations/ โ โโโ debugging/ โ โโโ development/ โ โโโ deployment/ โโโ grafana/ โโโ docker-compose.yml โโโ prometheus.yml โโโ grafana-datasource.yml โโโ grafana-dashboards.yml โโโ navigator-dashboard.json โโโ README.md - Creates
.claude/directory with hooks:.claude/ โโโ settings.json # Token monitoring hook configuration - Copies templates: DEVELOPMENT-README.md, config, Grafana setup
- Auto-detects project info: Name, tech stack (from package.json if available)
- Updates CLAUDE.md: Adds Navigator-specific instructions to project
- Creates .gitignore entries: Excludes temporary Navigator files
Execution Steps
1. Check if Already Initialized
if [ -d ".agent" ]; then
echo "โ
Navigator already initialized in this project"
echo ""
echo "To start a session: 'Start my Navigator session'"
echo "To view documentation: Read .agent/DEVELOPMENT-README.md"
exit 0
fi
2. Detect Project Information
Read package.json, pyproject.toml, go.mod, Cargo.toml, or similar to extract:
- Project name
- Tech stack
- Dependencies
Fallback: Use current directory name if no config found.
3. Create Directory Structure
Use Write tool to create:
.agent/
.agent/tasks/
.agent/system/
.agent/sops/integrations/
.agent/sops/debugging/
.agent/sops/development/
.agent/sops/deployment/
.agent/grafana/
4. Copy Templates
Copy from plugin's templates/ directory to .agent/:
DEVELOPMENT-README.md:
- Replace
${PROJECT_NAME}with detected project name - Replace
${TECH_STACK}with detected stack - Replace
${DATE}with current date
.nav-config.json (SuperNavigator enhanced):
{
"version": "6.0.0",
"project_name": "${PROJECT_NAME}",
"tech_stack": "${TECH_STACK}",
"layers": {
"os_layer_enabled": true,
"app_layer_enabled": true
},
"project_management": "none",
"task_prefix": "TASK",
"team_chat": "none",
"auto_load_navigator": true,
"compact_strategy": "conservative",
"tom_features": {
"verification_checkpoints": true,
"confirmation_threshold": "high-stakes",
"profile_enabled": true,
"diagnose_enabled": true,
"belief_anchors": false
},
"loop_mode": {
"enabled": false,
"max_iterations": 5,
"stagnation_threshold": 3,
"exit_requires_explicit_signal": true,
"show_status_block": true
},
"app_layer_features": {
"tdd_enforced": true,
"git_worktrees_enabled": true,
"subagent_development": true,
"systematic_debugging": true
},
"implicit_integration": {
"auto_save_markers": true,
"auto_compact_threshold": 0.85,
"auto_update_nav_tasks": true,
"trigger_boundaries": [
"before_brainstorming",
"after_plan_complete",
"after_code_review",
"on_branch_finish"
]
}
}
Grafana Setup: Copy all Grafana dashboard files to enable metrics visualization:
# Find plugin installation directory
PLUGIN_DIR="${HOME}/.claude/plugins/marketplaces/jitd-marketplace"
# Copy Grafana files if plugin has them
if [ -d "${PLUGIN_DIR}/.agent/grafana" ]; then
cp -r "${PLUGIN_DIR}/.agent/grafana/"* .agent/grafana/
echo "โ Grafana dashboard installed"
else
echo "โ ๏ธ Grafana files not found in plugin"
fi
Files copied:
- docker-compose.yml (Grafana + Prometheus stack)
- prometheus.yml (scrape config for Claude Code metrics)
- grafana-datasource.yml (Prometheus datasource config)
- grafana-dashboards.yml (dashboard provider config)
- navigator-dashboard.json (10-panel Navigator metrics dashboard)
- README.md (setup instructions)
5. Update Project CLAUDE.md
If CLAUDE.md exists:
- Append Navigator-specific sections
- Keep existing project customizations
If CLAUDE.md doesn't exist:
- Copy
templates/CLAUDE.mdto project root - Customize with project info
6. Setup Token Monitoring Hook
Create .claude/settings.json for token budget monitoring:
mkdir -p .claude
cat > .claude/settings.json << 'EOF'
{
"hooks": {
"PostToolUse": [
{
"matcher": "Write|Edit|Bash|Task",
"hooks": [
{
"type": "command",
"command": "python3 \"${CLAUDE_PLUGIN_DIR}/hooks/monitor-tokens.py\"",
"timeout": 5
}
]
}
]
}
}
EOF
echo "โ Token monitoring hook configured"
What this does:
- Monitors context usage after each tool call
- Warns at 70% usage, critical alert at 85%
- Suggests
/nav:compactwhen approaching limits
7. Create .gitignore Entries
Add to .gitignore if not present:
# Navigator context markers
.context-markers/
# Navigator temporary files
.agent/.nav-temp/
8. Success Message
โ
SuperNavigator Initialized Successfully!
Created structure:
๐ .agent/ SuperNavigator documentation
๐ .agent/tasks/ Implementation plans (App layer writes, OS layer indexes)
๐ .agent/system/ Architecture docs
๐ .agent/sops/ Standard procedures
๐ .agent/grafana/ Metrics dashboard
๐ .agent/.nav-config.json Configuration (both layers enabled)
๐ .claude/ Claude Code hooks
๐ .claude/settings.json Token monitoring config
๐ CLAUDE.md Updated with SuperNavigator workflow
Layers initialized:
โ OS Layer (Navigator): Context management, Theory of Mind, Loop Mode
โ App Layer (Superpowers): TDD, code review, systematic debugging
โ Implicit integration: Auto-markers, auto-compact, workflow boundaries
Next steps:
1. Start session: "Start my SuperNavigator session"
2. Optional: Enable metrics - see .agent/sops/integrations/opentelemetry-setup.md
3. Optional: Launch Grafana - cd .agent/grafana && docker compose up -d
Token monitoring is active - you'll be warned when approaching context limits.
Documentation: Read .agent/DEVELOPMENT-README.md
Learn more: README.md (layered architecture)
Error Handling
If .agent/ exists:
- Don't overwrite
- Show message: "Already initialized"
If templates not found:
- Error: "Navigator plugin templates missing. Reinstall plugin."
If no write permissions:
- Error: "Cannot create .agent/ directory. Check permissions."
Predefined Functions
project_detector.py
def detect_project_info(cwd: str) -> dict:
"""
Detect project name and tech stack from config files.
Checks (in order):
1. package.json (Node.js)
2. pyproject.toml (Python)
3. go.mod (Go)
4. Cargo.toml (Rust)
5. composer.json (PHP)
6. Gemfile (Ruby)
Returns:
{
"name": "project-name",
"tech_stack": "Next.js, TypeScript, Prisma",
"detected_from": "package.json"
}
"""
template_customizer.py
def customize_template(template_content: str, project_info: dict) -> str:
"""
Replace placeholders in template with project-specific values.
Placeholders:
- ${PROJECT_NAME}
- ${TECH_STACK}
- ${DATE}
- ${YEAR}
Returns customized template content.
"""
Examples
Example 1: New Next.js Project
User says: "Initialize Navigator in this project"
Skill detects:
package.jsonexists- Name: "my-saas-app"
- Dependencies: next, typescript, prisma
Result:
.agent/created- DEVELOPMENT-README.md shows: "Project: My SaaS App"
- DEVELOPMENT-README.md shows: "Tech Stack: Next.js, TypeScript, Prisma"
- .nav-config.json has project_name: "my-saas-app"
Example 2: Python Project
User says: "Set up Navigator"
Skill detects:
pyproject.tomlexists- Name: "ml-pipeline"
- Dependencies: fastapi, pydantic, sqlalchemy
Result:
.agent/created- Tech stack: "FastAPI, Pydantic, SQLAlchemy"
Example 3: Already Initialized
User says: "Initialize Navigator"
Skill checks:
.agent/directory exists
Result:
โ
Navigator already initialized in this project
To start a session: 'Start my Navigator session'
Integration with Other Skills
nav-start skill:
- Checks for
.agent/DEVELOPMENT-README.md - If missing, suggests: "Initialize Navigator first"
nav-task skill:
- Creates tasks in
.agent/tasks/ - Requires initialization
nav-sop skill:
- Creates SOPs in
.agent/sops/ - Requires initialization
Version History
- 1.0.0 (2025-01-20): Initial implementation
- Auto-detection of project info
- Template customization
- Grafana setup included
- Error handling for existing installations
Notes
- This skill replaces the deleted
/nav:initcommand from v2.x - Templates are copied from plugin installation directory
- Project info detection is best-effort (falls back to directory name)
- Safe to run multiple times (won't overwrite existing structure)
Score
Total Score
Based on repository quality metrics
SKILL.mdใใกใคใซใๅซใพใใฆใใ
ใฉใคใปใณในใ่จญๅฎใใใฆใใ
100ๆๅญไปฅไธใฎ่ชฌๆใใใ
GitHub Stars 100ไปฅไธ
3ใถๆไปฅๅ ใซๆดๆฐใใใ
10ๅไปฅไธใใฉใผใฏใใใฆใใ
ใชใผใใณIssueใ50ๆชๆบ
ใใญใฐใฉใใณใฐ่จ่ชใ่จญๅฎใใใฆใใ
1ใคไปฅไธใฎใฟใฐใ่จญๅฎใใใฆใใ
Reviews
Reviews coming soon