Site
Pick a site shape, build it from business context, and ship it through a linked site repo. Cloudflare Pages with git auto-deploy is the default deploy path.
Shared source: The portable workflow contract lives in
workflows/mb-site/workflow.md. This Claude skill is the Claude Code shell over
that source.
Shared contract markers: Keep these aligned with the shared source.
Required commands:
mb status --json --peek
mb start --json
mb doctor repair --plan
mb connect doctor --json
mb launch check "$SITE_REPO" --business-repo "$BUSINESS_REPO" --json
mb site check "$SITE_REPO" --business-repo "$BUSINESS_REPO" --json
mb validate --cross-refs --json
mb checkpoint --plan --json
Required fact paths:
money_path
money_path.objects.proof.quality
money_path.objects.cta_path
money_path.objects.channel_strategy
money_path.objects.active_push
validation.file_contracts
content_strategy
content_strategy.overall_state
content_strategy.simple_entry_point
content_strategy.layers
ranked_actions
update
readiness
drift.items
integrations
measurement
measurement.available
measurement.state
measurement.facts.expected_events
measurement.facts.instrumentation
measurement.blocked_count
measurement.manual_count
relationship_health.gaps
checkpoint.pending
checkpoint.pending.blockers
runtime.codex_cli
runtime.claude_code
state
blocked
manual
evidence
facts.expected_events
facts.instrumentation
facts.provider_state
facts.app_stack
facts.deploy
facts.commerce
facts.email
facts.measurement
recommended_action
source
child_descriptor
Approval gates: updates_repairs_migrations, file_writes, checkpoint,
provider_mutation, publishing_or_spend, customer_contact, private_data,
destructive_operations, structured_collection, public_issue_or_proposal,
domain_purchase, dns_change, pages_project, custom_domain_attach,
deploy_or_push, and account_change.
Public/private boundaries: no_secrets, no_raw_provider_exports,
no_raw_transcripts, no_customer_member_data,
no_private_runtime_settings, no_private_dms_or_gated_communities,
no_raw_finance_legal_records, and
no_absolute_local_paths_in_committed_descriptors.
Core flow: support plan, brief, build, preview, check, publish, iterate, graduate, or recover modes.
Marker phrase: plan, brief, build, preview, check, publish, iterate, graduate, or recover.
Preserve lander, minisite, website, sales-video surface, and site repo modes;
use mb site check readiness states including ready_for_operator_review; keep
domain, DNS, Cloudflare Pages, custom-domain, deploy, publishing, provider
mutation, account changes, spend, and customer contact behind explicit gates.
Provider boundary phrase: provider mutation. Broad launch readiness uses
mb launch check; paid-traffic measurement detail uses mb site check.
Codex support stays read-only planning until runtime smoke proves site writes,
builds, deploys, and publishing.
CLI facts first: In business repo mode, run mb status --json --peek
before setup/provider/launch-readiness advice. In site repo mode or whenever a
site repo is known, run mb launch check "$SITE_REPO" --business-repo "$BUSINESS_REPO" --json for broad launch truth, then mb site check "$SITE_REPO" --business-repo "$BUSINESS_REPO" --json for paid-traffic
readiness or publish guidance.
Output destinations and operator vocabulary
Site/lander records that wrap a coordinated push (a launch, drop, or
challenge with a goal and timeline) live under pushes/<YYYY-MM-DD-slug>/
on the business-repo side; the wrapping record is push.md (type: push),
and the site record is typically pushes/<YYYY-MM-DD-slug>/site.md. Site
files themselves live in the linked site repo (Cloudflare Pages, etc.) and
are not duplicated in the business repo.
Reverse references from the site repo use the role-neutral .mainbranch/repo.json descriptor with engine push paths (linked.pushes: ["pushes/<...>/push.md"]); older site repos may still use .mainbranch/source.json (its campaign_path should point at the current push record). If core/vocabulary.md defines display words (e.g. terms.push.singular: launch), speak the operator's word while still writing engine files. Legacy campaigns/ records are migration input: run mb doctor and mb migrate campaigns --plan before relying on them or creating new push work.
When creating push.md, include the validator-required frontmatter and fill
the values from repo truth or operator answers:
---
type: push
slug: YYYY-MM-DD-slug
kind: launch
status: planned
health: unknown
goal: { metric: "", target: "", by: YYYY-MM-DD }
owner: ""
audience: ""
offer: core/offers/<offer>/offer.md
promise: ""
---
When creating or first writing a push, ask once:
"Which bet does this push serve, and which existing decision or research supports it?"
Offer active bets and recent decisions and research by name from status facts or files already read.
If this is a measurable trial with a review or cut point and no covering bet,
route to mb-bet before execution.
Accept "none yet" and continue. For a deliberate one-off with no bet, write
linked_bets: [] and a one-line no_bet_reason. On an approved write, put the
chosen repo-relative paths in linked_bets, linked_decisions, and
linked_research on the push; add its path to linked_pushes on each named
bet, decision, and research file. Leave unanswered links empty; do not invent
a reason. Mirror typed links in ## Related links as relative Markdown links.
Use docs/business-connections.md; never infer links from body-only references.
Also link named playbooks and outcomes through linked_playbooks and
linked_outcomes.
Re-Invoke Often
Say /mb-site again after compaction, context loss, or switching focus. It reloads skill context. Do it whenever the conversation feels stale.
Start Every Run
- Load
references/pull-engine-updates.md and run the standard Main Branch update check.
- Detect business repo mode vs site repo mode. Load
references/site-repo-workflow.md for repo boundaries, source links, and reverse site records.
- When a business repo is known, run
mb status --json --peek and use its readiness, drift.items, integrations, measurement, and ranked_actions facts before inventing setup, provider, or launch-readiness checks in prose.
- Before any domain purchase, DNS, Cloudflare Pages project, custom-domain attach, or deploy work, run
mb connect doctor --json from the business repo and check provider:cloudflare.
- If Cloudflare is not
ready, stop before dispatching site tools and present exactly three choices:
- connect now (in your own terminal; the token prompt is hidden):
mb connect cloudflare --metadata token_type=account --metadata account_id=... && mb connect test cloudflare. Credential entry happens in the owner's own terminal, because the hidden prompt needs a real terminal; the agent hands off, then resumes its readiness check.
- continue read-only: availability checks, naming, brief, and research only; no buy, DNS, Pages, custom-domain, or deploy calls.
- skip for now: record the blocker in the push/site notes and stage a follow-up task.
cfat_ account tokens route automatically when account_id is present; keep token_type=account in examples because it is explicit and works on older mb versions. User API tokens remain supported as a fallback by omitting token_type=account.
- Resolve the active offer and required business context with
references/site-context.md.
- When the page, sales video, or lander depends on a weak offer, load
.claude/reference/conversion/offer-sharpening.md and route to /mb-think
before writing page copy from thin claims.
6a. Conversion-mechanism gate (before any page copy): confirm what the
visitor does to convert — submit a lead form, book a call, or buy — and
specifically whether the operator takes calls. If the operator has not
stated it, STOP and ask; never assume a model. Copy is shaped by the
mechanism, so it is pinned before drafting (the brief records it; see
mb-skill-brief-draft). A real business we built lost a full day when an
agent invented a call-booking flow the operator never chose.
- When the site, blog, wiki, changelog, or launch page depends on content or
recognition strategy, read
core/content-strategy.md and relevant
core/marketing/ files if present. Owned site content should support the
same known-for target, asset jobs, channel plan, and CTA path rather than
duplicating publishable site copy into the business repo. When the goal
includes ranking, organic search traffic, keyword research, blogging for
SEO, backlinks, or AI-search visibility, load
references/seo.md before promising SEO outcomes.
- Ask what the operator is building, then load only the shape reference needed next.
Operating Principles
Four behaviors /mb-site uses on every run:
- One flow: brief to site. Do not route the operator to a separate brief skill and then ask them to come back.
/mb-site walks research, brief draft, review, lock, concept variations, publish, and iteration as one flow.
- Foreground subagents. Research, concept, and review subagents run in the foreground. Background subagents can appear to write files that do not persist.
- Parallel by default. Multiple research questions, concepts, or review passes should run in parallel.
- Publish-first, then iterate. Checkpoint the rawest durable business-repo brief and commit the rawest working site-repo concept before iterating. Git history is the memory across context clears.
When research subagents record findings, they follow the /mb-think research pattern: dated research/YYYY-MM-DD-slug-claude-code.md files with frontmatter and linked_decisions: [].
When the operator needs a broad researched brief before the site brief, run or
reuse /mb-think --brief-format=grok-8. Its eight categories feed the site
flow directly: offering, ICP, journey, competitive landscape, brand story,
technical requirements, assets, and metrics/constraints. Keep the grok-8
brief in research/; the locked site brief still belongs in decisions/.
Business-repo saves use mb checkpoint, not raw git commits. For accepted
research files, locked briefs, and reverse site records, run
mb checkpoint --plan --json, validate a subject such as
[drafted] minisite research -- <slug>, [decided] minisite brief -- <slug>,
or [connected] site repo -- <slug>, then save with
mb checkpoint --message "<subject>" --yes after operator approval. Site repo
code commits still use that site's normal git flow.
Invocation Mode
Use references/site-repo-workflow.md.
- Business repo mode: CWD has current Main Branch markers. Say: "I'm reading business context here and will create or select a site repo." If CWD looks like an old Main Branch repo, run
mb status --json --peek and/or mb doctor repair --plan before saved config or discovery. Do not write to old repo structure.
- Site repo mode: CWD has
.mainbranch/repo.json or legacy .mainbranch/source.json. Say: "I'm editing the site here and reading business context from the linked business repo."
Business repo mode plans, researches, drafts the brief, picks an offer, records push/site state, and creates or selects the site repo. Site repo mode edits code, reviews pages, previews, deploys, and runs mb site check.
Triage
Ask the operator. Do not assume.
What are you doing?
A. New site from scratch. Pick a shape.
- Lander (1 page, all-in-one). Use for focused one-off offer tests, retargeting, or paid-traffic landers. Load
references/lander-build.md.
- Minisite (~4-6 pages, static HTML). V1 default for paid-ad lander tests, single-offer first deploys, payment, lead-form, and booking funnels. Load
references/minisite-build.md.
- Website (full site, usually with build step). Static-first on Cloudflare Pages, with an optional build step. Load
references/website-build.md.
B. Iterating on an existing site.
- Editing pages, adding sections, updating copy: load the current shape build reference.
- Publishing existing work: load the current shape build reference and follow its publish step; publishing asks for approval every time (see the approval gates above).
C. Graduating to a different shape.
- Lander -> minisite, minisite -> website, website -> website + CMS. Load
references/graduation.md.
If the operator cannot articulate the shape, ask: "What goal are you trying to hit? Drive paid traffic to a sale, lead, or booking? Sell a course? Replace your current Squarespace?" Their answer maps to the shape.
Modes
| Mode |
What it does |
Load |
| setup |
First-run for a new site |
Shape build ref, then setup step |
| build |
Generate or edit content |
Current shape build ref |
| preview |
Local server/dev environment |
Current shape preview step |
| publish |
Stage, commit, push |
Current shape publish step |
| instrumentation |
Analytics, tags, booking/form widgets, and event mapping |
references/site-measurement.md |
| check |
Paid-traffic readiness |
references/site-measurement.md |
| search data |
Which queries or pages bring clicks, is a page indexed, sitemap status, sessions |
references/search-data.md |
| recover |
Resume after compaction |
references/site-recovery.md |
Reference Map
Repo + context
references/site-repo-workflow.md - business repo mode vs site repo mode, source links, reverse records.
references/site-context.md - prerequisites, active offer resolution, required core/... files, and section mapping.
.claude/reference/conversion/offer-sharpening.md - universal offer rubric, style spectrum, evidence handling, and stop conditions.
- Engine doc
docs/content-strategy.md - layered content, distribution,
channel, account, person, push, and results model.
references/sales-video.md - sales video, VSL, about-page video, lander video, and embedded pitch scripts for owned surfaces.
references/site-measurement.md - mb site check and paid-traffic readiness states.
references/search-data.md - real Search Console and GA4 numbers through mb google ... --json (queries, indexing, sitemaps, sessions); recorded site and property only.
references/seo.md - SEO doctrine: content silos, keyword selection math, PageSpeed thresholds, blog/backlink rules, AI search, the API-first data layer, and the fulfillment loop.
references/site-recovery.md - compaction recovery and scope boundaries.
Shape flows
references/lander-build.md - 1-page shape stub.
references/minisite-build.md - minisite step router.
references/website-build.md - website flow (static-first, optional build step).
references/graduation.md - paths between shapes and CMS bolt-on.
Minisite step detail: references/minisite-build.md routes each step (research, brief, setup, conversion, concept variations, build-out, publish, iterate) to its own reference; load only the current step.
Generation + design
references/minisite-generation-system.md - load-bearing system prompt for minisite generation.
references/lander-generation-system.md - one-page lander generation profile.
references/review.md - dial-gated quality gates.
references/anti-patterns.md - AI tells and generation anti-patterns.
references/archetypes.md - 9-archetype picker. Load picked detail lazily.
references/headline-formulas.md - formulas grouped by frame.
Visibility, hosting, and checks
For screenshots, fixtures and test content, follow /mb-setup references/where-data-lives.md.
Site repos default to private. Before creating a public site repo,
ask one visibility question — see the engine docs
(repo-visibility-rubric) for the rule and exact wording.
Cloudflare is the deploy rail. GitHub Pages is not part of normal Main
Branch setup; the checks-and-review model in the engine docs explains
how local mb checks, GitHub Actions, and branch protection layer.
Setup, examples, help
references/naming-heuristic.md - domain naming playbook.
references/cloudflare-pages-link.md - Cloudflare Pages GitHub App handshake.
references/examples.md - usage examples.
references/troubleshooting.md - common fixes.
1---2name: mb-site3description: "Triage and build any site shape -- lander (1 page), minisite (~4 pages), or full website -- and graduate between them. Also writes owned-surface sales videos/VSLs, about-page videos, landing-page videos, and embedded pitch scripts. Routes to per-shape build flow, reads from business context files, deploys to Cloudflare Pages with git auto-deploy. Use when:4 (1) Operator says 'I want a site' / 'I want a lander' / 'spin up a one-pager'5 (2) Setting up a new site of any shape from offer + audience material6 (3) Updating / iterating on an existing site7 (4) Graduating a site to a new shape (lander -> minisite -> website -> website + CMS)8 (5) Writing a sales video, VSL, about-page video, landing-page video, or embedded pitch script for an owned conversion surface9 (6) Checking analytics/instrumentation, GA4, GTM/dataLayer, Meta pixel, booking links, HubSpot/forms, conversion-event mapping, form-submit smoke, or paid-traffic readiness10 (7) Previewing or publishing changes1112 Triggered by: /mb-site, 'build a site', 'landing page', 'lander', 'minisite', 'website', 'I need a site', 'spin up a site', 'put this online', 'publish site', 'deploy site', 'update my site', 'graduate my site', 'add a CMS to my site', 'analytics', 'instrumentation', 'Google Analytics', 'GA4', 'GTM', 'Meta pixel', 'HubSpot form', 'Calendly', 'booking link', 'form test', 'write a VSL', 'sales video', 'about page video', 'landing page video', 'pitch script'"13loops: [ship]14metadata:15 source: https://skillmd.com/skills/dmthepm/mb-site16---1718# Site1920Pick a site shape, build it from business context, and ship it through a linked site repo. Cloudflare Pages with git auto-deploy is the default deploy path.2122**Shared source:** The portable workflow contract lives in23`workflows/mb-site/workflow.md`. This Claude skill is the Claude Code shell over24that source.2526**Shared contract markers:** Keep these aligned with the shared source.2728Required commands:2930- `mb status --json --peek`31- `mb start --json`32- `mb doctor repair --plan`33- `mb connect doctor --json`34- `mb launch check "$SITE_REPO" --business-repo "$BUSINESS_REPO" --json`35- `mb site check "$SITE_REPO" --business-repo "$BUSINESS_REPO" --json`36- `mb validate --cross-refs --json`37- `mb checkpoint --plan --json`3839Required fact paths:4041- `money_path`42- `money_path.objects.proof.quality`43- `money_path.objects.cta_path`44- `money_path.objects.channel_strategy`45- `money_path.objects.active_push`46- `validation.file_contracts`47- `content_strategy`48- `content_strategy.overall_state`49- `content_strategy.simple_entry_point`50- `content_strategy.layers`51- `ranked_actions`52- `update`53- `readiness`54- `drift.items`55- `integrations`56- `measurement`57- `measurement.available`58- `measurement.state`59- `measurement.facts.expected_events`60- `measurement.facts.instrumentation`61- `measurement.blocked_count`62- `measurement.manual_count`63- `relationship_health.gaps`64- `checkpoint.pending`65- `checkpoint.pending.blockers`66- `runtime.codex_cli`67- `runtime.claude_code`68- `state`69- `blocked`70- `manual`71- `evidence`72- `facts.expected_events`73- `facts.instrumentation`74- `facts.provider_state`75- `facts.app_stack`76- `facts.deploy`77- `facts.commerce`78- `facts.email`79- `facts.measurement`80- `recommended_action`81- `source`82- `child_descriptor`8384Approval gates: `updates_repairs_migrations`, `file_writes`, `checkpoint`,85`provider_mutation`, `publishing_or_spend`, `customer_contact`, `private_data`,86`destructive_operations`, `structured_collection`, `public_issue_or_proposal`,87`domain_purchase`, `dns_change`, `pages_project`, `custom_domain_attach`,88`deploy_or_push`, and `account_change`.8990Public/private boundaries: `no_secrets`, `no_raw_provider_exports`,91`no_raw_transcripts`, `no_customer_member_data`,92`no_private_runtime_settings`, `no_private_dms_or_gated_communities`,93`no_raw_finance_legal_records`, and94`no_absolute_local_paths_in_committed_descriptors`.9596Core flow: support plan, brief, build, preview, check, publish, iterate, graduate, or recover modes.97Marker phrase: plan, brief, build, preview, check, publish, iterate, graduate, or recover.98Preserve lander, minisite, website, sales-video surface, and site repo modes;99use `mb site check` readiness states including `ready_for_operator_review`; keep100domain, DNS, Cloudflare Pages, custom-domain, deploy, publishing, provider101mutation, account changes, spend, and customer contact behind explicit gates.102Provider boundary phrase: provider mutation. Broad launch readiness uses103`mb launch check`; paid-traffic measurement detail uses `mb site check`.104Codex support stays read-only planning until runtime smoke proves site writes,105builds, deploys, and publishing.106107**CLI facts first:** In business repo mode, run `mb status --json --peek`108before setup/provider/launch-readiness advice. In site repo mode or whenever a109site repo is known, run `mb launch check "$SITE_REPO" --business-repo110"$BUSINESS_REPO" --json` for broad launch truth, then `mb site check111"$SITE_REPO" --business-repo "$BUSINESS_REPO" --json` for paid-traffic112readiness or publish guidance.113114## Output destinations and operator vocabulary115116Site/lander records that wrap a coordinated push (a launch, drop, or117challenge with a goal and timeline) live under `pushes/<YYYY-MM-DD-slug>/`118on the business-repo side; the wrapping record is `push.md` (`type: push`),119and the site record is typically `pushes/<YYYY-MM-DD-slug>/site.md`. Site120files themselves live in the linked site repo (Cloudflare Pages, etc.) and121are not duplicated in the business repo.122123Reverse references from the site repo use the role-neutral `.mainbranch/repo.json` descriptor with engine push paths (`linked.pushes: ["pushes/<...>/push.md"]`); older site repos may still use `.mainbranch/source.json` (its `campaign_path` should point at the current push record). If `core/vocabulary.md` defines display words (e.g. `terms.push.singular: launch`), speak the operator's word while still writing engine files. Legacy `campaigns/` records are migration input: run `mb doctor` and `mb migrate campaigns --plan` before relying on them or creating new push work.124125When creating `push.md`, include the validator-required frontmatter and fill126the values from repo truth or operator answers:127128```yaml129---130type: push131slug: YYYY-MM-DD-slug132kind: launch133status: planned134health: unknown135goal: { metric: "", target: "", by: YYYY-MM-DD }136owner: ""137audience: ""138offer: core/offers/<offer>/offer.md139promise: ""140---141```142143When creating or first writing a push, ask once:144"Which bet does this push serve, and which existing decision or research supports it?"145Offer active bets and recent decisions and research by name from status facts or files already read.146If this is a measurable trial with a review or cut point and no covering bet,147route to `mb-bet` before execution.148Accept "none yet" and continue. For a deliberate one-off with no bet, write149`linked_bets: []` and a one-line `no_bet_reason`. On an approved write, put the150chosen repo-relative paths in `linked_bets`, `linked_decisions`, and151`linked_research` on the push; add its path to `linked_pushes` on each named152bet, decision, and research file. Leave unanswered links empty; do not invent153a reason. Mirror typed links in `## Related links` as relative Markdown links.154Use docs/business-connections.md; never infer links from body-only references.155Also link named playbooks and outcomes through `linked_playbooks` and156`linked_outcomes`.157158## Re-Invoke Often159160Say `/mb-site` again after compaction, context loss, or switching focus. It reloads skill context. Do it whenever the conversation feels stale.161162## Start Every Run1631641. Load [`references/pull-engine-updates.md`](references/pull-engine-updates.md) and run the standard Main Branch update check.1652. Detect business repo mode vs site repo mode. Load [`references/site-repo-workflow.md`](references/site-repo-workflow.md) for repo boundaries, source links, and reverse site records.1663. When a business repo is known, run `mb status --json --peek` and use its `readiness`, `drift.items`, `integrations`, `measurement`, and `ranked_actions` facts before inventing setup, provider, or launch-readiness checks in prose.1674. Before any domain purchase, DNS, Cloudflare Pages project, custom-domain attach, or deploy work, run `mb connect doctor --json` from the business repo and check `provider:cloudflare`.168 - If Cloudflare is not `ready`, stop before dispatching site tools and present exactly three choices:169 - **connect now (in your own terminal; the token prompt is hidden):** `mb connect cloudflare --metadata token_type=account --metadata account_id=... && mb connect test cloudflare`. Credential entry happens in the owner's own terminal, because the hidden prompt needs a real terminal; the agent hands off, then resumes its readiness check.170 - **continue read-only:** availability checks, naming, brief, and research only; no buy, DNS, Pages, custom-domain, or deploy calls.171 - **skip for now:** record the blocker in the push/site notes and stage a follow-up task.172 - `cfat_` account tokens route automatically when `account_id` is present; keep `token_type=account` in examples because it is explicit and works on older `mb` versions. User API tokens remain supported as a fallback by omitting `token_type=account`.1735. Resolve the active offer and required business context with [`references/site-context.md`](references/site-context.md).1746. When the page, sales video, or lander depends on a weak offer, load175 `.claude/reference/conversion/offer-sharpening.md` and route to `/mb-think`176 before writing page copy from thin claims.1776a. **Conversion-mechanism gate (before any page copy):** confirm what the178 visitor does to convert — submit a lead form, book a call, or buy — and179 specifically whether the operator takes calls. If the operator has not180 stated it, STOP and ask; never assume a model. Copy is shaped by the181 mechanism, so it is pinned before drafting (the brief records it; see182 `mb-skill-brief-draft`). A real business we built lost a full day when an183 agent invented a call-booking flow the operator never chose.1847. When the site, blog, wiki, changelog, or launch page depends on content or185 recognition strategy, read `core/content-strategy.md` and relevant186 `core/marketing/` files if present. Owned site content should support the187 same known-for target, asset jobs, channel plan, and CTA path rather than188 duplicating publishable site copy into the business repo. When the goal189 includes ranking, organic search traffic, keyword research, blogging for190 SEO, backlinks, or AI-search visibility, load191 [`references/seo.md`](references/seo.md) before promising SEO outcomes.1928. Ask what the operator is building, then load only the shape reference needed next.193194## Operating Principles195196Four behaviors `/mb-site` uses on every run:1971981. **One flow: brief to site.** Do not route the operator to a separate brief skill and then ask them to come back. `/mb-site` walks research, brief draft, review, lock, concept variations, publish, and iteration as one flow.1992. **Foreground subagents.** Research, concept, and review subagents run in the foreground. Background subagents can appear to write files that do not persist.2003. **Parallel by default.** Multiple research questions, concepts, or review passes should run in parallel.2014. **Publish-first, then iterate.** Checkpoint the rawest durable business-repo brief and commit the rawest working site-repo concept before iterating. Git history is the memory across context clears.202203When research subagents record findings, they follow the `/mb-think` research pattern: dated `research/YYYY-MM-DD-slug-claude-code.md` files with frontmatter and `linked_decisions: []`.204When the operator needs a broad researched brief before the site brief, run or205reuse `/mb-think --brief-format=grok-8`. Its eight categories feed the site206flow directly: offering, ICP, journey, competitive landscape, brand story,207technical requirements, assets, and metrics/constraints. Keep the `grok-8`208brief in `research/`; the locked site brief still belongs in `decisions/`.209210Business-repo saves use `mb checkpoint`, not raw git commits. For accepted211research files, locked briefs, and reverse site records, run212`mb checkpoint --plan --json`, validate a subject such as213`[drafted] minisite research -- <slug>`, `[decided] minisite brief -- <slug>`,214or `[connected] site repo -- <slug>`, then save with215`mb checkpoint --message "<subject>" --yes` after operator approval. Site repo216code commits still use that site's normal git flow.217218## Invocation Mode219220Use [`references/site-repo-workflow.md`](references/site-repo-workflow.md).221222- **Business repo mode:** CWD has current Main Branch markers. Say: "I'm reading business context here and will create or select a site repo." If CWD looks like an old Main Branch repo, run `mb status --json --peek` and/or `mb doctor repair --plan` before saved config or discovery. Do not write to old repo structure.223- **Site repo mode:** CWD has `.mainbranch/repo.json` or legacy `.mainbranch/source.json`. Say: "I'm editing the site here and reading business context from the linked business repo."224225Business repo mode plans, researches, drafts the brief, picks an offer, records push/site state, and creates or selects the site repo. Site repo mode edits code, reviews pages, previews, deploys, and runs `mb site check`.226227## Triage228229Ask the operator. Do not assume.230231> **What are you doing?**232>233> **A. New site from scratch.** Pick a shape.234> - **Lander** (1 page, all-in-one). Use for focused one-off offer tests, retargeting, or paid-traffic landers. Load [`references/lander-build.md`](references/lander-build.md).235> - **Minisite** (~4-6 pages, static HTML). V1 default for paid-ad lander tests, single-offer first deploys, payment, lead-form, and booking funnels. Load [`references/minisite-build.md`](references/minisite-build.md).236> - **Website** (full site, usually with build step). Static-first on Cloudflare Pages, with an optional build step. Load [`references/website-build.md`](references/website-build.md).237>238> **B. Iterating on an existing site.**239> - Editing pages, adding sections, updating copy: load the current shape build reference.240> - Publishing existing work: load the current shape build reference and follow its publish step; publishing asks for approval every time (see the approval gates above).241>242> **C. Graduating to a different shape.**243> - Lander -> minisite, minisite -> website, website -> website + CMS. Load [`references/graduation.md`](references/graduation.md).244245If the operator cannot articulate the shape, ask: "What goal are you trying to hit? Drive paid traffic to a sale, lead, or booking? Sell a course? Replace your current Squarespace?" Their answer maps to the shape.246247## Modes248249| Mode | What it does | Load |250|---|---|---|251| setup | First-run for a new site | Shape build ref, then setup step |252| build | Generate or edit content | Current shape build ref |253| preview | Local server/dev environment | Current shape preview step |254| publish | Stage, commit, push | Current shape publish step |255| instrumentation | Analytics, tags, booking/form widgets, and event mapping | [`references/site-measurement.md`](references/site-measurement.md) |256| check | Paid-traffic readiness | [`references/site-measurement.md`](references/site-measurement.md) |257| search data | Which queries or pages bring clicks, is a page indexed, sitemap status, sessions | [`references/search-data.md`](references/search-data.md) |258| recover | Resume after compaction | [`references/site-recovery.md`](references/site-recovery.md) |259260## Reference Map261262**Repo + context**263264- [`references/site-repo-workflow.md`](references/site-repo-workflow.md) - business repo mode vs site repo mode, source links, reverse records.265- [`references/site-context.md`](references/site-context.md) - prerequisites, active offer resolution, required `core/...` files, and section mapping.266- `.claude/reference/conversion/offer-sharpening.md` - universal offer rubric, style spectrum, evidence handling, and stop conditions.267- Engine doc `docs/content-strategy.md` - layered content, distribution,268 channel, account, person, push, and results model.269- [`references/sales-video.md`](references/sales-video.md) - sales video, VSL, about-page video, lander video, and embedded pitch scripts for owned surfaces.270- [`references/site-measurement.md`](references/site-measurement.md) - `mb site check` and paid-traffic readiness states.271- [`references/search-data.md`](references/search-data.md) - real Search Console and GA4 numbers through `mb google ... --json` (queries, indexing, sitemaps, sessions); recorded site and property only.272- [`references/seo.md`](references/seo.md) - SEO doctrine: content silos, keyword selection math, PageSpeed thresholds, blog/backlink rules, AI search, the API-first data layer, and the fulfillment loop.273- [`references/site-recovery.md`](references/site-recovery.md) - compaction recovery and scope boundaries.274275**Shape flows**276277- [`references/lander-build.md`](references/lander-build.md) - 1-page shape stub.278- [`references/minisite-build.md`](references/minisite-build.md) - minisite step router.279- [`references/website-build.md`](references/website-build.md) - website flow (static-first, optional build step).280- [`references/graduation.md`](references/graduation.md) - paths between shapes and CMS bolt-on.281282**Minisite step detail:** [`references/minisite-build.md`](references/minisite-build.md) routes each step (research, brief, setup, conversion, concept variations, build-out, publish, iterate) to its own reference; load only the current step.283284**Generation + design**285286- [`references/minisite-generation-system.md`](references/minisite-generation-system.md) - load-bearing system prompt for minisite generation.287- [`references/lander-generation-system.md`](references/lander-generation-system.md) - one-page lander generation profile.288- [`references/review.md`](references/review.md) - dial-gated quality gates.289- [`references/anti-patterns.md`](references/anti-patterns.md) - AI tells and generation anti-patterns.290- [`references/archetypes.md`](references/archetypes.md) - 9-archetype picker. Load picked detail lazily.291- [`references/headline-formulas.md`](references/headline-formulas.md) - formulas grouped by frame.292293**Visibility, hosting, and checks**294295- For screenshots, fixtures and test content, follow `/mb-setup` `references/where-data-lives.md`.296297- Site repos default to **private**. Before creating a public site repo,298 ask one visibility question — see the engine docs299 (repo-visibility-rubric) for the rule and exact wording.300- Cloudflare is the deploy rail. GitHub Pages is not part of normal Main301 Branch setup; the checks-and-review model in the engine docs explains302 how local `mb` checks, GitHub Actions, and branch protection layer.303304**Setup, examples, help**305306- [`references/naming-heuristic.md`](references/naming-heuristic.md) - domain naming playbook.307- [`references/cloudflare-pages-link.md`](references/cloudflare-pages-link.md) - Cloudflare Pages GitHub App handshake.308- [`references/examples.md`](references/examples.md) - usage examples.309- [`references/troubleshooting.md`](references/troubleshooting.md) - common fixes.