Install & connect.

The engine: all skills, the shared standards, the Client Core template, the org marketplace. Public to the team, no pricing. Push here and the whole org gets it on sync.

The confidential layer: pricing, client data, proof. A separate private repo, mounted read-only in the crue House Project. The team gets every skill without it.

The Client Cores: one folder per client (clients/<slug>/) holding brand-pack, lock-ins, decisions. The Team project mounts it via Files → GitHub, selecting only that client's folder (read-only). Updated by commit (say "lock to client"), then Re-sync.

The actual deliverables: one repo per website or app (<client>-website), deployed on Vercel. The GitHub write MCP commits Cores and project files; it never writes crue-os or crue-house.

{
  "extraKnownMarketplaces": {
    "crue-os": { "source": { "source": "github", "repo": "crue-os/crue-os" }, "autoUpdate": true }
  },
  "enabledPlugins": {
    "crue-brand@crue-os": true,
    "crue-web@crue-os": true,
    "crue-product@crue-os": true,
    "crue-media@crue-os": true,
    "crue-content@crue-os": true,
    "crue-studio@crue-os": true,
    "crue-ops@crue-os": true
  }
}

Three ways to deploy it. User level (~/.claude/settings.json, paste once). Project level (.claude/settings.json committed into a crue-projects repo, so anyone who opens it gets the packs). Managed settings (MDM, zero-touch, org-wide).

Auth. Each user needs GitHub read access to crue-os/crue-os, the skills repo with no pricing. For background auto-update, set GITHUB_TOKEN (scope repo). autoUpdate keeps the packs current on startup.

Figma · Canva · Sanity · Supabase · Vercel · ClickUp · Microsoft 365 · Higgsfield. Settings → Connectors → find each → Connect → authorize the account. Enable per Project where relevant.

The hands behind lock to client: it commits Client Cores to the clients repo. Add custom connector with URL https://api.githubcopilot.com/mcp/, Connect, sign in with GitHub.

When it asks which repositories, choose only crue-os/crue-clients (and crue-projects for site code), with Contents: read and write. Never grant write to crue-os or crue-house. Enable it in each client Project. Claude Code commits via native git, so the MCP is optional there.

Add custom connector with URL https://api.mobbin.com/mcp, then Connect and sign in with your Mobbin Pro account. Per-seat login.

Add custom connector with URL https://mcp.ideogram.ai/mcp, then Connect and sign in with your Ideogram account.

The real-vector engine: vector / SVG, icon sets, brand style sets, vectorize a raster to clean SVG, backgrounds and upscale. Added org-wide as a custom connector, Connect and sign in with your Recraft account (per-account login).

Add custom connector with URL https://bexio-mcp.crue.ch/mcp, Connect, then sign in with your crue Microsoft 365 account (Entra SSO). Enabled only in the crue · House Project.

Component generation for the build. Get an API key from the 21st.dev Magic console, then:

npx @21st-dev/cli@latest install claude --api-key YOUR_KEY

Restart Claude, then use /ui in a build session. The key lives in local config, never in Git.

Captures reference sites (screenshots, structure, computed styles) and checks our own builds, the engine behind clone-from-reference and the web self-check. Ships bundled in the crue-web pack, so it auto-registers, no command to run. Needs Node 18+; the first run downloads a browser. Local only, so Code and Desktop, not the web, where the skills use the Chrome connector instead.

Real traffic and funnels, read-only. In Google Cloud: enable the Analytics Admin and Data APIs, create a Desktop OAuth client, then authorize and register:

gcloud auth application-default login \
  --scopes=https://www.googleapis.com/auth/analytics.readonly,\
https://www.googleapis.com/auth/cloud-platform \
  --client-id-file=YOUR_CLIENT.json

claude mcp add analytics-mcp --scope user \
  -e GOOGLE_APPLICATION_CREDENTIALS=PATH \
  -e GOOGLE_PROJECT_ID=PROJECT_ID \
  -- pipx run analytics-mcp

Each teammate sets up their own Google login. It sees the GA properties that account can access.

1. Generate something in the client Project: a colour, a voice, a style lock-in, a reference pack, a decision.
2. Say "lock to client". The lock-to-client skill picks the right file, applies the change in place, checks for conflicts against locked values, logs the decision.
3. It commits to crue-clients/clients/<slug>/<file>.md through the GitHub write MCP. A clean message, never a force-push, never history.
4. Sync the Project so the next chat reads the new state. The committed Core is the memory, not the chat.

The GitHub token writes to crue-clients and crue-projects only. Never crue-os or crue-house. Pricing and proof are never writable from a client chat, and one client's folder is never written from another's Project.

In Claude Code it is automatic: the repo is cloned, the skill edits the file and commits and pushes. In a Project chat the write MCP is what makes it automatic. Same loop, two surfaces.

1. Generate the Core. In crue · House, run initialize-project. Pick the client from Bexio or create them as a contact. It creates clients/<slug>/ in crue-clients from the latest template, filled, and commits it.
2. Create the Project. A new Claude Project named Client · <Name>.
3. Mount the Core. In the Team project, Files → connect GitHub → crue-os/crue-clients → select only this client's folder clients/<slug>/ (read-only) → it syncs; Re-sync to refresh. The folder picker keeps every other client out, one project sees one client. Prereq: the Claude GitHub app has access to the private repo. Set the archetype in brand-pack. (Personal project with no GitHub in Files? Upload the five files instead.)
4. Set the instructions. "This is the Client Core for <Name>. Always read brand-pack.md first. Stay within this brand. Never reference other clients or the crue House brand."
5. Enable connectors. The production tools, plus the GitHub write MCP so lock to client works: ClickUp, Figma, SharePoint, Vercel, Higgsfield. Never Bexio, it is House-only.
6. Work, then lock. Describe the task, the right skill runs and ends on the Roman Pass. Say "lock to client" to commit any result into the Core.