agentleFS
valewnrtvalewnrt/design-skills/skills/landing-page-design/SKILL.md

landing-page-design

Skill2 starsChanged 4 months agoMITView on GitHub

Design and review marketing sites and landing pages — hero sections, section rhythm, scroll and hover motion, illustrations, personality, copy tone, pricing and 404 pages. Use when building or improving a marketing page, when a site reads as sterile corporate AI mush, or when asked to "build a landing page", "make the homepage better", "this looks generic", or "improve conversion". For logged-in product UI use dashboard-design instead.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pitch-deck-visuals, web-design-guidelines and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • herbert051281Skill

    pitch-deck-visuals

    Investor pitch deck structure with slide-by-slide framework, visual design rules, and data presentation. Covers the 12-slide framework, chart types, team slides, and common investor turn-offs. Use for: fundraising decks, investor presentations, startup pitch, demo day, grant proposals. Triggers: pitch deck, investor deck, startup pitch, fundraising deck, demo day, pitch presentation, investor presentation, seed deck, series a deck, pitch slides, startup presentation, vc pitch, investor meeting

    Also in 3 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

  • VercelSkill

    agent-browser

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    The five-second test: if someone scrolled the page for five seconds, is it structured such that they'd understand the idea?

    line 35
  2. Distinctive:

    Commit to a position between playful and professional, and be consistent:

    line 70
  3. Very specific:

    Run references/audit-checklist.md.

    line 111

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Landing Page Design

Marketing pages have a different job from product UI: guide someone to an action, not maximize information density. For the logged-in surface, use dashboard-design.

The two failure modes sit at opposite ends:

  • Chaotic — too many components, crammed not crafted, everything competing
  • Sterile — corporate AI mush, technically fine, completely forgettable

Somewhere along the way "modern" became a synonym for sterile. The goal is structure plus personality.

How landing pages differ from product UI

Landing pageDashboard
Type scaleWide range, up to ~6 sizesCompressed, rarely >24px
GridGuideline — routinely broken on purposeFollowed strictly
MotionExpressive, storytellingTame, user-focused
ColorBrand-led, decorative allowedComes from the data
SuccessConversionTask efficiency

Build pipeline

1. Structure before personality

The five-second test: if someone scrolled the page for five seconds, is it structured such that they'd understand the idea?

Wireframe it with the content removed. One version will have blocks of text, simple illustrations and bold numbers. The other will have text split into fragments, multiple popups, small ornamentation and complex shapes. You can tell instantly which is followable — and the complex one is not the sophisticated one.

Restraint in structure wins. A clear grid-driven layout with generous space around the text beats a busy one, and it isn't a function of having a simpler product — plenty of complex offerings have clear sites.

Say what the product is. A company name in the corner at 12px is not positioning. If a project management tool reads like a wellness retreat ad, the hierarchy is wrong: lead with the value, show the actual product.

2. Then add personality

Removing everything from a busy page doesn't make it clearer — it makes it empty. The elements were carrying context. Without reading a word, illustrations of money, an invoice and a coin tell you what the product is for.

The distinction is context vs. clutter, and it comes down to spacing:

  • Maintain generous space around the text — that's what keeps supporting elements reading as context
  • Draw the eye toward the center. Elements should trail off the further they get from it
  • Know when to stop. There is a real line; one illustration too many crosses it, and you'll feel it before you can name it
  • Since you're breaking the grid deliberately, be selective about arrangement. There's a lot of eyeballing — tilt something wrong and it just looks off

3. Pick a point on the spectrum

Commit to a position between playful and professional, and be consistent:

VibeTreatment
PlayfulBlobs, bright colors, characters, neo-brutalist edges
MiddleDoodled illustrations, twinkles, tasteful scribbles
ProfessionalRealistic imagery, restrained palette, product screenshots

Then honor it everywhere — including the 404 page.

4. Motion that earns its place

Static is fine. But "just because things don't have to move doesn't mean they shouldn't."

The test for every animation: does it draw attention to the product, or to itself?

Good: an image that morphs and transitions into the next section as you scroll, deliberately pulling attention to the product and giving a first real look at it. Bad: complex animations that exist to be complex, making navigation harder.

See references/motion.md for the full catalogue — entrances, parallax, text animation, hover, scroll-triggered reveals.

5. Write like a person

Text is ~80% of most sites and it's usually the least considered part.

  • "We sweat the details" beats "We take pride in our attention to detail"
  • Natural language beats corporate jargon everywhere
  • Friendly copy is a design decision, not a copywriting afterthought

6. Finish the edges

Design is often more about the things you don't see. The 404 page is the ultimate place to be quirky — the user literally doesn't belong there. Also: empty search results, form validation, the pricing page's fine print.

7. Audit

Run references/audit-checklist.md. Screenshot the page and grade it — balance, whitespace and unity can't be judged from source.

The critique vocabulary

Grade any page against these eight. They're the ingredients of "I know it when I see it" — detailed treatment in references/foundations.md.

PrincipleFailing looks like
ContrastNo obvious focal point; everything competes equally
HierarchyWordmark, tagline and section titles fight for the same attention
AlignmentElements don't share edges or axes
ProximityRelated things not grouped; unrelated things jammed together
RepetitionThree type weights, two icon styles, four corner radii
BalanceBottom-heavy or lopsided; one dense block dominates
WhitespaceEvery pixel working; nothing breathes
UnityReads as a template with content poured in

Unity is what emerges when the other seven agree — if a page reads as generic, one of them is failing. Find which.

Reference files

  • references/foundations.md — the eight principles, hierarchy, spacing, type, icons, shadows, overlays
  • references/color.md — the four-layer color system, dark mode, semantic color, OKLCH for theming
  • references/structure.md — section anatomy, hero, the five-second test, illustration placement, pricing, social proof
  • references/motion.md — easing, entrances, parallax, text animation, scroll and hover, the unexpected
  • references/reference-page.html — a working page implementing the system; read it when you need concrete structure rather than description
  • references/audit-checklist.md — the full review rubric

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.