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
- GabrieleDattile/agent-superpowerstheir own version, first seen Nov 15, 2026
- furyoktria/claude-skillstheir own version, first seen Nov 8, 2026
- skygenesisenterprise/notploytheir own version, first seen Nov 1, 2026
- ArnavPuri/designskillstheir own version, first seen Nov 1, 2026
- elayadesign/ai-design-skillstheir own version, first seen Oct 30, 2026
- toribryan/design-skillstheir own version, first seen Oct 25, 2026
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.
herbert051281Skillpitch-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
VercelSkillweb-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
StrayDragonSkillui-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
VercelSkillagent-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
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- elayadesign/ai-design-skills★ 15ksame name
- KartikLabhshetwar/better-shot★ 2.4ksame name
- midudev/mcp-higgsfield-landing★ 122same name
- 2389-research/landing-page-design★ 41same name
- cm-wada-yusuke/claude-code-product-workshop-kit★ 18same name
- ArnavPuri/designskills★ 17same name
- FelipeAngeli/skills★ 2same name
- Geruyang/skills★ 2same name
- GabrieleDattile/agent-superpowers★ 1same name
- ifitsmanu/landing-studio★ 1same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- dashboard-designSkill
- mobile-app-designSkill
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
- Distinctive: line 35
The five-second test: if someone scrolled the page for five seconds, is it structured such that they'd understand the idea?
- Distinctive: line 70
Commit to a position between playful and professional, and be consistent:
- Very specific: line 111
Run references/audit-checklist.md.
“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.
Files
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 page | Dashboard | |
| Type scale | Wide range, up to ~6 sizes | Compressed, rarely >24px |
| Grid | Guideline — routinely broken on purpose | Followed strictly |
| Motion | Expressive, storytelling | Tame, user-focused |
| Color | Brand-led, decorative allowed | Comes from the data |
| Success | Conversion | Task 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:
| Vibe | Treatment |
| Playful | Blobs, bright colors, characters, neo-brutalist edges |
| Middle | Doodled illustrations, twinkles, tasteful scribbles |
| Professional | Realistic 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.
| Principle | Failing looks like |
| Contrast | No obvious focal point; everything competes equally |
| Hierarchy | Wordmark, tagline and section titles fight for the same attention |
| Alignment | Elements don't share edges or axes |
| Proximity | Related things not grouped; unrelated things jammed together |
| Repetition | Three type weights, two icon styles, four corner radii |
| Balance | Bottom-heavy or lopsided; one dense block dominates |
| Whitespace | Every pixel working; nothing breathes |
| Unity | Reads 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, overlaysreferences/color.md— the four-layer color system, dark mode, semantic color, OKLCH for themingreferences/structure.md— section anatomy, hero, the five-second test, illustration placement, pricing, social proofreferences/motion.md— easing, entrances, parallax, text animation, scroll and hover, the unexpectedreferences/reference-page.html— a working page implementing the system; read it when you need concrete structure rather than descriptionreferences/audit-checklist.md— the full review rubric
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
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.

