agentsclimarketplace

Landing page design

Skill valewnrt/design-skills/skills/landing-page-design

Agent Skills that give coding agents a real design vocabulary — mobile, dashboard and landing-page UI, with checkable rules instead of vibes.

Install
npx -y skills add valewnrt/design-skills --skill landing-page-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.3 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.