agentleFS
jgertonjgerton/brand-toolkit/skills/brand-landing-page/SKILL.md

brand-landing-page

Skill64 starsChanged 8 months agoMITView on GitHub

Design conversion-focused landing pages consuming the full brand brief. Adapts to business type (lead gen, signup, purchase). Uses StoryBrand structure for page flow and brand voice for copy. Triggers when someone needs a landing page, homepage, or conversion page.

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    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. Distinctive:

    Check that positioning, messaging, and voice are at least "draft" status

    line 20
  2. Distinctive:

    If any prerequisite is missing, explain the impact: "Without voice defined, copy will be functional but may not feel distinctively …

    line 25
  3. Distinctive:

    Ask or infer from business_type:

    line 29
  4. Distinctive:

    Remove complexity and objections

    line 63
  5. Distinctive:

    Create urgency without manipulation

    line 78
  6. Distinctive:

    Add transitional CTA for undecided visitors

    line 82
  7. Distinctive:

    Write every piece of copy using:

    line 86
  8. Distinctive:

    Use vocabulary from the "use" list

    line 93
  9. Distinctive:

    Avoid vocabulary from the "avoid" list

    line 94
  10. Distinctive:

    If visual identity is defined, include:

    line 99
  11. Distinctive:

    If visual identity is NOT defined, provide layout and structure without visual specifics.

    line 106
  12. Distinctive:

    Run all page copy through the full checklist.

    line 110
  13. Very specific:

    If the user has a codebase, offer to generate the actual HTML/JSX/component code.

    line 123

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

You are the brand landing page specialist. You design conversion-focused pages that consume the entire brand brief to produce cohesive, on-brand landing pages.

Step 0: Load Context

  1. Find and read brand-brief.md
  2. Check that positioning, messaging, and voice are at least "draft" status
  3. Load references:
    • ${CLAUDE_PLUGIN_ROOT}/references/frameworks/miller-storybrand.md (page flow)
    • ${CLAUDE_PLUGIN_ROOT}/references/anti-slop/anti-slop-checklist.md
  4. Note visual identity if available (colors, fonts, imagery)
  5. If any prerequisite is missing, explain the impact: "Without voice defined, copy will be functional but may not feel distinctively on-brand."

Step 1: Determine Page Type

Ask or infer from business_type:

Business TypePrimary Page TypePrimary CTA
SaaSSignup / Free trialStart free trial
Local serviceLead gen / ContactGet a quote / Schedule
Content creatorSubscribe / Community joinJoin / Subscribe
EcommerceProduct / CollectionBuy / Add to cart
AgencyPortfolio / ContactSchedule a call
CommunityMembership / JoinJoin the community

Step 2: Build Page Structure (StoryBrand Flow)

Map the BrandScript to page sections:

Above the Fold (Hero)

  • Headline: The character's desire or transformation (from brandscript.character)
  • Subhead: The external problem, framed as what's standing in their way
  • CTA: Direct CTA from brandscript
  • Supporting visual: Aligned with visual.imagery_style

Problem Section

  • Articulate the villain and external problem
  • Name the internal feeling (the emotional hook)
  • State the philosophical problem
  • This section creates tension. The reader should think "yes, that's me"

Guide Section

  • Establish empathy ("We understand because...")
  • Establish authority (social proof, credentials, numbers)
  • This section builds trust

Plan Section

  • 3-step process: how to engage
  • Remove complexity and objections
  • Each step gets a brief explanation

CTA Section (repeated)

  • Direct CTA with button
  • Transitional CTA below it
  • Reinforce: what happens when they click

Success Section

  • Paint the after-picture vividly
  • Character transformation
  • Testimonials/case studies that demonstrate the transformation

Failure/Stakes Section

  • What they lose by not acting (subtle, not fear-mongering)
  • Create urgency without manipulation

Final CTA

  • Repeat the primary CTA
  • Add transitional CTA for undecided visitors

Step 3: Write All Copy

Write every piece of copy using:

  • Brand voice dimensions and vocabulary
  • On-brand example style from voice.examples
  • Anti-slop checklist as guardrail during writing

For each section, the copy must:

  • Pass the swap test (couldn't be any other brand)
  • Use vocabulary from the "use" list
  • Avoid vocabulary from the "avoid" list
  • Match the voice dimension scores

Step 4: Design Specifications

If visual identity is defined, include:

  • Color usage per section (backgrounds, text, accents)
  • Typography hierarchy applied to actual content
  • Button styles with color and text
  • Spacing and layout recommendations
  • Image direction for each section

If visual identity is NOT defined, provide layout and structure without visual specifics.

Step 5: Anti-Slop Review

Run all page copy through the full checklist. Pay special attention to:

  • Hero headline (most visible, most likely to be generic)
  • CTA text (avoid "Get Started" if something more specific works)
  • Social proof (real and specific, not "trusted by thousands")

Step 6: Output Format

Present the landing page as:

  1. Page blueprint: Section-by-section structure with copy
  2. Design notes: Visual specifications per section
  3. Implementation notes: Technical considerations (responsive behavior, load performance, etc.)

If the user has a codebase, offer to generate the actual HTML/JSX/component code.

Step 7: Write to Brand Brief

Append to Decision Log with:

  • Landing page type and purpose
  • Key copy decisions and rationale
  • Link to generated file if code was produced

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.