agentleFS
SirCharanSirCharan/claude-code-harness/skills/marketing-microsite-design/SKILL.md

marketing-microsite-design

Skill0 starsChanged 5 months agoMITView on GitHub

Design recipes for marketing / landing / GTM microsites (product launches, pitch sites, campaign pages) built on Next.js + Tailwind + Vercel — e.g. a product launch page, a research landing, a margin/pricing comparison page. Covers the proven hero structure, section order, CTA hierarchy, social proof, pricing tables, conversion best-practices, entrance/scroll motion, font pairings, and the Bento/Minimal/Aurora look. Load alongside the `design-system` skill (it owns tokens, a11y, motion mechanics). Trigger on: "landing page", "marketing site", "GTM microsite", "launch page", "pitch site", "hero section", "pricing page", "convert", or styling a product-marketing page.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Place the CTA *beside the value statement*, not floating alone.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Marketing / Microsite Design

Pair with design-system (foundations + premium checklist) and layout-interaction-design (CTA/ button placement §2, nav §3, scroll/entrance states §4). This skill = layout, conversion, and the marketing look. ✅ strong consensus · ◐ situational.

Hero — above the fold ✅ (element order)

  1. Eyebrow/kicker — often a social-proof micro-line ("Used by 5,000+ traders").
  2. Headline — one idea, <10 words, benefit not feature.
  3. Subhead — 1–2 lines clarifying the headline.
  4. Primary CTA + optional secondary (ghost) CTA.
  5. Product visual (screenshot/loop) above the fold.
  6. Trust strip (logos/rating) right under the fold line.

CTA hierarchy ✅

  • One primary action, repeated identically at top, mid (after proof), and bottom; sticky CTA on mobile. Don't invent a new primary verb per section.
  • Secondary CTA is visually subordinate (ghost/text), never a competing color.
  • Place the CTA beside the value statement, not floating alone. ◐ On focused landing pages, strip the top nav to reduce exits.

Section rhythm ✅

Hero → value prop → how-it-works (3 steps) → benefits/features → social proof → pricing → FAQ → final CTA. One idea per section; alternate background shades (--bg / --surface) to segment.

Social proof ✅

Twice minimum: a logo/rating strip high (under hero) + testimonials/case studies near each CTA. Specific numbers ("5,000 users", "4.8★") beat vague praise.

Pricing tables ✅

  • 3 tiers (anchoring; most pick tier 2). Highlight the recommended/middle plan — contrasting border + "Most Popular" badge is the single most reliable conversion lever.
  • Checkmark feature grid for scanning; monthly/annual toggle; page must load <2s. ◐ A high "Enterprise / Contact us" tier anchors even if few choose it.

Conversion specifics ✅

Message-match the inbound ad/headline; remove distractions; benefit-first copy; speed = conversion (~7–10% drop per added second). Optimize the hero image; lazy-load below the fold.

Motion ✅

  • Baseline: subtle fade-up on enter via IntersectionObserver (not scroll listeners); stagger cards 30–50ms; durations <700ms (micro <300ms). Animate transform + opacity only.
  • Scroll-driven effects via CSS animation-timeline: view() where supported; graceful fallback.
  • Always gate behind prefers-reduced-motion — reduced users get instant content, same function.

Type & look

  • Fonts: characterful display + clean body. Pairs: Bricolage Grotesque + Geist · Fraunces (opsz) + Inter · Space Grotesk + IBM Plex Sans. Bigger ratio (1.333) for drama; tracking -0.02 to -0.03em on the hero headline; text-wrap: balance on headings.
  • Style: ✅ Bento grid + Minimalism for the bones; ◐ one Aurora/mesh or Glassmorphism accent in the hero (≤3 complementary gradient stops) for a distinctive, non-templated moment. Neo-brutalism only if "bold challenger" is the explicit brief — it reads unserious for a fintech pitch.
  • Light vs dark ◐: default light for broad B2B/consumer trust; dark fits dev-tools/crypto identity. Support both; keep contrast.

Pitfalls

Multiple competing CTAs · feature-listing instead of benefit copy · stock-photo heroes (use real product shots) · motion that delays content · pricing with >3 tiers · slow LCP from an unoptimized hero image.

Sources

goprimer.com (hero formula) · involve.me (landing structure) · saashero.net (CTA placement) · kinde.com & designstudiouiux.com (pricing that converts) · motion.dev & joshwcomeau.com (scroll motion).

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.