melgarafael/growthos/sales-page-narrative

Claude Code and agent skill by melgarafael/growthos

Trust tier 3
  • community
Source check pending

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-narrative

SKILL.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

WRONG: "Write a hero section" → generic headline + vague subheadline + "Get Started" CTA
RIGHT: "Write a hero section" → select framework → map awareness level → consult audience
language (Phase 2) → write headline using 4U formula → anti-slop check → score ≥ 30/35

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:

1. growthOS/output/sales-pages/{slug}/state.json — Pipeline state (phases 1-4)
2. growthOS/voice/offers/{product}.md — Product knowledge
3. growthOS/voice/GOLDEN-DOC.md — Brand voice (if user opted in)
4. growthOS/brand-voice.yaml — Anti-slop rules
5. growthOS/voice/virais/INDEX.md — Viral intelligence
6. growthOS/design-intelligence/theory/ogilvy-principles.md — Ogilvy rules (if available)

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
FrameworkBest ForAwareness LevelPage LengthEmotion Level
AIDAProduct-aware audiences, SaaS, toolsSolution-Aware to Product-Aware5-8 sectionsMedium
PASProblem-aware audiences, services, educationProblem-Aware to Solution-Aware6-10 sectionsHigh
Story BridgeUnaware audiences, emotional products, high-ticketUnaware to Problem-Aware8-12 sectionsVery High
Ogilvy DirectPremium products, luxury, authority positioningProduct-Aware to Most-Aware5-7 sectionsLow (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:

OrderSection TypeFramework StagePurpose
1heroAttentionBold claim or surprising stat that stops the scroll
2logo-barAttentionSocial proof — "trusted by" logos (if available)
3featuresInterest3-6 key features with benefit-oriented descriptions
4how-it-worksInterest3-step process showing simplicity
5social-proofDesireTestimonials, case studies, metrics
6pricingDesire → ActionPrice anchoring + value stack
7guaranteeActionRisk reversal
8final-ctaActionClosing 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:

OrderSection TypeFramework StagePurpose
1heroProblemName the pain using audience's own words
2problem-expansionProblemValidate 2-3 specific manifestations of the problem
3agitationAgitateShow consequences of NOT solving — what gets worse
4bridgeAgitate → Solution"There's a better way" transition
5solution-revealSolutionIntroduce the product as the natural resolution
6featuresSolutionHow it works — proof the solution is real
7social-proofSolutionTestimonials from people who had the same problem
8objection-handlerSolutionAddress top 3 objections inline
9pricingSolutionPrice vs. cost of inaction
10final-ctaSolutionCTA 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:

OrderSection TypeFramework StagePurpose
1heroHeroCustomer as the hero — their aspiration or desire
2problem-storyProblemThe villain — external, internal, and philosophical problem
3empathyGuide"I was where you are" — establish guide credibility
4authorityGuideCredentials, results, media — why you're the guide
5planPlanSimple 3-step plan — clarity reduces fear
6social-proofPlanOthers who followed the plan and succeeded
7cta-primaryActionClear call to action — "what to do now"
8success-visionSuccessPaint the picture of life AFTER the transformation
9failure-stakesFailureWhat happens if they do nothing (subtle, not fear-based)
10objection-handler—Address remaining doubts
11pricingActionPrice as investment in the transformation
12final-ctaActionLast 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:

OrderSection TypeFramework StagePurpose
1hero-visualVisual ImpactLarge visual (minimum 75vh), editorial-quality
2editorial-headlineAttentionLong headline (up to 25 words), Ogilvy-style
3long-form-copyArgumentDeep editorial copy — the full case, with subheadings
4before-afterProofSide-by-side or sequential before/after comparison
5social-proofAuthorityPremium testimonials — fewer but deeper
6single-ctaActionONE clear CTA, premium feel
7guaranteeTrustUnderstated 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
AttributeSpecification
PurposeFirst thing the visitor sees. Must communicate the core promise in <5 seconds.
Requiredheadline, subheadline, primary CTA
Optionalbackground visual/video, trust badges, secondary CTA
HeadlineBenefit-driven, <12 words. Score ≥ 12 on 4U formula.
SubheadlineExpand on HOW the benefit is delivered. 1-2 sentences.
CTAAction verb + outcome. Never "Learn More" or "Submit".
Scroll position0%
Psychological rolePattern interrupt. Break visitor's autopilot browsing.
logo-bar
AttributeSpecification
PurposeInstant trust transfer via brand association.
Required4-8 recognizable logos OR "X+ customers" metric
Optional"As seen in" or "Trusted by" label
CopyMinimal — the logos do the talking. One label line max.
Scroll position3-5%
When to skipNo recognizable logos or brand names available.
problem-expansion
AttributeSpecification
PurposeValidate the audience's pain with specificity. Make them feel SEEN.
Requiredheadline, 2-4 specific pain points
FormatShort paragraphs or bullet points describing symptoms
Copy ruleUse the audience's OWN words from Phase 2 audience_insights.language_patterns
Scroll position8-15%
Psychological roleEmpathy bridge — "this person understands my problem"
agitation
AttributeSpecification
PurposeShow the cost of inaction. Make the status quo feel unacceptable.
Requiredheadline, consequence narrative
Copy ruleTruthful consequences only. Project 6-12 months forward. Never invent fears.
ToneEmpathetic urgency, not fear-mongering
Scroll position15-22%
Psychological roleLoss aversion activation — losing hurts more than gaining
bridge
AttributeSpecification
PurposeTransition from problem to solution. The "there's a better way" moment.
Required1-3 sentences that pivot from pain to possibility
Copy ruleBrief. The bridge is a breath between tension and relief.
Scroll position20-25%
Psychological roleTension release — the reader exhales here
solution-reveal
AttributeSpecification
PurposeIntroduce the product as the natural resolution to the established problem.
Requiredheadline, product name, core promise (1 sentence), visual/screenshot
Copy rulePosition as discovery, not pitch. "We built X because..." not "Buy X now!"
Scroll position22-30%
Psychological roleRelief + curiosity — "this might actually work"
features
AttributeSpecification
PurposeShow WHAT the product does and HOW it delivers the promise.
Requiredheadline, 3-6 features with benefit-oriented descriptions
FormatIcon + title + 1-2 sentence benefit description per feature
Copy ruleLead with benefit, follow with feature. "Ship faster (auto-deploy)" not "Auto-deploy (faster shipping)"
Scroll position25-40%
Psychological roleRational 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

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
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/melgarafael/growthos/sales-page-narrative/badge)](https://verified-skill.com/skills/melgarafael/growthos/sales-page-narrative)

Something wrong with this skill or its page? Tell us.