landing-page-designlisted

# Landing Page Design A landing page is not a homepage. A homepage serves multiple intents. A landing page wins one intent: **one offer → one audience → one primary action.** This skill has two halves. **Part A** decides what the page says and how it is structured. **Part B** is the non negotiable visual system. Work through A before touching B. ## Scope Apply to all web UI work: landing pages, marketing sites, components, dashboards, prototypes, and design reviews. When a rule here conflicts with a framework default, this file wins. When the user's explicit prompt conflicts with a rule, the user wins. **Companion skill.** For upgrading an *existing* site rather than building a new one, use `redesign-existing-projects` ([github.com/elayadesign/redesign-skill](https://github.com/elayadesign/redesign-skill)). It diagnoses generic patterns and defers to this file for every concrete value. --- # PART A — Strategy and structure ## A1. Intake Gather these before designing or writing. Ask only for what is missing, and ask in one batch rather than one question at a time. **Purpose** - What is the ONE primary action? (trial, demo, buy, waitlist, download) - What is the offer, exactly what do they get? - What counts as a conversion? (click, signup, purchase) **Audience and context** - Who is the ICP? - What problem are they trying to solve? - Top three objections, meaning why they do not convert today - Traffic source: ads, search, social, email - What do visitors already k