You installed Orbit. Here's what to ask Claude first.

01 · See what the render gate actually catches

What happens: Claude writes the test email itself, so nothing of yours is involved: no HTML to paste, no API key, no brand kit. orbit_render_gate then renders it and measures what only a real render shows: computed contrast on that faint colour, single-word last lines, CTA rows that wrap on mobile, tap targets under 44px, and bytes against Gmail's clipping limit. A minute or two, and you watch the gate fail something on purpose before you trust it with real work.

02 · Build your own lifecycle brain from an email you already send

What happens: Orbit chains the flagship path. orbit_bootstrap_brain scaffolds a git repo: operating rules, conventions, a folder per lifecycle stage. orbit_learn_email_template reads your real email and derives a module catalogue plus brand tokens: your design system, not a vendor's template gallery. orbit_generate_brain_gate then writes the pre-send gate, parameterised to your byte limits and templating branches. About 15 minutes, and you end up owning the repo.

03 · Audit a lifecycle program you already have

What happens: Orbit triggers the Lifecycle Audit skill. It asks 6–8 questions about your current programs, stack, and metrics, then produces a structured gap analysis with prioritized recommendations. About 10 minutes, mostly you answering questions.

04 · Design an onboarding flow from scratch

What happens: Orbit routes to the Stripo Email Builder skill. It scopes the program shape, how many emails, what triggers each, then writes a Notion-ready build spec: one section per email, a copy table mapped to your live Stripo modules, six pre-launch gates.

05 · Fix Braze naming conventions across your workspace

What happens: With your Braze API key connected, Orbit triggers the Braze Instance Audit skill. Pulls every canvas, campaign, and segment. Flags off-convention assets and proposes a 4-dimension naming standard you can apply to new work. Existing assets get a bulk-rename plan.

06 · Plan an IP warm-up

What happens: Orbit triggers the Braze Build Packager skill. The 14-day ramp comes back build-ready rather than as advice: a Canvas build sheet per day's send, naming conventions, and QA and test-user checklists.

07 · Build a production email end-to-end

What happens: Same skill, from the build side. Braze Build Packager owns the handoff: the win-back email comes back as an implementation bundle, asset and Content Block manifests, Liquid snippets, a test-user checklist, with the MJML from the production skill it names.