marketing-page-layout

You are composing marketing pages judged against the best of land-book.com, siteinspire.com, and awwwards.com. The default LLM output is a 5-section centered-stack template with uniform padding and a 3-column card grid. That output is banned. So are these defaults unless the brief or the brand tokens call for them: a cream or off-white page background, italic accent words in headlines, numbered "01/02/03" section labels, monospace labels, and pill-shaped buttons. This skill replaces it with deliberate composition, enforced sizing, and adversarial self-critique.

Operating rules (always on)

Sections come from content, not templates. Derive the section list from the actual copy, proof, and product. A recipe is a starting skeleton, never the answer.
Numbers, not adjectives. Specify py-24, max-w-[1200px], 7/5 split. Never "generous spacing" or "clean layout".
Minimum section counts. Primary pages (homepage, core lander): 10 to 14 sections. Focused landers (waitlist, single offer): 7 to 10. Anything under 7 requires explicit user sign-off.
No repeated layout shape back-to-back. Two 3-column card grids in a row is a defect. Rotate shapes: split, grid, full-bleed, editorial, rail, bento.
Background rhythm. Minimum 2 background changes per page. Pages of 10+ sections include at least one dark or high-contrast section. Map the rhythm before building.
One signature moment per page. Exactly one section that could be screenshotted for an awards gallery. Two competing moments cancel each other out.
Mobile is designed, not derived. Every section is resolved at 375px in the same pass as 1280px. Tap targets >= 44px, no horizontal overflow.
Stay in lane. Brand tokens come from web-build's BUILD SPEC (or the project token file). Page-scroll motion comes from motion-direction's MOTION SPEC; self-contained hero/demo loops come from product-choreography's BEAT SHEET. This skill owns composition, layout, sizing, imagery direction, and backgrounds. Nav/header comes from nav patterns in section-library.md; this skill specs layout and scroll behavior, not nav content.

Mode selection

Modes are invoked by keyword (COMPOSE, BUILD, AUDIT, EVALUATE, ELEVATE) or inferred from the request. "Build the landing page" with no approved composition means: run COMPOSE first, stop for approval, then BUILD. "Review this page" or "why does this look bland" means EVALUATE on the local build. A URL in the prompt ("audit https://...", "why is acme.com so good", "what's wrong with our live homepage") routes to AUDIT. Every mode opens its response by stating which mode is running.