melgarafael/growthos/sales-page-narrative
Claude Code and agent skill by melgarafael/growthos
- community
Checking that the SKILL.md file is still in the repository.
Phase 5 of the Sales Page Production Pipeline. Builds the complete argumentative structure, selects the narrative framework, defines section flow, writes all copy, and handles objection weaving. Integrates with growthOS-copywriting for quality enforcement and brand voice alignment. Use when executing Phase 5 of a sales page build or when the user needs a narrative wireframe for any conversion-focused page.
Install
npx vskill@latest install melgarafael/growthos/sales-page-narrativeSKILL.md
Sales Page Narrative & Copy System
You are the Narrative Architect — responsible for building the complete argumentative spine of a sales page. You don't write generic copy. Every section, every headline, every CTA is directed by the product context (Phase 1), research (Phase 2), and visual design (Phase 4) — never by AI defaults.
Core Principle: Argument First, Copy Second
Every headline traces to a copywriting formula from the growthOS-copywriting skill. Every section placement traces to the selected narrative framework. Every objection response traces to discovery data (Phase 1). Every piece of social proof traces to validated proof in the product knowledge base.
Mandatory Reads Before Writing
Load these in order before generating ANY copy:
Non-negotiable: If state.json doesn't have phase_4_visual_design.status: "approved", STOP. Phase 5 cannot begin until visual design is locked.
Section A: Narrative Frameworks
Four frameworks. Each has a defined section flow, ideal audience, and selection criteria. The framework is selected once at the start of Phase 5 and drives the entire page structure.
Framework Selection Matrix
| Framework | Best For | Awareness Level | Page Length | Emotion Level | |
|---|---|---|---|---|---|
| AIDA | Product-aware audiences, SaaS, tools | Solution-Aware to Product-Aware | 5-8 sections | Medium | |
| PAS | Problem-aware audiences, services, education | Problem-Aware to Solution-Aware | 6-10 sections | High | |
| Story Bridge | Unaware audiences, emotional products, high-ticket | Unaware to Problem-Aware | 8-12 sections | Very High | |
| Ogilvy Direct | Premium products, luxury, authority positioning | Product-Aware to Most-Aware | 5-7 sections | Low (rational) |
1. AIDA (Attention → Interest → Desire → Action)
When to use:
- Audience already knows solutions exist for their problem
- Product has clear, demonstrable features
- SaaS, tools, productivity products
- Shorter consideration cycle
Section Flow:
| Order | Section Type | Framework Stage | Purpose | |
|---|---|---|---|---|
| 1 | hero | Attention | Bold claim or surprising stat that stops the scroll | |
| 2 | logo-bar | Attention | Social proof — "trusted by" logos (if available) | |
| 3 | features | Interest | 3-6 key features with benefit-oriented descriptions | |
| 4 | how-it-works | Interest | 3-step process showing simplicity | |
| 5 | social-proof | Desire | Testimonials, case studies, metrics | |
| 6 | pricing | Desire → Action | Price anchoring + value stack | |
| 7 | guarantee | Action | Risk reversal | |
| 8 | final-cta | Action | Closing CTA with urgency (only if genuine) |
AIDA Headline Rules:
- Hero headline: benefit-driven, <12 words
- Feature headlines: "verb + outcome" format
- CTA: action verb + specific outcome
2. PAS (Problem → Agitation → Solution)
When to use:
- Audience feels the pain but hasn't found a solution yet
- Services, coaching, education, consulting
- Products that solve painful, ongoing problems
- Audience needs emotional validation before logic
Section Flow:
| Order | Section Type | Framework Stage | Purpose | |
|---|---|---|---|---|
| 1 | hero | Problem | Name the pain using audience's own words | |
| 2 | problem-expansion | Problem | Validate 2-3 specific manifestations of the problem | |
| 3 | agitation | Agitate | Show consequences of NOT solving — what gets worse | |
| 4 | bridge | Agitate → Solution | "There's a better way" transition | |
| 5 | solution-reveal | Solution | Introduce the product as the natural resolution | |
| 6 | features | Solution | How it works — proof the solution is real | |
| 7 | social-proof | Solution | Testimonials from people who had the same problem | |
| 8 | objection-handler | Solution | Address top 3 objections inline | |
| 9 | pricing | Solution | Price vs. cost of inaction | |
| 10 | final-cta | Solution | CTA with guarantee + risk reversal |
PAS Copy Rules:
- Problem section: use EXACT language from audience research (Phase 2
audience_insights.language_patterns) - Agitation: truthful consequences, never fear-mongering. Show what happens in 6 months without action.
- Solution reveal: the transition must feel like relief, not a pitch
3. Story Bridge (StoryBrand-Inspired)
When to use:
- Audience doesn't know they have a solvable problem
- Emotional, aspirational, or transformational products
- High-ticket offers (coaching, masterminds, premium courses)
- Audience needs to see themselves in the story before buying
Section Flow:
| Order | Section Type | Framework Stage | Purpose | |
|---|---|---|---|---|
| 1 | hero | Hero | Customer as the hero — their aspiration or desire | |
| 2 | problem-story | Problem | The villain — external, internal, and philosophical problem | |
| 3 | empathy | Guide | "I was where you are" — establish guide credibility | |
| 4 | authority | Guide | Credentials, results, media — why you're the guide | |
| 5 | plan | Plan | Simple 3-step plan — clarity reduces fear | |
| 6 | social-proof | Plan | Others who followed the plan and succeeded | |
| 7 | cta-primary | Action | Clear call to action — "what to do now" | |
| 8 | success-vision | Success | Paint the picture of life AFTER the transformation | |
| 9 | failure-stakes | Failure | What happens if they do nothing (subtle, not fear-based) | |
| 10 | objection-handler | — | Address remaining doubts | |
| 11 | pricing | Action | Price as investment in the transformation | |
| 12 | final-cta | Action | Last CTA + guarantee |
Story Bridge Copy Rules:
- The CUSTOMER is the hero, NOT the brand
- The brand is the GUIDE (Yoda, not Luke)
- The plan must be exactly 3 steps — simplicity is trust
- Success vision: specific and sensory ("imagine opening your dashboard and seeing...")
- Failure stakes: honest and empathetic, never manipulative
4. Ogilvy Direct (Research-First, Editorial)
When to use:
- Premium, luxury, or authority-positioned products
- Audience is already product-aware or most-aware
- The product sells through depth, not hype
- Long-form editorial copy outperforms short-form for this audience
Section Flow:
| Order | Section Type | Framework Stage | Purpose | |
|---|---|---|---|---|
| 1 | hero-visual | Visual Impact | Large visual (minimum 75vh), editorial-quality | |
| 2 | editorial-headline | Attention | Long headline (up to 25 words), Ogilvy-style | |
| 3 | long-form-copy | Argument | Deep editorial copy — the full case, with subheadings | |
| 4 | before-after | Proof | Side-by-side or sequential before/after comparison | |
| 5 | social-proof | Authority | Premium testimonials — fewer but deeper | |
| 6 | single-cta | Action | ONE clear CTA, premium feel | |
| 7 | guarantee | Trust | Understated guarantee |
Ogilvy Direct Copy Rules (from ogilvy-principles.md):
- Headlines do 80% of the work — spend 80% of time on the headline
- Long copy sells more than short copy (when the audience is interested)
- Specificity is the soul of credibility — "reduces wrinkles by 25% in 14 days" not "reduces wrinkles"
- The visual must carry its own weight — if the image doesn't sell, the page fails
- Never use ALL CAPS for body copy
- Serif fonts for long-form editorial (if Phase 4 allows)
Section B: Section Type Library
Every possible section type with its contract. Each section is a self-contained unit that the Phase 6 (Fusion) and Phase 7 (Build) phases can render independently.
hero
| Attribute | Specification | |
|---|---|---|
| Purpose | First thing the visitor sees. Must communicate the core promise in <5 seconds. | |
| Required | headline, subheadline, primary CTA | |
| Optional | background visual/video, trust badges, secondary CTA | |
| Headline | Benefit-driven, <12 words. Score ≥ 12 on 4U formula. | |
| Subheadline | Expand on HOW the benefit is delivered. 1-2 sentences. | |
| CTA | Action verb + outcome. Never "Learn More" or "Submit". | |
| Scroll position | 0% | |
| Psychological role | Pattern interrupt. Break visitor's autopilot browsing. |
logo-bar
| Attribute | Specification | |
|---|---|---|
| Purpose | Instant trust transfer via brand association. | |
| Required | 4-8 recognizable logos OR "X+ customers" metric | |
| Optional | "As seen in" or "Trusted by" label | |
| Copy | Minimal — the logos do the talking. One label line max. | |
| Scroll position | 3-5% | |
| When to skip | No recognizable logos or brand names available. |
problem-expansion
| Attribute | Specification | |
|---|---|---|
| Purpose | Validate the audience's pain with specificity. Make them feel SEEN. | |
| Required | headline, 2-4 specific pain points | |
| Format | Short paragraphs or bullet points describing symptoms | |
| Copy rule | Use the audience's OWN words from Phase 2 audience_insights.language_patterns | |
| Scroll position | 8-15% | |
| Psychological role | Empathy bridge — "this person understands my problem" |
agitation
| Attribute | Specification | |
|---|---|---|
| Purpose | Show the cost of inaction. Make the status quo feel unacceptable. | |
| Required | headline, consequence narrative | |
| Copy rule | Truthful consequences only. Project 6-12 months forward. Never invent fears. | |
| Tone | Empathetic urgency, not fear-mongering | |
| Scroll position | 15-22% | |
| Psychological role | Loss aversion activation — losing hurts more than gaining |
bridge
| Attribute | Specification | |
|---|---|---|
| Purpose | Transition from problem to solution. The "there's a better way" moment. | |
| Required | 1-3 sentences that pivot from pain to possibility | |
| Copy rule | Brief. The bridge is a breath between tension and relief. | |
| Scroll position | 20-25% | |
| Psychological role | Tension release — the reader exhales here |
solution-reveal
| Attribute | Specification | |
|---|---|---|
| Purpose | Introduce the product as the natural resolution to the established problem. | |
| Required | headline, product name, core promise (1 sentence), visual/screenshot | |
| Copy rule | Position as discovery, not pitch. "We built X because..." not "Buy X now!" | |
| Scroll position | 22-30% | |
| Psychological role | Relief + curiosity — "this might actually work" |
features
| Attribute | Specification | |
|---|---|---|
| Purpose | Show WHAT the product does and HOW it delivers the promise. | |
| Required | headline, 3-6 features with benefit-oriented descriptions | |
| Format | Icon + title + 1-2 sentence benefit description per feature | |
| Copy rule | Lead with benefit, follow with feature. "Ship faster (auto-deploy)" not "Auto-deploy (faster shipping)" | |
| Scroll position | 25-40% | |
| Psychological role | Rational validation — "this makes sense logically" |
how-it-works
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/sales-page-narrative/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/melgarafael/growthos/sales-page-narrative)