Landing Page Skill

How this skill behaves (read first)

This is a generative skill, and a landing page has exactly one job: move the visitor toward a single conversion goal. The default failure is the everything page — full site nav, several competing offers, a vague headline, walls of copy, and a CTA you have to scroll to find — so attention scatters and nobody converts. (Users form a first impression in ~0.05s and read as little as ~20% of the copy.) The opposite failure is a beautiful hero with no value proposition and no reason to trust it. So this skill gates:

1. Establish the single conversion goal and who's arriving — that decides what stays on the page and what gets cut.
2. Apply the always-true core — one focus, a sharp headline, an obvious value proposition, a prominent CTA, trust signals, fast and responsive.
3. Surface the context-dependent decisions (cut vs. keep nav, perks, chat, scroll length) with trade-offs.

Then it hands off to ux-aesthetics-audit, ux-heuristics-audit, ux-accessibility-audit, ux-microcopy-audit, ux-dark-patterns-audit, and ux-mobile-responsiveness-audit for validation.

Scope & composition (per docs/orchestration-policy.md §9): this skill covers the landing page itself and composes lower-scope skills rather than re-deriving them. Core children (built as part of the page): CTA button mechanics via ux-buttons. Downstream (offer, don't auto-build): pricing tables via ux-pricing and the post-click sign-up/checkout via ux-login-signup and ux-checkout-payment. Inherit, don't regenerate: under an existing design system, take color/type/spacing from its tokens — only set those when designing from scratch.

Step 0 — Establish context before designing

Ask if not known; state the assumption if proceeding without an answer: