From vibiz
Onboard the current repo as a Vibiz brand (matches against existing vibizes first; only creates if none match)
How this command is triggered — by the user, by Claude, or both
Slash command
/vibiz:onboardThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /vibiz:onboard End-to-end flow: detect this project's URL → check for an existing vibiz → only create a new one if no match. ## Steps 1. **MCP gate.** Try `list_vibiz`. If unauthed → tell user `/mcp` → vibiz → Authenticate → re-run. Stop. 2. **Detect this project's brand URL** using the [project-match skill](../skills/project-match/SKILL.md). Same fallback chain: `package.json` `homepage` → `pyproject.toml` / `Cargo.toml` → first non-badge non-github link in README → ask user. 3. **Match against existing vibizes** (using normalized `websiteUrl` comparison from the project-match skill)....
End-to-end flow: detect this project's URL → check for an existing vibiz → only create a new one if no match.
MCP gate. Try list_vibiz. If unauthed → tell user /mcp → vibiz → Authenticate → re-run. Stop.
Detect this project's brand URL using the project-match skill. Same fallback chain: package.json homepage → pyproject.toml / Cargo.toml → first non-badge non-github link in README → ask user.
Match against existing vibizes (using normalized websiteUrl comparison from the project-match skill).
Branch on the match outcome:
Existing match found → tell the user, do NOT create another.
✓ Found an existing vibiz for <url>: "<name>" (slug: <slug>)
Reusing it. To force-create a new one, say: /vibiz:onboard --force <url>
Then list ICPs + offers from that vibiz so the user knows what's already in there.
No match → confirm with the user before creating:
I'll scrape <url> and create a new vibiz from it. This:
- generates a brand kit (colors, fonts, logo, voice)
- auto-discovers ICPs and offers
- takes ~30 seconds
Sound good? (yes / no / use a different URL)
On yes → call vibiz_create_from_url({ websiteUrl: "<url>" }). Show the returned viewUrl. Tell the user the slug for use on later commands.
No URL detected → ask: "Paste the public URL for this project, or skip."
Optional follow-up. Once a vibiz is matched OR created, ask:
Want me to (1) generate 3 ad variants now, or (2) draft a launch post about your latest commit? Map answers to
/vibiz:launchand/vibiz:postrespectively.
localhost, 127.0.0.1, *.internal, *.local, *.test) → refuse, explain the brand kit needs a public URL.--force <url> flag in $1 → skip the matching step, go straight to vibiz_create_from_url. Useful when the detected URL was wrong./vibiz:onboard --force <correct-url>.org_*).npx claudepluginhub vibiz-ai/vibiz-claude-plugin --plugin vibiz/onboardGenerates four audience-tailored onboarding guides—Contributor, Staff Engineer, Executive, Product Manager—in an onboarding/ folder with index hub.
/onboardGenerates a developer onboarding guide by scanning project configs, structure, and docs for prerequisites, setup, workflow, key concepts. Writes to docs/onboarding.md.
/onboardIndexes this folder and saves a persistent overview that future sessions pick up automatically. In a git repo this writes `codebase:onboard` (code-shape map). In a non-git folder this writes `project:onboard` (file-shape index built by deterministic extractors — no LLM at index time).
/onboardGenerates a comprehensive developer onboarding guide including architecture diagram, tech stack, setup instructions, key files, API routes, database schema, and common gotchas.
/onboardGuides new Swarm users through core concepts—outcomes, modes—and launches their first team via interactive step-by-step gates.
/onboardScans new codebase, checks context and files, classifies stack, maps architecture, sets up rules, and saves knowledge to .memory/ for building.