Marketing landing

Skill sukirman1901/frontend-expert/skills/marketing-landing

Marketing / SaaS landing page structure — section stack (hero, logo cloud, features, gallery, testimonials, CTA, footer), not a lone hero. Use when building or auditing landing pages, marketing sites, "landing page", "homepage marketing", or when the page feels incomplete after only a hero. Hand-roll sections with pack tokens/craft — never default to installing a third-party block registry. Pair with motion, fe-seo, anti-ai-slop.From its SKILL.md

Install

npx -y skills add sukirman1901/frontend-expert --skill marketing-landing

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

One thing to look at

10 stars10 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.

SKILL.md

3.5 KB, as published. Nobody here has run it

Marketing Landing

Overview

A landing page is a stack of section jobs, not a WebGL hero with a footer. Use the section vocabulary in references/landing-sections.md.

Hand-roll HTML/CSS (or the project’s components) from that recipe. Do not answer with npx / shadcn add / @tailark/* / registry install as the default.

When to use

New marketing homepage / landing / launch page
User names section types (hero, logo cloud, features, testimonials, CTA…)
Audit says “incomplete landing” / hero-only / AI slop marketing

When to skip

App shell / dashboard chrome → app-shell-routing
Tiny copy tweak on an existing section → ui-feel
Pure SEO meta without layout → fe-seo

Canonical stack (default SaaS)

Build in this order unless the user specifies otherwise:

Header (simple) → Hero → Logo cloud → Features → Gallery (or product) →
Testimonials → CTA → Footer

Example recipe (IA labels only — not packages to install):

header · hero · logo-cloud · features · gallery · testimonials · cta · footer

Ignore obsessing over Header variants — keep header quiet; invest in Hero → Footer jobs.

MUST

Rule	Detail
Section jobs	Each section has one purpose, one headline, one short support line
Hero budget	Brand (hero-level) + one headline + one lede + one CTA group + one dominant visual plane
No hero-only page	At least Logo cloud or Features + CTA + Footer beyond the hero
Proof order	Trust (logos) before deep features when possible
Hand-roll	Implement sections yourself — registry/block CLI install is not the pack default
Anti-slop	No purple defaults, no 3 identical icon-cards as the whole Features story, no Lorem, no equal-weight CTA row in hero
Motion	≤2 families from `motion-families.md`; hand-roll; honor reduced-motion
SEO	Unique title/description/OG via `fe-seo`

Workflow

Confirm surface = marketing landing (not dashboard)
Pick a recipe from references/landing-sections.md (or user-named section jobs)
Tokens via decision tree (design-tokens) — landing surface signal OK
Hand-roll sections in order; Reicon for icons (ui-components)
Responsive + full-width primary CTA <768 (responsive-ui)
Light marketing motion (motion) — not decorative spam
Scan anti-ai-slop + Conventions check

Checklist

Stack matches a known recipe (not hero + footer only)
Hero brand is hero-level; one primary CTA
Logo cloud / features / proof present when SaaS
Gallery or product visual is real product context
Closing CTA section before footer
Footer: brand + essential links
No purple/Lorem/generic 3-card feature grid as the only Features pattern
Did not default to installing a block registry

Depth

references/landing-sections.md
Motion: motion + motion-families.md
SEO: fe-seo
Craft refs: Plasma / Send2Figma-quality heroes — atmosphere without template slop