/cloud-os-builder

name: cloud-os-builder
description: "Set up a Cloud OS — your second brain hosted either in a synced cloud folder (Google Drive, OneDrive, iCloud, Dropbox) or as a Notion workspace. Asks where to host it, then takes the matching route: for a folder it builds the Local OS structure (root CLAUDE.md + Context + Projects/Intelligence/Daily/Resources/Skills, Obsidian-free) and gives provider-specific sync steps; for Notion it builds pages + databases via the connector. Runs the same personalized onboarding either way. Two modes — Solopreneurs/Professionals (default), Business/Teams. The Cloud OS tier of the AIOS family. Use when the user says \"set up a cloud OS\", \"host my second brain on Google Drive/Dropbox/iCloud/OneDrive/Notion\", or runs /cloud-os-builder."
disable-model-invocation: true

Cloud OS — Host Selection + Setup + Onboarding

USE WHEN the user runs `/cloud-os-builder` or asks to set up a Cloud OS, or to host their second brain in a synced cloud folder (Google Drive, OneDrive, iCloud, Dropbox).

This is the **Cloud OS** tier of the AIOS family. It builds the **same structure the Local OS uses**, but inside a **synced cloud folder** so it follows the user across devices — and it **omits the Obsidian `.obsidian/` layer** (that layer does nothing without Obsidian and is the part that syncs badly on consumer cloud). This skill is **self-contained**: every reference template it needs lives in its own `references/` folder; it does not depend on any other skill.

This is a multi-step process:

• **Phase H**: Host Selection — ask which cloud and confirm the exact folder path (do this FIRST)
• **Phase 0**: Mode Selection — ask which OS variant to create
• **Phase A**: Bootstrap — create the directory structure and system files **inside the cloud folder** (skip Obsidian-specific steps)
• **Phase B**: Onboarding — interview the user and personalize everything
• **Phase C**: Cloud Sync Setup — exact provider step-by-step + verify sync

---

Phase H: Host Selection (do this first)

Two questions, via AskUserQuestion (the second only if needed). This keeps each question within the 4-option limit.

H.1 — Route

Ask: "Where do you want to host your OS?" Pass both `label` and `description`:

• **Notion** — "Build it as a Notion workspace (pages + databases with relations + a home dashboard). You operate from inside Notion; Claude reads/writes via the Notion connector. Realtime + multiplayer, but cloud-only (no local file copy)."
• **Synced cloud folder** — "A plain folder synced via Google Drive, iCloud, Dropbox, or OneDrive. Real files on disk; Claude operates it directly. Single-user, with a sync delay."

**Branch:**

• If they pick **Notion** → jump to `## Notion Route` near the bottom. **Skip Pre-flight, Phase A, and Phase C** (those are the file route). The Notion Route reuses Phase 0 and the Phase B interview.
• If they pick **Synced cloud folder** → continue with **H.2**, then Pre-flight → Phase 0 → A → B → C.

H.2 — Provider (file route only)

Ask: "Which cloud?" Pass both `label` and `description`:

• **Google Drive** — "Most free storage (15 GB); simple desktop sync."
• **iCloud** — "Best if you're all-Apple; near-realtime across Mac/iPhone/iPad."
• **Dropbox** — "Most reliable sync; best mobile path (via Remotely Save)."
• **OneDrive** — "Best if you live in Microsoft 365 / Windows."

If they're unsure, read `references/comparison.md` and recommend by their devices (Apple-only → iCloud; mobile matters → Dropbox; Microsoft shop → OneDrive; most free storage → Google Drive).

Then confirm the **exact folder path** inside that provider's synced location, and create it:

• iCloud → `~/Library/Mobile Documents/com~apple~CloudDocs/<OS-name>`
• Google Drive → `~/Google Drive/My Drive/<OS-name>`
• Dropbox → `~/Dropbox/<OS-name>`
• OneDrive → `~/OneDrive/<OS-name>`

**This cloud folder is the OS root.** `cd` into it (or treat it as the working directory) so every `./…` write path in Phase A/B below resolves **inside this folder**. Remember the chosen provider — Phase C uses it.

---

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 (file route only)

Create the directory structure and write all system files for the selected mode. (For the **Notion** route, skip this entirely — see `## Notion Route` near the bottom.)

Resolving reference file paths

Ev