Create & Ship
mb-site
Last updated May 25, 2026
Read-only planning in Codex
Brief, check, and improve pages from owned context before publishing.
- Sense
- Decide
- Ship
- Reflect
Usage
Use mb-site as an agent route. The route should read Main Branch facts before advice, then stay inside the approval gates for the work it recommends.
mb-site
# Claude Code, when installed
/mb-siteWhen to use it
Best for
A planning-only Codex route for page briefs, site readiness, conversion checks, and publish preparation.
Use when
- The operator asks for website or landing page work.
- A page needs offer, proof, audience, or analytics context.
- Publishing or tracking changes need a preflight plan.
Route workflow
- Read owned offer, proof, audience, and site posture.
- Identify page job, conversion path, evidence gaps, and publish blockers.
- Produce a page plan or readiness findings.
- Ask before editing site files, tracking, or publishing.
Safe fact commands
Run only the read-only facts needed for the route before recommending next work. Approval-gated commands belong in the plan, not the first move.
mb status --json --peek
mb site check --jsonCommand contract
Reads
- offers
- proof
- audience
- decisions
- analytics posture
- site files
Writes
- none in Codex by default; site plans and readiness findings only
Approval gates
- file edits in a site repo
- publishing
- tracking changes
- destructive edits
Expected output
Return
- Page job and audience.
- Readiness findings.
- Recommended changes and approval gates.
Do not
- Do not publish or mutate tracking without approval.
- Do not invent proof not present in the repo.
- Do not confuse a page plan with a reusable playbook.
Example response
The landing page needs sharper proof near the first CTA and a checkout path check before traffic is sent.