agentleFS
Sign inStart free
sukirman1901sukirman1901/frontend-expert/skills/marketing/SKILL.md

marketing

Skill9 starsChanged 2 months agoMITView on GitHub

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, seo, anti-slop-design.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing, research and 3 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.
  • alxyrginSkill

    writing

    Создание контента для личного бренда — статьи, посты, туториалы. Use when user asks to "напиши статью", "создай пост", "подготовь контент", "write article", "create content", or when task requires content creation for blogging, LinkedIn, Medium, or other publishing platforms.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 4 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 4 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 0

    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. Very specific:

    Use this sequence when its evidence exists.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 22 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

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
  • Tiny copy tweak on an existing section → polish
  • Pure SEO meta without layout → seo

Canonical stack (default SaaS)

Use this sequence when its evidence exists; choose an evidence-led alternative in references/landing-sections.md when it does not. Do not create unsupported proof to fill the recipe:

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

RuleDetail
Section jobsEach section has one purpose, one headline, one short support line
Hero budgetBrand (hero-level) + one headline + one lede + one CTA group + one dominant visual plane
No hero-only pageAt least Logo cloud or Features + CTA + Footer beyond the hero
Proof orderUse supplied, verified proof; product demonstration may precede or replace logos/testimonials when those are unavailable
Hand-rollImplement sections yourself — registry/block CLI install is not the pack default
Anti-slopNo 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
SEOUnique title/description/OG via seo

Workflow

  1. Confirm surface = marketing landing (not dashboard)
  2. Inventory actual facts/visuals/proof, then pick a recipe from references/landing-sections.md (or user-named section jobs); one product specimen can carry the story
  3. Tokens via decision tree (tokens) — landing surface signal OK
  4. Hand-roll sections in order; Reicon for icons (components)
  5. Responsive + full-width primary CTA <768 (responsive)
  6. Light marketing motion (motion) — not decorative spam
  7. Scan anti-slop-design + Conventions check

Checklist

  • Sequence answers understand → judge fit → act using available evidence (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: seo
Craft refs: Plasma / Send2Figma-quality heroes — atmosphere without template slop

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.

Check your setup, free