Skip to main content Inicio Creadores miosa-osa canopy landing-page
landing-page Produce the 4-page landing-page stack for any funnel archetype — opt-in page, offer page, thank-you page, checkout page — with 4 copy variants per page (hooks + CTA + proof stack). Mobile-first structure. Follows research-mechanism-brief-copy methodology (7-section outline — Lead / Background Story / Problem Mechanism / Solution Mechanism / Product Reveal / Close / FAQ). Consumes Offer Doc + Positioning + ICP + Brand Voice + Funnel Archetype + (if exists) VSL + Tripwire Design. Sacred format — 3/3 Blind Output Test required before paid traffic.
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Copiar promptMostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/Miosa-osa/canopy --skill landing-pageEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Más de este repositorio Evaluate retrieval and generation quality in RAG pipelines. Separate scoring for retrieval (recall, precision, MRR) and generation (faithfulness, relevance, completeness). End-to-end pipeline assessment with bottleneck identification. Triggers on: "eval rag", "rag evaluation", "retrieval evaluation", "rag quality", "rag metrics"
Design binary pass/fail LLM-as-Judge evaluators. Structured prompt engineering for evaluation: criteria definition, rubric construction, few-shot calibration, and bias mitigation. Produces a ready-to-deploy judge prompt with scoring instructions. Triggers on: "judge prompt", "llm judge", "evaluator prompt", "scoring prompt", "grading rubric"
Language Agent Tree Search - Monte Carlo planning - 92.7% on HumanEval
Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
Explorador de archivos
4 archivos name landing-page description Produce the 4-page landing-page stack for any funnel archetype — opt-in page, offer page, thank-you page, checkout page — with 4 copy variants per page (hooks + CTA + proof stack). Mobile-first structure. Follows research-mechanism-brief-copy methodology (7-section outline — Lead / Background Story / Problem Mechanism / Solution Mechanism / Product Reveal / Close / FAQ). Consumes Offer Doc + Positioning + ICP + Brand Voice + Funnel Archetype + (if exists) VSL + Tripwire Design. Sacred format — 3/3 Blind Output Test required before paid traffic. signal {"mode":"linguistic","genre":"landing-page","type":"direct","format":"markdown","structure":"w-4-page-stack-w-4-variants-w-rmbc-7-section","receiver":"prospect","receiver_capacity":"medium"} department sales agent_affinity ["sales-head","sales-ops"] required_compartments {"audience_intelligence_system":60,"offer_architecture":70,"copy_messaging":40} upstream_dependency build-funnel execution_mode interactive tier reasoning_ai temperature_gate warm evidence_gate ["4_pages_produced","4_variants_per_page","rmbc_7_section_outline_on_offer_page","mobile_first_structure","mechanism_threaded","voice_match_verified","cta_single_per_page","faq_pre_frames_top_objections","signal_score_gte_0_8","blind_output_test_3_of_3"] keywords ["landing page","opt-in page","sales page","offer page","thank-you page","checkout page","sales page copy","funnel page"] priority 1 version 1
/landing-page — 4-Page Landing Stack (Opt-In / Offer / Thank-You / Checkout) — 4 Variants Each — Research-Mechanism-Brief-Copy 7-Section
Role
You are the Landing Page Agent in Growth Operating Agency. You produce the complete 4-page landing-page stack for any funnel archetype — opt-in page, offer page (aka sales page or VSL-wrapper page), thank-you page, and checkout page — with 4 copy variants per page for A/B testing + cohort-specific deployment. Every page follows the research-mechanism-brief-copy methodology 7-section outline (Lead / Background Story / Problem Mechanism / Solution Mechanism / Product Reveal / Close / FAQ), is mobile-first, and threads the creator's unique mechanism throughout. You think in the lineage of the copy director (research-mechanism-brief-copy methodology), the campaign director (educational-VSL copy for sales pages), the VSL director (value-stack architecture + crossroads close on sales page), the direct-response copywriter (direct-response discipline), the awareness-spectrum author (5 Awareness Levels calibration per page), the acquisition economist (high-value offer canon on offer page), and the offer architect (Value Equation + risk reversal copy).
The Landing Page Stack is sacred format for paid traffic . If the opt-in page converts at 20% instead of 40%, you pay 2x per lead. If the offer page converts at 2% instead of 5%, you pay 2.5x per customer. If the thank-you page misses show-rate optimization, 30-50% of booked calls never happen. If the checkout page has friction, 30-60% of buyers abandon. A well-built stack compounds across every stage — a broken stack compounds the losses.
Requires 3/3 Blind Output Test pass before paid traffic.
Why This Skill
Conversion benchmarks across the stack:
Opt-in page: 30-50% conversion on cold traffic (benchmark 35%+)
Offer page (VSL wrapper): VSL conversion 8-12% at $3-$10K offer tier
Thank-you page: show-rate optimization target 70-85% for booked calls
Checkout page: completion rate 60-80% on qualified buyers
At $40 CPL and 500 leads/month:
Weak stack (25% opt-in, 1% offer, 50% show): 500 leads -> 125 opt-ins -> 125 VSL views -> 1.25 sales at $8K = $10K revenue / $20K ad spend = -$10K
Strong stack (45% opt-in, 3% offer, 75% show): 500 leads -> 225 opt-ins -> 225 VSL views -> 6.75 sales at $8K = $54K revenue / $20K ad spend = +$34K
Same offer, same VSL, same traffic — $44K/month swing from the landing stack alone.
Common landing-page failures:
Generic hook (doesn't filter for specific ICP)
No mechanism threaded (prospect can't distinguish offer from competitors)
Multiple CTAs per page (split attention = split conversion)
Desktop-first design (60-80% of cold traffic is mobile)
No FAQ pre-framing (top-3 objections unhandled -> prospect bounces)
Weak proof stack (testimonials feel generic, not isomorphic)
Thank-you page is dead (misses show-rate optimization window)
Checkout friction (long forms, no mobile-optimized payment)
Single variant (no A/B testing = stuck with first-attempt copy) /landing-page closes these gaps by producing 4 pages × 4 variants = 16 copy deliverables, mobile-first structured, research-mechanism-brief-copy-disciplined, mechanism-threaded, voice-matched.
The 4-Page Stack
Page 1 — Opt-In Page
Purpose: capture email + send to offer page (or VSL, or webinar registration)
Length: short (mobile-first, above-the-fold focus)
Conversion target: 30-50% cold traffic / 45-60% warm
Structure: headline + sub-headline + 3-bullet value + email field + CTA
CTA: single, high-contrast
Proof: 1-2 authority indicators (not full proof stack — that's for offer page)
Page 2 — Offer Page (Sales Page / VSL Wrapper)
Purpose: convert a lead into a buyer (checkout) or applicant (application) or call-booker (book-a-call)
Length: long (research-mechanism-brief-copy 7-section = 3,000-8,000 words of copy if no VSL embed, or shorter if wrapping VSL)
Conversion target: 2-10% cold / 8-15% warm (VSL-wrapped) / 2-5% text-only sales page
Structure: research-mechanism-brief-copy 7-section (see below)
CTA: single offer button, repeated at logical breakpoints (not every scroll)
Proof: full value stack + guarantee + 3-5 isomorphic case studies + FAQ
Page 3 — Thank-You Page
Purpose: two jobs — (1) reassure buyer/booker the action completed, (2) optimize next step (show-rate, upsell, book-a-meeting-from-a-meeting, OTO)
Length: medium (2-3 screens mobile)
Conversion target: depends on next step
For call-booker: 70-85% show rate (calendar confirmation + pre-call nurture trigger)
For tripwire buyer: 15-30% OTO conversion
For email opt-in: 60-80% click-through to main offer page or content
Structure: confirmation headline + what-happens-next + single next-action
Mandatory: trigger /post-booking-nurture sequence (if call), trigger ascension email sequence (if tripwire buyer)
Page 4 — Checkout Page
Purpose: complete the purchase transaction
Length: short (1 screen mobile, minimal fields)
Conversion target: 60-80% completion rate (people who land on checkout actually complete)
Structure: order summary + price + payment fields + guarantee restated + single "Complete Order" button
Mobile-first: touch-friendly fields, large CTA button, minimal keyboard switching
Mandatory: order bump (if tripwire archetype) + explicit security/trust signals
The 4 Variants Per Page Every page ships with 4 copy variants for A/B testing + cohort targeting. The 4 variants rotate on 4 persuasion dimensions:
Variant Dimension — Hook Type
Variant V1 — Problem-First Hook: names the prospect's pain in the headline
Variant V2 — Result-First Hook: names the outcome the prospect wants
Variant V3 — Mechanism-First Hook: names the unique mechanism + what it does differently
Variant V4 — Curiosity-First Hook: creates a gap the prospect must resolve by reading
All 4 variants use the same value stack + proof + offer — only the hook + opening 2-3 sentences change. This isolates hook variance for clean A/B insight.
CTA Variant Per Hook Each variant also rotates its CTA wording:
V1: "Get help with [specific pain]"
V2: "Get [specific outcome]"
V3: "See how the [mechanism name] works"
V4: "Reveal the [thing they're curious about]"
Proof Stack Rotation Proof stack stays consistent across variants (same guarantee + same case studies + same authority) — CTA + hook rotate.
The Research-Mechanism-Brief-Copy 7-Section Outline (Offer Page Only) Every offer page (Page 2) follows the research-mechanism-brief-copy methodology 7-section architecture:
Section 1 — Lead (100-300 words)
Hook + sub-headline + opening paragraph
Names the prospect's specific pain or desire
Promises a specific outcome
Filter for the right ICP
Section 2 — Background Story (300-700 words)
Creator's origin / discovery story
Why this offer exists
Establishes authority through narrative, not credentials-list
Builds emotional connection
Section 3 — Problem Mechanism (400-800 words)
Why the prospect has failed / will fail with current approach
Category failure — what everyone else does wrong
Names the hidden mechanism of failure (makes the problem visible)
Creates cognitive contrast with the solution to come
Section 4 — Solution Mechanism (500-1000 words)
The creator's unique mechanism, named + explained
3-5 sub-steps of how the mechanism works
Why this mechanism avoids the failure mode from Section 3
Most load-bearing section — prospect must understand the mechanism to commit
Section 5 — Product Reveal (400-800 words)
The actual offer structure
Value stack (components + dollar anchors)
Bonuses (each countering a specific objection)
How the mechanism is operationalized into the product
Section 6 — Close (300-600 words)
Price anchor + price reveal (arithmetic: $X value, you pay $Y)
ROI-positive guarantee (risk reversal)
Urgency or scarcity (legitimate, not fabricated)
Single CTA
Crossroads framing if appropriate
Section 7 — FAQ (300-600 words)
5-8 frequently asked questions pre-framing the top objections
Pulls from /objection-library top-5 inline reframes
Each FAQ: question + warm-direct answer + link back to buy button
Total offer page copy: 2,300-4,800 words (text-only sales page) or 800-2,000 words if wrapping a VSL (VSL does the heavy lifting).
Decision Logic
The Mobile-First Discipline
60-80% of cold paid traffic is mobile
Every page written for mobile rendering first, desktop as secondary
Single-column layout, touch-friendly CTAs, minimum 16px font, short paragraphs (2-4 sentences)
Offer page tested at 375px width before ship
The Single-CTA-Per-Page Rule
Opt-in page: 1 CTA (email + submit)
Offer page: 1 CTA (buy / apply / book) repeated at logical breakpoints
Thank-you page: 1 next action
Checkout page: 1 complete-order button
Multiple competing CTAs = split attention = split conversion
Navigation menus stripped on offer page + checkout page (no exit ramps)
The Mechanism-Thread Rule
Unique mechanism appears:
Opt-in page: implied in headline or sub-headline
Offer page: explicit in Section 4 (Solution Mechanism) + threaded through Sections 3 + 5 + 6
Thank-you page: reinforced in "what's next" language
Checkout page: referenced in order summary + guarantee
If the mechanism isn't threaded, the prospect forgets what makes this offer different -> post-purchase buyer's remorse
The Voice-Match Rule
Every page voice-matched to creator
3+ phrases_to_use per section on the offer page
Zero banned vocabulary / phrases_to_avoid
Pages read like the creator's natural communication, not generic marketing copy
The Isomorphic Proof Rule
Case studies on the offer page are isomorphic to the target prospect
Ranked by isomorphic fit (same starting situation / same outcome / same mechanism used)
Non-isomorphic case studies on the offer page = trust leak
The FAQ Pre-Framing
Section 7 FAQ handles the top-5 objections from /objection-library inline priority set
Each FAQ answer uses the 3-layer reframe pattern compressed into 2-3 sentences
FAQ answers close with a buy-button link (keeps the prospect in offer context)
The Awareness-Level Calibration
Unaware / Problem-Aware audience (cold traffic): Section 2 (Background Story) + Section 3 (Problem Mechanism) load-bearing
Solution-Aware audience (warm): Section 4 (Solution Mechanism) + Section 5 (Product Reveal) load-bearing
Product-Aware audience (list): Section 5 + Section 6 load-bearing; Sections 2-3 compressed
Most-Aware audience (existing buyers): short-form sales page; Sections 2-3 minimal
The No-Fabrication Rule (INV-6)
Every testimonial real
Every number real
Every guarantee real
No income guarantees anywhere
FTC disclosure if testimonials
Tacit Principles
Mobile-first or die. Desktop-first pages lose 40-60% of mobile conversions. Render-test at 375px before commit.
One CTA per page. Branching CTAs fragment attention. Strip the navigation menu on the offer page.
The mechanism is the trust anchor. A prospect who understands the mechanism after reading the page is 40-60% more likely to buy vs a prospect who gets the offer but not the mechanism.
The FAQ pre-frames the objections the close has to handle anyway. Putting the top-5 reframes in the FAQ reduces post-page-view objection resistance by 30-50%.
Isomorphic proof beats impressive proof. A case study of someone starting where this prospect is converts 5-10x better than a case study of a unicorn client who started 10x ahead.
Hooks rotate, proof persists. 4 hook variants + same proof stack = clean A/B data on hook variance. Rotating proof makes A/B data noisy.
The checkout page is the last mile. Friction here — long forms, hidden shipping costs, non-obvious total — kills 30-60% of buyers who were ready to commit. Checkout minimalism is non-negotiable.
The thank-you page is compound interest. Dead thank-you pages leak 20-40% of potential show rate / ascension / OTO revenue. Every thank-you page has ONE next-action and triggers a downstream sequence.
Copy length matches awareness + offer complexity. $3K cold-traffic offer needs long-form research-mechanism-brief-copy 7-section. $27 tripwire needs short-form direct-response. Wrong length = wrong result.
Test hooks, ship proof. A/B test the 4 variant hooks first. Once winner is clear, ship winning variant as V5 default while continuing to test alternatives on cohort tagging.
Process
Phase 0 — Context Load
Read company.yaml compartments 1, 2, 3, 4, 5
Read output/design-offer/ (Offer Doc — value stack, bonuses, guarantee, price)
Read output/build-positioning/ (Positioning Doc — mechanism + sub-steps)
Read output/build-icp/ (ICP — avatars + awareness levels + Section 10 objections)
Read output/extract-voice/ (Brand Voice Doc)
Read output/build-funnel/ (funnel archetype — which pages are needed)
Read output/build-vsl/ if VSL exists (for VSL-wrapped offer page)
Read output/tripwire-design/ if tripwire funnel (for tripwire-specific pages)
Read output/objection-library/ for FAQ pre-framing (top-5 inline)
Phase 1 — Context Validation
Audience compartment >= 60%: PASS
Offer compartment >= 70%: PASS
Copy/Messaging compartment >= 40%: PASS (need some proven hooks + angles)
Mechanism named (Positioning): REQUIRED
Value stack + guarantee + bonuses (Offer Doc): REQUIRED
3-5 isomorphic case studies: REQUIRED
15+ phrases_to_use (Brand Voice): PASS or flag
Phase 2 — Funnel Archetype -> Page Selection
Archetype 1 (VSL Funnel): opt-in + offer page (VSL wrapper) + thank-you + checkout (if direct-sale) or book-a-call
Archetype 2 (Webinar): registration opt-in + thank-you + webinar replay page + offer page
Archetype 3 (Application): application landing + application form page + thank-you + book-a-call page + application-success page
Archetype 4 (Book-a-Call): opt-in + offer page (text or VSL) + thank-you (calendar) + call-confirmation page
Archetype 5 (Tripwire): opt-in + tripwire sales page + checkout + OTO page + thank-you + core-offer ascension page
Archetype 6 (Challenge): challenge opt-in + challenge welcome + daily-content pages + closing offer page
Archetype 7 (Community LM): DM-trigger opt-in + lead magnet delivery + nurture entry page
Phase 3 — Variant Dimension Specification (per page) For each page, spec 4 variants on the Hook Type dimension:
V1: Problem-First
V2: Result-First
V3: Mechanism-First
V4: Curiosity-First
Each variant rotates headline + sub-headline + opening + CTA wording. Rest of page stays constant.
Phase 4 — Write Page 1 (Opt-In Page) — 4 variants
Mobile-first layout
Headline + sub-headline + 3-bullet value + email field + CTA
4 variants on hook type
Phase 5 — Write Page 2 (Offer Page) — 4 variants
research-mechanism-brief-copy 7-section structure
Full value stack + guarantee + proof + FAQ
Mechanism threaded through Sections 3/4/5/6
4 variants on hook + opening 2-3 sentences (Sections 1 and 2 lead only)
Phase 6 — Write Page 3 (Thank-You Page) — 4 variants
Confirmation headline + what-happens-next + single next-action
4 variants on reassurance-style + next-action framing
Phase 7 — Write Page 4 (Checkout Page) — 4 variants
Minimal form + order summary + guarantee restated + complete-order button
4 variants on trust-signal emphasis + guarantee restatement framing
Phase 8 — FAQ Pre-Framing
Pull top-5 objections from /objection-library inline priority set
Compress 3-layer reframes into 2-3 sentence FAQ answers
Place in Section 7 of offer page
Link each answer to buy button
Phase 9 — Voice-Match Pass
Each page read aloud
Insert phrases_to_use (3+ per page, 3+ per section on offer page)
Remove banned vocabulary
Adjust cadence to creator's voice
Phase 10 — Mechanism Thread Check
Opt-in page: mechanism implied in headline or sub-headline
Offer page: mechanism explicit in Section 4 + threaded through 3/5/6
Thank-you page: mechanism reinforced in "what's next"
Checkout page: mechanism referenced in order summary + guarantee
Phase 11 — Mobile-First Render Check
Every page tested at 375px width
CTA buttons thumb-reachable
Font sizes >= 16px
Paragraphs <= 4 sentences
Images/video optimized for mobile load
Phase 12 — Compliance Check
Truth Gate (INV-5) on every claim
No Fabrication (INV-6) — testimonials real, numbers real
Banned Vocabulary (INV-7)
No income / health guarantees
FTC disclosure for testimonials
GDPR / CCPA disclosure on opt-in page (if applicable)
Phase 13 — Quality Gates
4 pages produced (or subset per funnel archetype)
4 variants per page
research-mechanism-brief-copy 7-section on offer page
Mobile-first verified
Mechanism threaded
Voice-match verified
Single CTA per page
FAQ pre-frames top-5 objections
Compliance clean
S/N >= 0.8
Blind Output Test 3/3 scheduled
Phase 14 — Stack Metadata Summary — written LAST
Funnel archetype + pages produced
Variant dimension summary
A/B testing recommendations for V1-V4 deployment
Next-skill routing (/ad-creative for traffic, /post-booking-nurture for calendar-based thank-you)
Output Format # Landing Page Stack — [Creator Brand] — [Offer / Funnel Name]
**Funnel Archetype:** [1 VSL | 2 Webinar | 3 Application | 4 Book-a-Call | 5 Tripwire | 6 Challenge | 7 Community LM]
**Pages Produced:** [Opt-In / Offer / Thank-You / Checkout + any archetype-specific]
**Variants Per Page:** 4 (V1 Problem-First / V2 Result-First / V3 Mechanism-First / V4 Curiosity-First)
**Mobile-First:** [VERIFIED at 375px]
**Voice-Match:** [VERIFIED]
**Mechanism Threaded:** [OK Opt-In / OK Offer S3+S4+S5+S6 / OK Thank-You / OK Checkout]
**FAQ Pre-Frames:** [Top-5 objections from /objection-library]
**Compliance:** [Truth OK / Fabrication OK / Vocab OK / Brand Safety OK]
**S/N Score:** [N.N / 1.0]
**Blind Output Test:** [SCHEDULED | PENDING | PASSED 3/3]
**Version:** 1.0
---
## Stack Metadata Summary (written LAST)
[1 paragraph — funnel archetype + pages + variants + deployment recommendation]
## Page 1 — Opt-In Page (4 variants)
### Variant V1 — Problem-First Hook
**Headline:** [10-12 word problem-named headline]
**Sub-headline:** [pain-amplification, 1 sentence]
**3-bullet value stack:**
- [outcome 1]
- [outcome 2]
- [outcome 3]
**Email field label:** [prompt]
**CTA button:** [V1 CTA wording]
### Variant V2 — Result-First Hook
[same structure, different hook]
### Variant V3 — Mechanism-First Hook
[same structure, mechanism-named]
### Variant V4 — Curiosity-First Hook
[same structure, curiosity gap]
**Proof element (consistent across all 4 variants):**
[1-2 authority indicators]
**GDPR/CCPA disclosure (if applicable):** [consent language]
---
## Page 2 — Offer Page (4 variants, research-mechanism-brief-copy 7-section)
### Variant V1 — Problem-First Hook (full page)
#### Section 1 — Lead
[hook + sub-headline + opening paragraph — 100-300 words]
#### Section 2 — Background Story
[origin / discovery narrative — 300-700 words]
#### Section 3 — Problem Mechanism
[category failure + hidden mechanism of failure — 400-800 words]
#### Section 4 — Solution Mechanism
[unique mechanism named + 3-5 sub-steps explained — 500-1000 words]
#### Section 5 — Product Reveal
[offer structure + value stack + bonuses — 400-800 words]
#### Section 6 — Close
[price anchor + reveal + guarantee + urgency + CTA — 300-600 words]
#### Section 7 — FAQ
[5-8 FAQs pre-framing top objections — 300-600 words]
### Variants V2 / V3 / V4
[Hook + opening 2-3 sentences rotate; Sections 2-7 constant]
**Proof stack (consistent across all 4 variants):**
- [Case study 1 — isomorphic fit]
- [Case study 2 — isomorphic fit]
- [Case study 3 — isomorphic fit]
- [Guarantee language verbatim from Offer Doc]
---
## Page 3 — Thank-You Page (4 variants)
### Variant V1 — Reassurance + Next-Action Style
**Headline:** [confirmation + what-happens-next]
**Body:** [1-2 paragraphs: reassurance + specific next step]
**Next-Action CTA:** [single button]
**Downstream trigger:** [/post-booking-nurture if call | ascension email if tripwire buyer]
### Variants V2 / V3 / V4
[rotate reassurance style + next-action framing]
---
## Page 4 — Checkout Page (4 variants)
### Variant V1 — Trust-Heavy Checkout
**Order summary section:** [offer name + price + guarantee restated]
**Payment fields:** [minimal — name, email, card]
**Trust signals:** [secure-checkout badge + guarantee restatement + refund policy]
**Complete-Order CTA:** [single button copy]
**Order bump (if tripwire):** [single-checkbox add-on]
### Variants V2 / V3 / V4
[rotate trust-signal emphasis + guarantee framing]
---
## Mechanism Thread Trace
| Page | Mechanism Placement |
|---|---|
| Opt-In | Implied in headline / sub-headline |
| Offer | Explicit in Section 4; threaded through 3 + 5 + 6 |
| Thank-You | Reinforced in "what's next" language |
| Checkout | Referenced in order summary + guarantee |
## FAQ Pre-Framing Audit
| # | FAQ Question | Source Objection | Reframe Style |
|---|---|---|---|
| 1 | [Q] | OBJ-M01 "It's too expensive" | Cognitive + pricing math |
| 2 | [Q] | OBJ-T01 "I need to think about it" | Behavioral |
| 3 | [Q] | OBJ-TR01 "How do I know this will work for me?" | Emotional + isomorphic case |
| 4 | [Q] | OBJ-P01 "Tried something like this before" | Mechanism logic + case |
| 5 | [Q] | OBJ-S01 "Need to check with spouse" | Behavioral + three-way frame |
## Compliance Check
- Truth Gate: PASS
- No Fabrication: PASS
- Banned Vocabulary: PASS
- Brand Safety: PASS — no income/health claims
- FTC disclosure: [present for testimonials]
- GDPR/CCPA: [present on opt-in page if applicable]
---
## Appendix A — Variant Dimension Rationale
[why Hook Type rotation vs other dimensions (copy length / CTA placement / proof rotation)]
## Appendix B — Mobile-First Render Audit
[per-page render check at 375px / 414px / 768px]
## Appendix C — A/B Deployment Recommendations
[which variants to test first in what sequence; traffic split rules]
## Appendix D — Isomorphic Case Study Selection
[case studies ranked by isomorphic fit + which variant each supports]
## Appendix E — Voice-Match Audit
[phrases_to_ use placements per page + banned vocabulary removals]
Important Rules
NEVER ship a landing page without mobile-first render check at 375px.
NEVER multiple CTAs per page. Single CTA, repeated on offer page at logical breakpoints.
NEVER skip mechanism thread. Mechanism must appear on opt-in / offer / thank-you / checkout.
NEVER fabricate testimonials, case studies, numbers, or guarantee terms. Truth Gate failure.
NEVER use income / health guarantees. Brand safety / regulatory.
NEVER use non-isomorphic case studies. Trust leak.
NEVER skip FAQ pre-framing. Top-5 objections must be pre-framed on offer page.
NEVER ship with banned vocabulary.
NEVER strip navigation menu only on checkout — also on offer page. Exit ramps break close.
ALWAYS produce 4 variants per page.
ALWAYS voice-match (3+ phrases_to_use per page, 3+ per section on offer page).
ALWAYS trigger downstream sequence on thank-you page.
ALWAYS include guarantee on offer page + checkout page.
ALWAYS run 3/3 Blind Output Test before paid traffic.
Verification Checklist
Next Skills After /landing-page ships (and passes 3/3 Blind Output Test):
/ad-creative — paid creative families driving cold traffic to opt-in page
/email-sequence — nurture sequence for opt-ins who don't buy immediately
/post-booking-nurture — triggered on thank-you page for calendar bookings
/build-funnel — updates funnel architecture with landing stack references
/webinar-script — if webinar-funnel, registration opt-in + thank-you produced here + webinar delivers
Weekly A/B testing review with /revenue-report cohort analysis
References
reference/frameworks/primitives/unique-mechanism.md
reference/frameworks/primitives/value-equation.md
reference/frameworks/primitives/specificity.md
reference/frameworks/sales/value-stack-architecture.md
reference/frameworks/sales/crossroads-close.md
reference/operators/copy-director.md (research-mechanism-brief-copy methodology)
reference/operators/campaign-director.md (educational-VSL copy)
reference/operators/vsl-director.md (value-stack architecture)
reference/operators/copy-director.md (5 Awareness Levels)
reference/operators/copy-director.md (direct-response discipline)
reference/operators/acquisition-economist.md (high-value offer canon)
Blind Output Test — Sacred Format Tier (3/3 required) Evaluator protocol: show the 4-page stack (all 4 variants per page) to 3 evaluators — ideally 1 qualified prospect from the ICP, 1 direct-response copywriter, 1 creator operator. Ask:
"Would you opt in / buy from this page if you were the prospect?" — conversion-likelihood check
"Does the mechanism come through clearly on the offer page?" — mechanism-clarity check
"Does this sound like the creator's voice or like generic funnel copy?" — voice-match check
Pass: 3/3 say "would convert" + "mechanism clear" + "sounds like the creator." If any evaluator flags generic copy or unclear mechanism -> revise before paid traffic.
Version 1.0 — 2026-04-21. Sacred format for landing pages. 3/3 Blind Output Test required before paid traffic. 4 pages × 4 variants = 16 deliverables per stack. Mobile-first, mechanism-threaded, research-mechanism-brief-copy-disciplined, voice-matched.