mb-setuplisted

Bootstrap a new business folder with Main Branch structure, or migrate an existing single-offer folder to multi-offer. Use when: (1) New user needs Claude Code environment configured (2) User says "set up", "get started", "initialize", "bootstrap", "create my repo", "new business" (3) User is new to Main Branch and needs full onboarding (4) Migrating existing business context into the Main Branch structure (5) User wants to add a second offer to an existing repo. Creates CLI and skill wiring, a business folder with full structure, and bounded context until core files are useful. Applies business setup patterns. Teaches concepts during setup.
noontide-co/mainbranch · ★ 27 · AI & Automation · score 78

Install: claude install-skill noontide-co/mainbranch

# Repo Setup Get a new user fully configured with Claude Code and their business repo. Use shipped `mb` commands for setup facts before teaching concepts or reading reference prose. **CLI facts first:** Run `mb doctor`, `mb start --json`, and `mb status --json --peek` when a repo exists or can be identified. Use `mb onboard status --json` as the read-only progress check for existing repos. Use `mb onboard plan` only after the operator approves writing setup progress; do not keep onboarding state only in chat prose. If there is no repo yet, inspect `mb onboard --help`, explain the target folder, ask for approval, then use `mb onboard` to create one instead of hand-rolling repo-shape checks. For provider setup, use `mb connect plan` and `mb connect doctor --json` as the durable readiness contract. Explain providers as business capabilities, not developer config, and end with exact commands. **Pasted setup guide = setup intent.** If the user pastes this guide, the beginner setup guide, or a bootstrap prompt with business/folder intent, treat it as setup intent, not as a document to save. Do not offer to save it as a document. Check `mb --version`; if missing, stop with `pipx install mainbranch`. If present, inspect `mb onboard --help`, explain the target folder, and ask before any write. **GitHub-backed setup preflight.** GitHub is strongly recommended because it gives Main Branch a free cloud backup, shared history, task/proposal layer, and connector-friendly copy of the b