/local-os-builder

name: local-os-builder
description: Set up a Local OS — bootstrap a local Obsidian vault as your second brain and run personalized onboarding. Creates all directories, system files, Obsidian config, memory system, hooks, and output styles, then interviews the user to personalize everything. Two modes — Solopreneurs/Professionals (default), Business/Teams. The Local OS tier of the AIOS family (alongside Skill OS and Cloud OS). Use when user says "set up a local OS", "set up my vault", "bootstrap", "initialize", "onboarding", or runs /local-os-builder.
disable-model-invocation: true

Local OS — Setup + Onboarding

USE WHEN the user runs `/local-os-builder` or asks to set up a Local OS, set up their vault, bootstrap the assistant, initialize the system, or configure a local Obsidian second brain.

This is the **Local OS** tier of the AIOS family — the brain lives in a local Obsidian vault on disk. It shares the same internal structure as the Skill OS and Cloud OS tiers, so a user can graduate between them.

This is a three-phase process:

• **Phase 0**: Mode Selection — Ask which OS variant to create
• **Phase A**: Bootstrap — Create the directory structure and system files for the selected mode
• **Phase B**: Onboarding — Interview the user and personalize everything

Pre-flight Check

Check if `claude.md` or `CLAUDE.md` exists **only** in the current working directory (do NOT search subdirectories or parent directories — check only the exact CWD path).

• **If it exists**: The vault is already set up. Ask the user:
• "This vault is already set up. Would you like to:"
• **Re-run the interview** — Keep existing structure, update memory files based on new answers
• **Full reset** — Delete everything and start fresh (confirm twice before proceeding)
• **Cancel** — Do nothing
• **If it does NOT exist**: Proceed with full setup (Phase 0 + Phase A + Phase B)

---

Phase 0: Mode Selection

Ask the user to pick a mode using AskUserQuestion with these exact `label` and `description` values:

• Question: `What type of vault do you want?`
• Option 1 label: `Solopreneurs/Professionals` — description: `Blends work and personal. Best for solo founders, freelancers, consultants.`
• Option 2 label: `Business/Teams` — description: `Org structure with departments, processes, stakeholders. Best for teams and companies.`

**CRITICAL**: You MUST pass both `label` AND `description` for each option in AskUserQuestion. The `description` field is what explains each mode to the user. Never leave `description` empty.

Mode mapping:

• Solopreneurs/Professionals → `os-mode: professional`
• Business/Teams → `os-mode: business`

Accept any clear signal: "solo", "professional", "freelancer", "business", "org", "team", etc.

If the user skips or says "I don't know", use **Solopreneurs/Professionals** (professional mode).

Store the selected mode. It will be written to `CLAUDE.md` frontmatter as `os-mode: professional | business`.

---

Phase A: Bootstrap

Create the directory structure and write all system files for the selected mode.

Resolving reference file paths

Every `references/<file>.md` mentioned below lives in the `references/` subdirectory next to **this SKILL.md** — not in the user's working directory. Two conventions matter:

• **Read paths** (`references/foo.md`) → resolve relative to this SKILL.md's directory.
• **Write paths** (`./Foo/CLAUDE.md`) → resolve relative to the user's current working directory (the vault root).

If the Read tool can't open a `references/...` path directly (some harnesses mount the skill at a path that differs between Read and Bash), run a quick discovery step **once** before Step A.2:

# Find the references directory; cache the result for the rest of Phase A.
find / -type d -path '*/setup/references' 2>/dev/null | head -1

Use that absolute path as the prefix for every reference read in Phase A and Phase B. Don't retry path resolution per-file — do it once and reuse.

Step A.1: Create Directory Structure

**All modes** share this base:

mkdir -p .claude
mkdir -p Context
mkdir -p Projects
mkdir -p Daily
mkdir -p Resources
mkdir -p Skills

**Solopreneurs/Professionals mode** adds:

mkdir -p Intelligence/meetings/team-standups
mkdir -p Intelligence/meetings/client-calls
mkdir -p Intelligence/meetings/one-on-ones
mkdir -p Intelligence/meetings/general
mkdir -p Intelligence/competitors
mkdir -p Intelligence/market
mkdir -p Intelligence/decisions
mkdir -p Intelligence/archive

**Business mode** adds:

mkdir -p Intelligence/meetings/team-standups
mkdir -p Intelligence/meetings/client-calls
mkdir -p Intelligence/meetings/one-on-ones
mkdir -p Intelligence/meetings/board-reviews
mkdir -p Intelligence/meetings/all-hands
mkdir -p Intelligence/meetings/cross-team
mkdir -p Intelligence/meetings/general
mkdir -p Intelligence/competitors
mkdir -p Intelligence/market
mkdir -p Intelligence/decisions
mkdir -p Intelligence/processes
mkdir -p Intelligence/archive
mkdir -p Departments
mkdir -p Team
mkdir -p Onboarding
mkdir -p Resources/templates

`Team/` is created empty here. Profile-first subfolders (`Team/{org}/Profiles/{person}/...`) are scaffolded in Phase B once Q6 answers are in.

Step A.2: Write System Files from References

Read each reference file and write it to the corresponding local path. The reference files contain the complete content for each system file.

**All modes** — shared system files:

| Reference File | Creates at Local Path | |---|---| | `references/settings-json-template.md` | `./.claude/settings.json` | | `references/claudeignore-template.md` | `./.claudeignore` | | `references/gitignore-template.md` | `./.gitignore` |

**Mode-specific root CLAUDE.md template:**

| Mode | Reference File | Creates at Local Path | |---|---|---| | Solopreneurs/Professionals | `references/claude-md-template.md` | `./CLAUDE.md` | | Business | `references/claude-md-template-business.md` | `./CLAUDE.md` |

**P