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
- Distinctive: line 20
Check that positioning, messaging, and voice are at least "draft" status
- Distinctive: line 25
If any prerequisite is missing, explain the impact: "Without voice defined, copy will be functional but may not feel distinctively …
- Distinctive: line 29
Ask or infer from business_type:
- Distinctive: line 63
Remove complexity and objections
- Distinctive: line 78
Create urgency without manipulation
- Distinctive: line 82
Add transitional CTA for undecided visitors
- Distinctive: line 86
Write every piece of copy using:
- Distinctive: line 93
Use vocabulary from the "use" list
- Distinctive: line 94
Avoid vocabulary from the "avoid" list
- Distinctive: line 99
If visual identity is defined, include:
- Distinctive: line 106
If visual identity is NOT defined, provide layout and structure without visual specifics.
- Distinctive: line 110
Run all page copy through the full checklist.
- Very specific: line 123
If the user has a codebase, offer to generate the actual HTML/JSX/component code.
≈ “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.
Files
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
- Find and read
brand-brief.md - Check that positioning, messaging, and voice are at least "draft" status
- Load references:
${CLAUDE_PLUGIN_ROOT}/references/frameworks/miller-storybrand.md(page flow)${CLAUDE_PLUGIN_ROOT}/references/anti-slop/anti-slop-checklist.md
- Note visual identity if available (colors, fonts, imagery)
- 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 Type | Primary Page Type | Primary CTA |
| SaaS | Signup / Free trial | Start free trial |
| Local service | Lead gen / Contact | Get a quote / Schedule |
| Content creator | Subscribe / Community join | Join / Subscribe |
| Ecommerce | Product / Collection | Buy / Add to cart |
| Agency | Portfolio / Contact | Schedule a call |
| Community | Membership / Join | Join 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:
- Page blueprint: Section-by-section structure with copy
- Design notes: Visual specifications per section
- 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
In this repository9 other files it gives its agents.
- brand-ad-copySkill
- brand-auditSkill
- brand-competitor-scanSkill
- brand-messagingSkill
- brand-positioningSkill
- brand-radarSkill
- brand-visual-identitySkill
- brand-voiceSkill
- startSkill
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
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.

