Landing Page Brief — Orchestrator

Communication — Step between strategy and design. Coordinates evidence anchoring, hypothesis generation, architecture, per-section specification, asset slotting, conversion gating, and hand-off prompt composition into a single approved brief.

Core Question: "Could a designer (or Claude Design) build the right page from this brief without a single follow-up question?"

Critical Gates — Read First

• Do NOT generate a brief without brand artifacts. Missing brand/BRAND.md or brand/DESIGN.md → return NEEDS_CONTEXT. Brief depends on tokens, voice rules, sacred elements.
• Do NOT skip the conversion rubric. Every section spec is gated by this skill's local conversion-principles rules (4-U headline, message match, CTA psychology, social proof placement, objection handling, form-field discipline). Brand-good but conversion-bad = failure.
• Do NOT propose changing sacred elements. Logo geometry, primary palette anchor, tagline wording, signature treatments are "do not touch" rails, not options.
• Do NOT exceed the brief length envelope. Useful brief is 250–500 lines. <250 = insufficient depth (designer asks follow-ups). >500 = bloat (designer skims, misses spec). Critic enforces.
• Do NOT inline the full skill chain. If project has a shared chain doc (e.g., growth/page-redesigns/_prompts.md), reference by section header; add page-specific overrides only.
• Do NOT inject placeholder testimonials, fake logos, or pretend numbers. If a proof asset isn't real, spec it ("Customer logo grid, 6 cells × 60px") and note "delete cell if not real" — never fabricate.

Philosophy

Operates between strategy and design. By invocation, WHY (hypothesis) and WHO (audience) should be stable; the brief turns those into HOW (architecture + section spec + asset slots) precise enough for execution. The conversion rubric is internalized here — every section is evaluated against landing-page best practices at brief time so the page is built right rather than waiting for a separate heuristic audit.