Interactive orientation and reference guide for Zaphod. Use when onboarding, learning features, or looking up how to do something.
Walk new owners through their first session and serve as an ongoing reference for Zaphod's capabilities. First-run mode covers the essentials step by step. After that, jump to any topic by name.
.local/.orientation-complete).local/.orientation-complete marker after completing the walkthrough--topic <name> is provided: Jump directly to that topic section. Skip first-run detection.--full is provided: Run the full walkthrough regardless of marker..local/.orientation-complete exists: Show the topic menu (reference mode).Greet the user in Zaphod's voice. Briefly explain what this workspace is and what the walkthrough covers. Present the 6-section list and ask if they want all 6 or specific ones.
setup)scripts/zaphod.sh and explain what it doessource ~/a/zaphod/scripts/zaphod.sh in ~/.zshrczaphod--add-dir: Zaphod's persona loads from this workspace; your code is accessible via the added directorysessions)@ syntax/journal at end, /recap at startplugins)warden:security-review before installingclaude plugin list, claude plugin install <name>knowledge).claude/knowledge/): Curated reference files loaded at startupdocs/solutions/): Institutional memory — add entries with ce:compound.claude/skills/<name>/SKILL.md following standard structure.claude/rules/ for always-loaded procedural guidancefirst-missions)Mission 1: Convention Capture — Tell Zaphod about your team's working conventions. Share branching strategy, code style, deployment process, communication norms. Ask Zaphod to write conventions as rule files or knowledge files.
Mission 2: Codebase Survey — Point Zaphod at a project and ask it to survey and document the architecture, key patterns, and dependencies. Review and refine the output.
Mission 3: Problem Journal — After your first non-trivial task (30+ minutes, non-obvious solution), run ce:compound to document it as a KB entry.
fleet)troubleshooting)| Issue | Cause | Fix |
|---|---|---|
| Context getting large | Long session, many file reads | /journal, fresh session, /recap |
| Permission prompts | Classifier blocking legitimate action | Add pattern to autoMode.allow in .claude/settings.local.json |
| Plugin skills not being used | Missing "you are not alone" instruction | Check CLAUDE.md Plugin Skills section |
| Fleet CI not triggering | Missing ANTHROPIC_API_KEY secret | gh secret set ANTHROPIC_API_KEY -R erochest/zaphod |
| Personality feels generic | SOUL.md too vague | Sharpen traits, add speech patterns |
| Knowledge not loading | Files not in .claude/knowledge/ | Domain reference files must be in .claude/knowledge/ to auto-load |
.local/.orientation-complete markerzaphod to launch, /journal to end, /recap to start, ce:compound to capture knowledge/getting-started --topic <name> for any section~/a/zaphod.local/.orientation-complete marker written (first-run mode only)