ericrisco/rsc-harness / skills/landing-copy
landing-copy
VerifiedUse when writing the words on a single conversion page — the hero headline and subhead, the offer, the proof and testimonials, and one primary CTA — or diagnosing a page that gets traffic and does not convert, as a copy problem rather than a layout one. NOT the paid ad that drives the click (that is `ads`), NOT the visual layout the words sit in (that is `design`), NOT the experiment that picks the winning variant (that is `ab-testing`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.2 KB |
| evals/README.md | markdown | 1.6 KB |
| evals/cases.yaml | config | 5.5 KB |
| references/frameworks.md | markdown | 3.4 KB |
| references/page-skeleton.md | markdown | 2.5 KB |
| references/vsl-page-handoff.md | markdown | 1.4 KB |
| scripts/verify.shexecutable | script | 6.3 KB |
references/frameworks.md
View on GitHub# Copy frameworks as scaffolds
Frameworks are skeletons you fill with the **buyer's own words** — never fill-in
templates you ship as-is. Pick one for the page's spine and one (FAB) for the
offer block. Examples below are fictional illustrations, not evidence or publishable customer claims.
Use only behavior and outcomes supported by the actual product evidence.
## PAS — Problem, Agitate, Solution
Best for **pain-aware** traffic that already feels the problem.
- **Problem** — name the pain in the reader's language. "Closing the books takes you nine days every month."
- **Agitate** — make the cost vivid, briefly. "Nine days your team isn't forecasting, isn't planning — just chasing receipts."
- **Solution** — present the offer as the relief. "Lumen closes in two. Snap, submit, done."
Don't over-agitate warm traffic; it reads as manipulation. Agitation length scales with how cold the visitor is (see awareness note below).
## AIDA — Attention, Interest, Desire, Action
Broad **top-of-funnel** traffic that may not yet know the category.
- **Attention** — the hook headline stops the scroll.
- **Interest** — the subhead and first section make it relevant ("for finance teams of 20–200").
- **Desire** — the offer + proof make them want the outcome (the result-bearing testimonial).
- **Action** — the single CTA, repeated.
## BAB — Before, After, Bridge
Strong for **transformation** stories and pages built around a customer journey.
- **Before** — the world today: "Month-end was three late nights and a spreadsheet you didn't trust."
- **After** — the world with the product: "Now it's a Tuesday afternoon and the numbers reconcile themselves."
- **Bridge** — the product is how you cross from one to the other: "Lumen is the bridge — connect your cards, set the rules once."
## FAB — Feature, Advantage, Benefit (the offer block)
This is the feature→benefit transform. Climb the ladder, then **stop at the benefit** the reader cares about and use the feature/mechanism as the proof underneath.
- **Feature** — what it has: "Import preview."
- **Advantage** — what that does: "shows records needing review before the import."
- **Benefit** — what the buyer gets: "inspect exceptions before approving changes to live records" (when the product supports this preview).
Write the benefit as the line; keep the feature as the evidence beneath it.
```text
Bad — "Includes SSO, SCIM provisioning, and audit logs."
Better — "Review recorded access changes in the audit log."
Use only if that behavior is verified; the feature list alone does not prove it.
```
## Awareness stage changes how much you agitate
How much problem-agitation you do **before** the offer depends on traffic temperature:
| Traffic | Awareness | Copy move |
| --- | --- | --- |
| Cold (broad ad, first touch) | Problem-unaware / problem-aware | Lead with the problem, agitate, *then* offer (PAS/AIDA). They need to feel the pain first. |
| Warm (retargeting, email list, referral) | Solution-aware / product-aware | Go straight to the offer and proof. Re-agitating insults them and adds friction. |
| Hot (pricing page, "buy" intent) | Most aware | Minimal copy: offer, proof, CTA. Remove everything between them and the button. |
Match the framework to where the visitor is, not to a habit. A retargeting page that
re-explains the problem the visitor already knows loses them to impatience.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |