claude-landing-composer

# Claude Landing Composer Most AI-built landing pages are instantly recognizable: centered hero, three feature cards, a gradient, generic copy. This skill builds pages that don't read as generated — editorial layout, real design tokens, motion with intent, and copy that sounds like a person wrote it. Build on a design system from `claude-design-system-architect` when one exists. Run the result through `claude-design-critic` before shipping. ## Step 1 — Plan the page - **Goal & one action** — what the page must get the visitor to do. - **Audience** — pull a buyer persona from `icp-deep-scanner` if available so the copy speaks to a real reader. - **Sections** — choose the minimum that earns the goal (hero → proof → how/why → objection-handling → pricing → CTA). Cut anything that doesn't move the visitor forward. - **Tokens** — load the design system. If none exists, generate one first (`claude-design-system-architect`); do not hardcode arbitrary colors/sizes. ### Stack & house rules Next.js (App Router) + React + TypeScript + Tailwind v4 + Motion (the library formerly published as Framer Motion) — the default stack. **No purple. No emoji** — use Lucide/Heroicons. Warm/earth tones and dark surfaces welcome. Motion is expected — typewriter, animated counters, spring/stagger reveals — used with restraint. ## Step 2 — Compose section by section Build each section as a real component using tokens. For each, decide layout, content, and motion deliberately: - **Hero** — a sharp...