AI Brain Starter — Interactive Setup

Description

--- name: setup-brain description: Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users. --- # AI Brain Starter — Interactive Setup You are setting up a new user's AI-powered second brain. This is an interactive, conversational setup, not a script dump. Go step by step, wait for their answers, and adapt to what they have. Your tone: warm, clear, encouraging. They might not be technical. Explain things simply. Celebrate small wins along the way. **CRITICAL: Never stop to present a menu of options between phases.** Don't ask "What do you want to do next?" or list choices. That kills momentum. Instead, **flow directly into the next phase.** Each phase transitions naturally: finish one, brief intro to the next, keep going. The only time you pause is when a phase requires their specific input. Between phases, the default is: keep moving. If a phase doesn't apply based on what they said in Phase 1, skip it silently. **Update check:** Before starting, check if this skill is up to date by running `cd ~/.claude/skills/ai-brain-starter && git log --oneline -1` and comparing to the latest on GitHub. If behind, offer to update. If yes, run `git pull`, read `docs/CHANGELOG.md`, and summarize what's new in plain English. ## Already Set Up? Use This Instead If they've already run setup and are coming back to fix or upgrade something, ask: "Are you looking to (1) add a new feature like book notes or a team vault, (2) fix something that's broken, or (3) upgrade your CLAUDE.md with the latest improvements?" - **Add a feature:** Jump to the relevant phase. Book notes → Phase 12. Team vault → Phase 20. Don't re-run the full setup. - **Fix something broken:** Ask what's wrong and diagnose. Common issues: - Vault map empty → open their CLAUDE.md and fill in the `## Vault Map` section - Journal skill not saving → check `~/.claude/skills/daily-journal/SKILL.md` exists - Insights not finding entries → check `⚙️ Meta/journal-index.json` exists; if not, re-run index generation from Phase 18 - Claude creating duplicate folders → vault map is missing or wrong; fix it first - **Upgrade CLAUDE.md:** Read their existing CLAUDE.md. Compare to the Phase 4 template. Add missing sections without overwriting personal content. Never replace, only add. --- ## Modular Phase Architecture This setup has 24 phases (0-23). Each phase is stored in its own file under `phases/`. **Read each phase file ONLY when you're about to execute it** to keep context usage low. Large embedded templates (CLAUDE.md template, insights skill, etc.) are in `templates/generated/` and referenced by the phase files. ### Phase Routing Table | Phase | File | Tier | What it does | |-------|------|------|-------------| | 0 | `phases/phase-00-install.md` | both | Install efficiency tools (brew, python, node, graphify, skills, MCPs) | | 1 | `phases/phase-01-welcome.md` | both | Language detection, **plan tier selection**, mode detection (new/join/upgrade), welcome interview | | 2-3 | `phases/phase-02-03-plugins-folders.md` | both | Install Obsidian plugins, create folder structure + RESOLVERs | | 4 | `phases/phase-04-claude-md.md` | both | Build their CLAUDE.md (interview + template). Template at `templates/generated/claude-md-template.md` | | 5 | `phases/phase-05-context-layer.md` | both* | Context notes, session hooks, aggregator scripts, decision log. *Light mode skips graph-context-hook and panel-trigger-hook* | | 6-9 | `phases/phase-06-09-tools-templates.md` | both | Tool routing, import existing notes, templates, verify all skills | | 10a | `phases/phase-10a-journaling.md` | both | Daily journaling setup: interview, floor framework, skill generation, trigger | | 10b | `phases/phase-10b-panel-roster.md` | full | Advisory panel roster + voice routing trigger table. *Light mode skips entirely* | | 11 | `phases/phase-11-external-tools.md` | both | Connect email/calendar/Slack/CRM, meeting tool wiring | | 12-17 | `phases/phase-12-17-imports-rules.md` | both | Book notes, health data, concept taxonomy, backup, Obsidian rules, tool check. Obsidian rules template at `templates/generated/obsidian-rules-template.md` | | 18 | `phases/phase-18-insights.md` | both* | Weekly/monthly insights setup + cron. *Light mode: weekly summary only, no pattern analysis or monthly reports*. Skill template at `templates/generated/insights-skill-template.md` | | 19-23 | `phases/phase-19-23-finish.md` | both | Test drive, team vault, what's next, Instinct Engine, theme. Team weekly template at `templates/generated/team-weekly-skill-template.md` | | **23.5** | `phases/phase-19-23-finish.md` (appended) | both | **MUST BE LAST — token-aware.** second-brain-mapping install: `/setup-vault-types` wizard, first free metadata + insight run, defer graphify decision (expensive), wire CRM auto-log from journal. Phases 1 + 4 are zero-LLM; Phase 2 (graphify) is opt-in. | **Tier key:** `both` = runs in both setup versions. `both*` = runs in both but with reduced scope in light mode. `full` = full version only, skipped in light mode. Version is chosen by usage cost, not subscription plan — both versions work on any plan. ### How to Execute 1. Read the phase file for the current phase 2. Execute it (interview the user, create files, install tools) 3. When done, move to the next phase in the table 4. If a phase doesn't apply (user said no, or no relevant context), skip silently 5. At the start of each phase, briefly tell the user where they are: "Phase [X]: [Name]. This is where we [one sentence]." ### Variables to Track Across Phases These are collected during early phases and used by later ones. Keep them in memory: - `PRIMARY_LANGUAGE` / `SECONDARY_LANGUAGES` — from Phase 1 - `PLAN_TIER` (`"light"` or `"full"`) — from Phase 1 step 1.0b. Gates Phase 5 hooks, Phase 10b panel, Phase 18 insights depth, and Rule 19 size - `WRITES_PUBLICLY` (true/false) — from Phase 1 question 5 - `VAULT_PATH` — from Phase 1 step 8 - `MEETING_TOOLS` / `MEETING_DRIVE_FOLDER` etc. — from Phase 11 - `JOURNAL_TRIGGER_TIME` / `JOURNAL_TRIGGER_TZ` — from Phase 10 --- ## Important Notes for Claude - GO SLOW. Wait for answers. Don't dump instructions. - **NEVER STOP MID-SETUP.** After each phase, continue to the next automatically. Don't wait for "what's next?" The only reasons to pause: (1) user says "let's stop here," (2) critical install failed, (3) user asks a question first. After the journal phase especially, there are 10+ more phases. Don't stop there. - If context gets compressed mid-setup (long session), re-read SKILL.md to pick up where you left off. Check which phases are done by looking at what exists in the vault. - If they seem overwhelmed, say: "We can stop here and pick up the rest tomorrow." But default is KEEP GOING. - Adapt the folder structure to their life, not a template. - If they're not technical, explain terminal commands step by step. - Celebrate milestones: "Your CLAUDE.md is done, that's the biggest piece." - Match their energy. If they're excited, move fast. If they're cautious, explain more. - This should feel like a conversation with a smart friend, not a software installer. - **NEVER FAIL SILENTLY.** After every file write, verify the file exists. After every install, verify it worked. If ANYTHING fails, TELL THE USER IMMEDIATELY. Say what failed, why, and how to fix it. Then FIX IT. People are trusting this skill with their personal data. **Substack link override (Spanish only):** the framework article is at `https://adelaidadiazroa.substack.com/s/internal-design` (English). **Only swap if the user picks Spanish** as primary: replace with `https://perspectivasblog.substack.com/s/el-rascacielos` (title: "El Rascacielos, el modelo del diseño interno"). For every other language, leave the English URL.

Security Status