opencode-skills-antigravity 0.0.7 โ 0.0.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/bundled-skills/docs/users/getting-started.md +1 -1
- package/bundled-skills/docs/users/walkthrough.md +21 -17
- package/bundled-skills/landing-page-generator/SKILL.md +203 -0
- package/bundled-skills/landing-page-generator/references/conversion-patterns.md +176 -0
- package/bundled-skills/landing-page-generator/references/frameworks.md +177 -0
- package/bundled-skills/landing-page-generator/references/landing-page-patterns.md +98 -0
- package/bundled-skills/landing-page-generator/references/seo-checklist.md +109 -0
- package/bundled-skills/landing-page-generator/scripts/landing_page_scaffolder.py +568 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -14,9 +14,11 @@ OpenCode automatically detects all skills and makes them available to the AI age
|
|
|
14
14
|
You can then invoke any skill explicitly in your prompt:
|
|
15
15
|
|
|
16
16
|
```bash
|
|
17
|
-
opencode run
|
|
17
|
+
opencode run /brainstorming help me plan a feature
|
|
18
18
|
```
|
|
19
19
|
|
|
20
|
+
Skills are also available as `/` commands directly in the OpenCode chat (e.g., `/brainstorming`).
|
|
21
|
+
|
|
20
22
|
Or simply describe what you want and OpenCode will pick the right skill automatically.
|
|
21
23
|
|
|
22
24
|
## ๐ Installation
|
|
@@ -1,42 +1,46 @@
|
|
|
1
|
-
# Walkthrough: Release v8.
|
|
1
|
+
# Walkthrough: Release v8.2.0 Maintenance Sweep
|
|
2
2
|
|
|
3
3
|
## Overview
|
|
4
4
|
|
|
5
|
-
This walkthrough captures the maintainer-side documentation and release
|
|
5
|
+
This walkthrough captures the maintainer-side documentation and release publication work for **v8.2.0** after the 2026-03-18 maintenance sweep.
|
|
6
6
|
|
|
7
7
|
## Changes Verified
|
|
8
8
|
|
|
9
9
|
### 1. Community PR batch integrated
|
|
10
10
|
|
|
11
|
-
- **PR #
|
|
12
|
-
- **PR #
|
|
13
|
-
- **PR #
|
|
14
|
-
- **PR #
|
|
15
|
-
- **PR #
|
|
16
|
-
- **PR #
|
|
11
|
+
- **PR #333**: Repaired missing required frontmatter fields in `skill-anatomy` and `adapter-patterns`
|
|
12
|
+
- **PR #336**: Added `astro`, `hono`, `pydantic-ai`, and `sveltekit`
|
|
13
|
+
- **PR #338**: Repaired malformed markdown in `browser-extension-builder`
|
|
14
|
+
- **PR #343**: Added missing metadata labels to `devcontainer-setup`
|
|
15
|
+
- **PR #340**: Added `openclaw-github-repo-commander`
|
|
16
|
+
- **PR #334**: Added `goldrush-api`
|
|
17
|
+
- **PR #345**: Added `Wolfe-Jam/faf-skills` to README source attributions
|
|
17
18
|
|
|
18
19
|
### 2. Release-facing docs refreshed
|
|
19
20
|
|
|
20
21
|
- **README.md**:
|
|
21
|
-
- Current release updated to **v8.
|
|
22
|
+
- Current release updated to **v8.2.0**
|
|
22
23
|
- Release summary text aligned with the merged PR batch
|
|
23
24
|
- Contributor acknowledgements kept in sync with the latest merge set
|
|
24
25
|
- **docs/users/getting-started.md**:
|
|
25
|
-
- Version header updated to **v8.
|
|
26
|
-
- **docs/users/faq.md**:
|
|
27
|
-
- Active `skill-review` workflow guidance retained as the current contributor check
|
|
26
|
+
- Version header updated to **v8.2.0**
|
|
28
27
|
- **CHANGELOG.md**:
|
|
29
|
-
- Added the release notes section for **8.
|
|
28
|
+
- Added the release notes section for **8.2.0**
|
|
30
29
|
|
|
31
|
-
### 3.
|
|
30
|
+
### 3. Maintenance fixes verified
|
|
31
|
+
|
|
32
|
+
- **Issue #344**: Corrected `.claude-plugin/marketplace.json` to use `source: "./"` and added a regression test for the Claude Code marketplace entry
|
|
33
|
+
- **.github/MAINTENANCE.md**: Documented the maintainer flow for fork-gated workflows and stale PR metadata
|
|
34
|
+
|
|
35
|
+
### 4. Release protocol executed
|
|
32
36
|
|
|
33
37
|
- `npm run release:preflight`
|
|
34
38
|
- `npm run security:docs`
|
|
35
39
|
- `npm run validate:strict` (diagnostic, optional blocker)
|
|
36
|
-
- `npm run release:prepare -- 8.
|
|
37
|
-
- `npm run release:publish -- 8.
|
|
40
|
+
- `npm run release:prepare -- 8.2.0`
|
|
41
|
+
- `npm run release:publish -- 8.2.0`
|
|
38
42
|
|
|
39
43
|
## Expected Outcome
|
|
40
44
|
|
|
41
45
|
- Documentation, changelog, and generated metadata all agree on the release state.
|
|
42
|
-
- The repository
|
|
46
|
+
- The repository published the `v8.2.0` tag and GitHub release successfully.
|
|
@@ -0,0 +1,203 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: "landing-page-generator"
|
|
3
|
+
description: "Generates high-converting Next.js/React landing pages with Tailwind CSS. Uses PAS, AIDA, and BAB frameworks for optimized copy/components (Heroes, Features, Pricing). Focuses on Core Web Vitals/SEO."
|
|
4
|
+
category: "front-end"
|
|
5
|
+
risk: "safe"
|
|
6
|
+
source: "community"
|
|
7
|
+
date_added: "2026-03-18"
|
|
8
|
+
author: "alirezarezvani"
|
|
9
|
+
tags: ["nextjs", "react", "tailwind", "landing-page", "marketing", "seo", "cro"]
|
|
10
|
+
tools: ["claude", "cursor", "gemini"]
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
# Landing Page Generator
|
|
14
|
+
|
|
15
|
+
Generate high-converting landing pages from a product description. Output complete Next.js/React components with multiple section variants, proven copy frameworks, SEO optimization, and performance-first patterns. Not lorem ipsum โ actual copy that converts.
|
|
16
|
+
|
|
17
|
+
**Target:** LCP < 1s ยท CLS < 0.1 ยท FID < 100ms
|
|
18
|
+
**Output:** TSX components + Tailwind styles + SEO meta + copy variants
|
|
19
|
+
|
|
20
|
+
## Core Capabilities
|
|
21
|
+
|
|
22
|
+
- 5 hero section variants (centered, split, gradient, video-bg, minimal)
|
|
23
|
+
- Feature sections (grid, alternating, cards with icons)
|
|
24
|
+
- Pricing tables (2โ4 tiers with feature lists and toggle)
|
|
25
|
+
- FAQ accordion with schema markup
|
|
26
|
+
- Testimonials (grid, carousel, single-quote)
|
|
27
|
+
- CTA sections (banner, full-page, inline)
|
|
28
|
+
- Footer (simple, mega, minimal)
|
|
29
|
+
- 4 design styles with Tailwind class sets
|
|
30
|
+
|
|
31
|
+
---
|
|
32
|
+
|
|
33
|
+
## Generation Workflow
|
|
34
|
+
|
|
35
|
+
Follow these steps in order for every landing page request:
|
|
36
|
+
|
|
37
|
+
1. **Gather inputs** โ collect product name, tagline, audience, pain point, key benefit, pricing tiers, design style, and copy framework using the trigger format below. Ask only for missing fields.
|
|
38
|
+
2. **Analyze brand voice** (recommended) โ if the user has existing brand content (website copy, blog posts, marketing materials), run it through `marketing-skill/content-production/scripts/brand_voice_analyzer.py` to get a voice profile (formality, tone, perspective). Use the profile to inform design style and copy framework selection:
|
|
39
|
+
- formal + professional โ **enterprise** style, **AIDA** framework
|
|
40
|
+
- casual + friendly โ **bold-startup** style, **BAB** framework
|
|
41
|
+
- professional + authoritative โ **dark-saas** style, **PAS** framework
|
|
42
|
+
- casual + conversational โ **clean-minimal** style, **BAB** framework
|
|
43
|
+
3. **Select design style** โ map the user's choice (or infer from brand voice analysis) to one of the four Tailwind class sets in the Design Style Reference.
|
|
44
|
+
4. **Apply copy framework** โ write all headline and body copy using the chosen framework (PAS / AIDA / BAB) before generating components. Match the voice profile's formality and tone throughout.
|
|
45
|
+
5. **Generate sections in order** โ Hero โ Features โ Pricing โ FAQ โ Testimonials โ CTA โ Footer. Skip sections not relevant to the product.
|
|
46
|
+
6. **Validate against SEO checklist** โ run through every item in the SEO Checklist before outputting final code. Fix any gaps inline.
|
|
47
|
+
7. **Output final components** โ deliver complete, copy-paste-ready TSX files with all Tailwind classes, SEO meta, and structured data included.
|
|
48
|
+
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
## Triggering This Skill
|
|
52
|
+
|
|
53
|
+
```
|
|
54
|
+
Product: [name]
|
|
55
|
+
Tagline: [one sentence value prop]
|
|
56
|
+
Target audience: [who they are]
|
|
57
|
+
Key pain point: [what problem you solve]
|
|
58
|
+
Key benefit: [primary outcome]
|
|
59
|
+
Pricing tiers: [free/pro/enterprise or describe]
|
|
60
|
+
Design style: dark-saas | clean-minimal | bold-startup | enterprise
|
|
61
|
+
Copy framework: PAS | AIDA | BAB
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## Design Style Reference
|
|
67
|
+
|
|
68
|
+
| Style | Background | Accent | Cards | CTA Button |
|
|
69
|
+
|---|---|---|---|---|
|
|
70
|
+
| **Dark SaaS** | `bg-gray-950 text-white` | `violet-500/400` | `bg-gray-900 border border-gray-800` | `bg-violet-600 hover:bg-violet-500` |
|
|
71
|
+
| **Clean Minimal** | `bg-white text-gray-900` | `blue-600` | `bg-gray-50 border border-gray-200 rounded-2xl` | `bg-blue-600 hover:bg-blue-700` |
|
|
72
|
+
| **Bold Startup** | `bg-white text-gray-900` | `orange-500` | `shadow-xl rounded-3xl` | `bg-orange-500 hover:bg-orange-600 text-white` |
|
|
73
|
+
| **Enterprise** | `bg-slate-50 text-slate-900` | `slate-700` | `bg-white border border-slate-200 shadow-sm` | `bg-slate-900 hover:bg-slate-800 text-white` |
|
|
74
|
+
|
|
75
|
+
> **Bold Startup** headings: add `font-black tracking-tight` to all `<h1>`/`<h2>` elements.
|
|
76
|
+
|
|
77
|
+
---
|
|
78
|
+
|
|
79
|
+
## Copy Frameworks
|
|
80
|
+
|
|
81
|
+
**PAS (Problem โ Agitate โ Solution)**
|
|
82
|
+
- H1: Painful state they're in
|
|
83
|
+
- Sub: What happens if they don't fix it
|
|
84
|
+
- CTA: What you offer
|
|
85
|
+
- *Example โ H1:* "Your team wastes 3 hours a day on manual reporting" / *Sub:* "Every hour spent on spreadsheets is an hour not closing deals. Your competitors are already automated." / *CTA:* "Automate your reports in 10 minutes โ"
|
|
86
|
+
|
|
87
|
+
**AIDA (Attention โ Interest โ Desire โ Action)**
|
|
88
|
+
- H1: Bold attention-grabbing statement โ Sub: Interesting fact or benefit โ Features: Desire-building proof points โ CTA: Clear action
|
|
89
|
+
|
|
90
|
+
**BAB (Before โ After โ Bridge)**
|
|
91
|
+
- H1: "[Before state] โ [After state]" โ Sub: "Here's how [product] bridges the gap" โ Features: How it works (the bridge)
|
|
92
|
+
|
|
93
|
+
---
|
|
94
|
+
|
|
95
|
+
## Representative Component: Hero (Centered Gradient โ Dark SaaS)
|
|
96
|
+
|
|
97
|
+
Use this as the structural template for all hero variants. Swap layout classes, gradient direction, and image placement for split, video-bg, and minimal variants.
|
|
98
|
+
|
|
99
|
+
```tsx
|
|
100
|
+
export function HeroCentered() {
|
|
101
|
+
return (
|
|
102
|
+
<section className="relative flex min-h-screen flex-col items-center justify-center overflow-hidden bg-gray-950 px-4 text-center">
|
|
103
|
+
<div className="absolute inset-0 bg-gradient-to-b from-violet-900/20 to-transparent" />
|
|
104
|
+
<div className="pointer-events-none absolute -top-40 left-1/2 h-[600px] w-[600px] -translate-x-1/2 rounded-full bg-violet-600/20 blur-3xl" />
|
|
105
|
+
<div className="relative z-10 max-w-4xl">
|
|
106
|
+
<div className="mb-6 inline-flex items-center gap-2 rounded-full border border-violet-500/30 bg-violet-500/10 px-4 py-1.5 text-sm text-violet-300">
|
|
107
|
+
<span className="h-1.5 w-1.5 rounded-full bg-violet-400" />
|
|
108
|
+
Now in public beta
|
|
109
|
+
</div>
|
|
110
|
+
<h1 className="mb-6 text-5xl font-bold tracking-tight text-white md:text-7xl">
|
|
111
|
+
Ship faster.<br />
|
|
112
|
+
<span className="bg-gradient-to-r from-violet-400 to-pink-400 bg-clip-text text-transparent">
|
|
113
|
+
Break less.
|
|
114
|
+
</span>
|
|
115
|
+
</h1>
|
|
116
|
+
<p className="mx-auto mb-10 max-w-2xl text-xl text-gray-400">
|
|
117
|
+
The deployment platform that catches errors before your users do.
|
|
118
|
+
Zero config. Instant rollbacks. Real-time monitoring.
|
|
119
|
+
</p>
|
|
120
|
+
<div className="flex flex-col items-center gap-4 sm:flex-row sm:justify-center">
|
|
121
|
+
<Button size="lg" className="bg-violet-600 text-white hover:bg-violet-500 px-8">
|
|
122
|
+
Start free trial
|
|
123
|
+
</Button>
|
|
124
|
+
<Button size="lg" variant="outline" className="border-gray-700 text-gray-300">
|
|
125
|
+
See how it works โ
|
|
126
|
+
</Button>
|
|
127
|
+
</div>
|
|
128
|
+
<p className="mt-4 text-sm text-gray-500">No credit card required ยท 14-day free trial</p>
|
|
129
|
+
</div>
|
|
130
|
+
</section>
|
|
131
|
+
)
|
|
132
|
+
}
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
## Other Section Patterns
|
|
138
|
+
|
|
139
|
+
### Feature Section (Alternating)
|
|
140
|
+
|
|
141
|
+
Map over a `features` array with `{ title, description, image, badge }`. Toggle layout direction with `i % 2 === 1 ? "lg:flex-row-reverse" : ""`. Use `<Image>` with explicit `width`/`height` and `rounded-2xl shadow-xl`. Wrap in `<section className="py-24">` with `max-w-6xl` container.
|
|
142
|
+
|
|
143
|
+
### Pricing Table
|
|
144
|
+
|
|
145
|
+
Map over a `plans` array with `{ name, price, description, features[], cta, highlighted }`. Highlighted plan gets `border-2 border-violet-500 bg-violet-950/50 ring-4 ring-violet-500/20`; others get `border border-gray-800 bg-gray-900`. Render `null` price as "Custom". Use `<Check>` icon per feature row. Layout: `grid gap-8 lg:grid-cols-3`.
|
|
146
|
+
|
|
147
|
+
### FAQ with Schema Markup
|
|
148
|
+
|
|
149
|
+
Inject `FAQPage` JSON-LD via `<script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }} />` inside the section. Map FAQs with `{ q, a }` into shadcn `<Accordion>` with `type="single" collapsible`. Container: `max-w-3xl`.
|
|
150
|
+
|
|
151
|
+
### Testimonials, CTA, Footer
|
|
152
|
+
|
|
153
|
+
- **Testimonials:** Grid (`grid-cols-1 md:grid-cols-3`) or single-quote hero block with avatar, name, role, and quote text.
|
|
154
|
+
- **CTA Banner:** Full-width section with headline, subhead, and two buttons (primary + ghost). Add trust signals (money-back guarantee, logo strip) immediately below.
|
|
155
|
+
- **Footer:** Logo + nav columns + social links + legal. Use `border-t border-gray-800` separator.
|
|
156
|
+
|
|
157
|
+
---
|
|
158
|
+
|
|
159
|
+
## SEO Checklist
|
|
160
|
+
|
|
161
|
+
- [ ] `<title>` tag: primary keyword + brand (50โ60 chars)
|
|
162
|
+
- [ ] Meta description: benefit + CTA (150โ160 chars)
|
|
163
|
+
- [ ] OG image: 1200ร630px with product name and tagline
|
|
164
|
+
- [ ] H1: one per page, includes primary keyword
|
|
165
|
+
- [ ] Structured data: FAQPage, Product, or Organization schema
|
|
166
|
+
- [ ] Canonical URL set
|
|
167
|
+
- [ ] Image alt text on all `<Image>` components
|
|
168
|
+
- [ ] robots.txt and sitemap.xml configured
|
|
169
|
+
- [ ] Core Web Vitals: LCP < 1s, CLS < 0.1
|
|
170
|
+
- [ ] Mobile viewport meta tag present
|
|
171
|
+
- [ ] Internal linking to pricing and docs
|
|
172
|
+
|
|
173
|
+
> **Validation step:** Before outputting final code, verify every checklist item above is satisfied. Fix any gaps inline โ do not skip items.
|
|
174
|
+
|
|
175
|
+
---
|
|
176
|
+
|
|
177
|
+
## Performance Targets
|
|
178
|
+
|
|
179
|
+
| Metric | Target | Technique |
|
|
180
|
+
|---|---|---|
|
|
181
|
+
| LCP | < 1s | Preload hero image, use `priority` on Next/Image |
|
|
182
|
+
| CLS | < 0.1 | Set explicit width/height on all images |
|
|
183
|
+
| FID/INP | < 100ms | Defer non-critical JS, use `loading="lazy"` |
|
|
184
|
+
| TTFB | < 200ms | Use ISR or static generation for landing pages |
|
|
185
|
+
| Bundle | < 100KB JS | Audit with `@next/bundle-analyzer` |
|
|
186
|
+
|
|
187
|
+
---
|
|
188
|
+
|
|
189
|
+
## Common Pitfalls
|
|
190
|
+
|
|
191
|
+
- Hero image not preloaded โ add `priority` prop to first `<Image>`
|
|
192
|
+
- Missing mobile breakpoints โ always design mobile-first with `sm:` prefixes
|
|
193
|
+
- CTA copy too vague โ "Get started" beats "Learn more"; "Start free trial" beats "Sign up"
|
|
194
|
+
- Pricing page missing trust signals โ add money-back guarantee and testimonials near CTA
|
|
195
|
+
- No above-the-fold CTA on mobile โ ensure button is visible without scrolling on 375px viewport
|
|
196
|
+
|
|
197
|
+
---
|
|
198
|
+
|
|
199
|
+
## Related Skills
|
|
200
|
+
|
|
201
|
+
- **Brand Voice Analyzer** (`marketing-skill/content-production/scripts/brand_voice_analyzer.py`) โ Run before generation to establish voice profile and ensure copy consistency
|
|
202
|
+
- **UI Design System** (`product-team/ui-design-system/`) โ Generate design tokens from brand color before building the page
|
|
203
|
+
- **Competitive Teardown** (`product-team/competitive-teardown/`) โ Competitive positioning informs landing page messaging and differentiation
|
|
@@ -0,0 +1,176 @@
|
|
|
1
|
+
# High-Converting Landing Page Patterns
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
|
|
5
|
+
This reference catalogs proven landing page design patterns that drive higher conversion rates. Each pattern includes placement guidance, implementation notes, and A/B testing priorities.
|
|
6
|
+
|
|
7
|
+
## Hero Section Layouts
|
|
8
|
+
|
|
9
|
+
### Pattern 1: Left Copy + Right Product Screenshot
|
|
10
|
+
- **Best for:** SaaS products with a strong visual UI
|
|
11
|
+
- **Structure:** Headline, subheadline, CTA on left (60%); product screenshot on right (40%)
|
|
12
|
+
- **Why it works:** F-pattern reading leads with copy, product image provides proof
|
|
13
|
+
- **Conversion lift:** Baseline pattern, strong performer across industries
|
|
14
|
+
|
|
15
|
+
### Pattern 2: Centered Copy + Full-Width Background
|
|
16
|
+
- **Best for:** Brand-driven products, consumer apps
|
|
17
|
+
- **Structure:** Centered headline, subheadline, CTA over background image/gradient
|
|
18
|
+
- **Why it works:** Focuses attention on single message, high visual impact
|
|
19
|
+
- **Note:** Ensure text contrast against background for readability
|
|
20
|
+
|
|
21
|
+
### Pattern 3: Video Hero
|
|
22
|
+
- **Best for:** Complex products requiring demonstration
|
|
23
|
+
- **Structure:** Short headline + embedded video (60-90 seconds) + CTA below
|
|
24
|
+
- **Why it works:** Video explains what text cannot, increases time on page
|
|
25
|
+
- **Note:** Always include thumbnail; autoplay is often counterproductive
|
|
26
|
+
|
|
27
|
+
### Pattern 4: Interactive Demo
|
|
28
|
+
- **Best for:** Developer tools, data products, design tools
|
|
29
|
+
- **Structure:** Minimal copy + embedded interactive product experience
|
|
30
|
+
- **Why it works:** Hands-on experience converts better than description
|
|
31
|
+
- **Note:** Keep demo focused on one "aha moment" workflow
|
|
32
|
+
|
|
33
|
+
## Social Proof Placement
|
|
34
|
+
|
|
35
|
+
### Logo Bar
|
|
36
|
+
- **Position:** Immediately below hero section
|
|
37
|
+
- **Count:** 5-7 logos for credibility without clutter
|
|
38
|
+
- **Label:** "Trusted by" or "Used by teams at"
|
|
39
|
+
- **Selection:** Mix recognizable brands with relevant industry logos
|
|
40
|
+
|
|
41
|
+
### Testimonial Cards
|
|
42
|
+
- **Position:** After feature explanation sections
|
|
43
|
+
- **Format:** Photo + name + title + company + specific quote
|
|
44
|
+
- **Best quotes:** Include measurable outcomes ("Saved 10 hours/week")
|
|
45
|
+
- **Layout:** 2-3 testimonials in a row, carousel for more
|
|
46
|
+
|
|
47
|
+
### Case Study Callouts
|
|
48
|
+
- **Position:** Mid-page, before pricing
|
|
49
|
+
- **Format:** Company logo + headline metric + "Read the story" link
|
|
50
|
+
- **Example:** "Acme Corp reduced onboarding time by 60%"
|
|
51
|
+
|
|
52
|
+
### Social Proof Numbers
|
|
53
|
+
- **Position:** Near CTA or in dedicated trust section
|
|
54
|
+
- **Format:** Large number + descriptor (e.g., "50,000+ teams", "4.8/5 rating")
|
|
55
|
+
- **Selection:** Choose 3-4 most impressive metrics
|
|
56
|
+
|
|
57
|
+
## Pricing Table Designs
|
|
58
|
+
|
|
59
|
+
### Good/Better/Best (3-Tier)
|
|
60
|
+
- Most effective for SaaS with clear feature tiers
|
|
61
|
+
- Highlight recommended plan with visual emphasis
|
|
62
|
+
- Show annual discount prominently
|
|
63
|
+
- Include feature comparison matrix below
|
|
64
|
+
|
|
65
|
+
### Simple Two-Tier
|
|
66
|
+
- Free/Pro or Starter/Professional
|
|
67
|
+
- Best for PLG products with clear upgrade trigger
|
|
68
|
+
- Minimize decision fatigue
|
|
69
|
+
|
|
70
|
+
### Enterprise Custom
|
|
71
|
+
- Replace price with "Contact Sales" for high-ACV products
|
|
72
|
+
- List enterprise-specific features (SSO, SLA, dedicated support)
|
|
73
|
+
- Include a "Talk to Sales" CTA, not just a form
|
|
74
|
+
|
|
75
|
+
### Pricing Psychology
|
|
76
|
+
- Anchor with highest-priced plan first (or in the middle with visual highlight)
|
|
77
|
+
- Use monthly price with annual billing toggle
|
|
78
|
+
- Show savings percentage for annual plans
|
|
79
|
+
- Round prices ending in 9 (e.g., $49/mo, $99/mo)
|
|
80
|
+
|
|
81
|
+
## Trust Signals
|
|
82
|
+
|
|
83
|
+
### Security Badges
|
|
84
|
+
- SOC 2, ISO 27001, GDPR compliance badges
|
|
85
|
+
- SSL certificate indicator
|
|
86
|
+
- Place near forms and payment sections
|
|
87
|
+
|
|
88
|
+
### Guarantees
|
|
89
|
+
- Money-back guarantee with specific timeframe
|
|
90
|
+
- Free trial with no credit card requirement
|
|
91
|
+
- SLA uptime commitments
|
|
92
|
+
|
|
93
|
+
### Awards & Recognition
|
|
94
|
+
- Industry awards (best of, top rated)
|
|
95
|
+
- Analyst recognition (Gartner, Forrester, G2 Leader)
|
|
96
|
+
- Media mentions (as seen in logos)
|
|
97
|
+
|
|
98
|
+
### Real-Time Activity
|
|
99
|
+
- "X people signed up today" (use real data only)
|
|
100
|
+
- Recent activity feed
|
|
101
|
+
- Live user count
|
|
102
|
+
|
|
103
|
+
## Urgency Elements
|
|
104
|
+
|
|
105
|
+
### Ethical Urgency
|
|
106
|
+
- Limited-time pricing (with real deadline)
|
|
107
|
+
- Early adopter benefits (extra features, lower price)
|
|
108
|
+
- Cohort-based enrollment (actual capacity limits)
|
|
109
|
+
|
|
110
|
+
### Avoid
|
|
111
|
+
- Fake countdown timers that reset
|
|
112
|
+
- False scarcity ("only 3 left" when unlimited)
|
|
113
|
+
- Pressure tactics that erode trust
|
|
114
|
+
|
|
115
|
+
## Form Optimization
|
|
116
|
+
|
|
117
|
+
### Field Reduction
|
|
118
|
+
- Every additional field reduces conversion ~10%
|
|
119
|
+
- Start with email only, progressive profiling later
|
|
120
|
+
- Use single-column layouts for forms
|
|
121
|
+
|
|
122
|
+
### Smart Defaults
|
|
123
|
+
- Pre-fill country based on IP
|
|
124
|
+
- Auto-detect company from email domain
|
|
125
|
+
- Default to most popular plan
|
|
126
|
+
|
|
127
|
+
### Inline Validation
|
|
128
|
+
- Validate fields on blur, not on submit
|
|
129
|
+
- Show success states (green checkmark)
|
|
130
|
+
- Provide helpful error messages
|
|
131
|
+
|
|
132
|
+
### Multi-Step Forms
|
|
133
|
+
- Break long forms into 2-3 steps with progress indicator
|
|
134
|
+
- Put easiest questions first to build commitment
|
|
135
|
+
- Allow saving progress for complex forms
|
|
136
|
+
|
|
137
|
+
## Mobile-First Patterns
|
|
138
|
+
|
|
139
|
+
### Thumb-Friendly Design
|
|
140
|
+
- CTAs in thumb zone (bottom 40% of screen)
|
|
141
|
+
- Minimum tap target: 44x44px
|
|
142
|
+
- Adequate spacing between interactive elements
|
|
143
|
+
|
|
144
|
+
### Content Priority
|
|
145
|
+
- Lead with most compelling content (no scrolling to find CTA)
|
|
146
|
+
- Collapse secondary information into accordions
|
|
147
|
+
- Use sticky CTA bar on scroll
|
|
148
|
+
|
|
149
|
+
### Performance
|
|
150
|
+
- Target <3s load time on 3G
|
|
151
|
+
- Lazy-load images below fold
|
|
152
|
+
- Minimize JavaScript execution
|
|
153
|
+
|
|
154
|
+
## A/B Testing Priority Matrix
|
|
155
|
+
|
|
156
|
+
Test these elements in order of expected impact:
|
|
157
|
+
|
|
158
|
+
| Priority | Element | Expected Impact | Effort |
|
|
159
|
+
|----------|---------|----------------|--------|
|
|
160
|
+
| 1 | Headline | High | Low |
|
|
161
|
+
| 2 | CTA text and color | High | Low |
|
|
162
|
+
| 3 | Hero image/video | High | Medium |
|
|
163
|
+
| 4 | Social proof placement | Medium | Low |
|
|
164
|
+
| 5 | Form fields (fewer) | Medium | Low |
|
|
165
|
+
| 6 | Pricing presentation | Medium | Medium |
|
|
166
|
+
| 7 | Page length | Medium | High |
|
|
167
|
+
| 8 | Testimonial selection | Low | Low |
|
|
168
|
+
| 9 | Color scheme | Low | Medium |
|
|
169
|
+
| 10 | Font choices | Low | Low |
|
|
170
|
+
|
|
171
|
+
### Testing Best Practices
|
|
172
|
+
- Test one variable at a time for clear attribution
|
|
173
|
+
- Run tests for minimum 2 weeks or 1,000 visitors per variant
|
|
174
|
+
- Use 95% statistical significance threshold
|
|
175
|
+
- Document all test results for institutional knowledge
|
|
176
|
+
- Winner becomes new control for next test iteration
|
|
@@ -0,0 +1,177 @@
|
|
|
1
|
+
# Landing Page Copywriting Frameworks
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
|
|
5
|
+
Four copy frameworks with worked SaaS examples you can adapt. Each framework includes a complete before/after example plus specific guidelines for each section.
|
|
6
|
+
|
|
7
|
+
## 1. AIDA Framework (Attention - Interest - Desire - Action)
|
|
8
|
+
|
|
9
|
+
The classic direct response formula, ideal for product landing pages.
|
|
10
|
+
|
|
11
|
+
**Example โ Project management SaaS:**
|
|
12
|
+
|
|
13
|
+
> **Attention:** "Your Team Loses 12 Hours Every Sprint to Status Meetings"
|
|
14
|
+
>
|
|
15
|
+
> **Interest:** "Engineering teams at Series A-C startups spend 23% of their week in sync meetings โ not writing code. We tracked 847 teams over 6 months. The pattern was clear: the more people in a standup, the less code shipped that day."
|
|
16
|
+
>
|
|
17
|
+
> **Desire:** "Teams using AsyncStand ship 31% more story points per sprint. No more 15-person standups where 13 people zone out. Replace your daily sync with a 2-minute async check-in that your engineers actually complete (94% response rate vs 67% attendance for live standups)."
|
|
18
|
+
>
|
|
19
|
+
> **Action:** "Start Your Free 14-Day Trial โ No Credit Card Required"
|
|
20
|
+
|
|
21
|
+
### Attention
|
|
22
|
+
- Lead with a specific, quantified pain point (not vague claims)
|
|
23
|
+
- Weak: "Save time on meetings" โ Strong: "Your Team Loses 12 Hours Every Sprint to Status Meetings"
|
|
24
|
+
- Keep headlines under 10 words for maximum impact
|
|
25
|
+
|
|
26
|
+
### Interest
|
|
27
|
+
- Back up the headline with specific data or a relatable scenario
|
|
28
|
+
- Weak: "Meetings waste time" โ Strong: "We tracked 847 teams โ the more people in standup, the less code shipped that day"
|
|
29
|
+
- Use their language: mirror words from customer reviews, support tickets, and G2 feedback
|
|
30
|
+
|
|
31
|
+
### Desire
|
|
32
|
+
- Stack measurable outcomes, not features
|
|
33
|
+
- Weak: "AI-powered async updates" โ Strong: "31% more story points per sprint, 94% response rate"
|
|
34
|
+
- Compare directly to the status quo they already endure
|
|
35
|
+
|
|
36
|
+
### Action
|
|
37
|
+
- Single, clear CTA with action-oriented verb
|
|
38
|
+
- Reduce friction: "No credit card required," "Set up in 2 minutes"
|
|
39
|
+
- Repeat CTA after each major content block
|
|
40
|
+
|
|
41
|
+
## 2. PAS Framework (Problem - Agitate - Solution)
|
|
42
|
+
|
|
43
|
+
Best for pain-point-driven products where the problem is well understood.
|
|
44
|
+
|
|
45
|
+
**Example โ Expense management tool:**
|
|
46
|
+
|
|
47
|
+
> **Problem:** "Your finance team is still chasing receipts in Slack DMs."
|
|
48
|
+
>
|
|
49
|
+
> **Agitate:** "Last quarter, your team spent 46 hours manually reconciling expenses across email threads, shared drives, and 'I'll submit it later' promises. That's $4,200 in payroll โ spent on data entry. And when audit season hits? Good luck finding that client dinner receipt from February."
|
|
50
|
+
>
|
|
51
|
+
> **Solution:** "Snap a photo of the receipt. ExpenseFlow auto-extracts vendor, amount, and category in 3 seconds. Your monthly close drops from 5 days to 1. 2,400 finance teams already made the switch."
|
|
52
|
+
|
|
53
|
+
### Problem
|
|
54
|
+
- Name the exact scenario (not the abstract category)
|
|
55
|
+
- Weak: "Expense tracking is hard" โ Strong: "Your finance team is still chasing receipts in Slack DMs"
|
|
56
|
+
- Mirror language from reviews and support tickets
|
|
57
|
+
|
|
58
|
+
### Agitate
|
|
59
|
+
- Quantify the cost in dollars, hours, or missed opportunities
|
|
60
|
+
- Weak: "This costs you money" โ Strong: "46 hours last quarter, $4,200 in payroll โ on data entry"
|
|
61
|
+
- Acknowledge the workarounds they've tried and why those fail too
|
|
62
|
+
|
|
63
|
+
### Solution
|
|
64
|
+
- Lead with the user action, not the technology: "Snap a photo" not "AI-powered OCR"
|
|
65
|
+
- Include one proof point: number of customers, time saved, or before/after metric
|
|
66
|
+
- Make the mechanism clear in one sentence: what happens when they use it
|
|
67
|
+
|
|
68
|
+
## 3. BAB Framework (Before - After - Bridge)
|
|
69
|
+
|
|
70
|
+
Ideal for aspirational products and lifestyle-oriented landing pages.
|
|
71
|
+
|
|
72
|
+
**Example โ Sales enablement platform:**
|
|
73
|
+
|
|
74
|
+
> **Before:** "It's 9 PM. You're rebuilding a deck for tomorrow's demo because the prospect is in healthcare, not fintech. You copy-paste from three old decks, pray the logos are right, and rehearse the new talk track in the shower."
|
|
75
|
+
>
|
|
76
|
+
> **After:** "It's 9 AM. You type 'healthcare, 200-bed hospital, HIPAA-concerned CTO.' DeckGen builds your slides in 40 seconds โ case studies, compliance badges, ROI calculator pre-loaded. You walk into the call with the best deck your prospect has ever seen."
|
|
77
|
+
>
|
|
78
|
+
> **Bridge:** "DeckGen connects to your CRM, learns your win patterns, and generates prospect-specific decks in under a minute. 340 AEs at companies like Stripe and Notion already use it. Start free โ your first 5 decks are on us."
|
|
79
|
+
|
|
80
|
+
### Before
|
|
81
|
+
- Describe a specific, lived moment โ not an abstract pain category
|
|
82
|
+
- Weak: "Sales decks take too long" โ Strong: "It's 9 PM. You're rebuilding a deck for tomorrow's demo..."
|
|
83
|
+
- Use second person and present tense to make it feel immediate
|
|
84
|
+
|
|
85
|
+
### After
|
|
86
|
+
- Same level of specificity โ show the transformed version of that exact moment
|
|
87
|
+
- Include a measurable outcome: "40 seconds," "best deck your prospect has ever seen"
|
|
88
|
+
- The after state should feel effortless compared to the before
|
|
89
|
+
|
|
90
|
+
### Bridge
|
|
91
|
+
- Name the product explicitly and explain the mechanism in one sentence
|
|
92
|
+
- Include one social proof data point
|
|
93
|
+
- End with a low-friction CTA that connects to the after state
|
|
94
|
+
|
|
95
|
+
## 4. 4Ps Framework (Promise - Picture - Proof - Push)
|
|
96
|
+
|
|
97
|
+
Strong for SaaS and B2B landing pages with measurable outcomes.
|
|
98
|
+
|
|
99
|
+
### Promise
|
|
100
|
+
- Make a clear, specific, believable promise
|
|
101
|
+
- Tie it to a measurable outcome
|
|
102
|
+
- Example: "Reduce customer churn by 25% in 90 days"
|
|
103
|
+
|
|
104
|
+
### Picture
|
|
105
|
+
- Help the reader visualize success
|
|
106
|
+
- Use scenarios they can relate to
|
|
107
|
+
- Show the product in context (screenshots, demos)
|
|
108
|
+
|
|
109
|
+
### Proof
|
|
110
|
+
- Back the promise with evidence
|
|
111
|
+
- Customer testimonials with specific results
|
|
112
|
+
- Case studies with before/after metrics
|
|
113
|
+
- Third-party validation (awards, analyst reports)
|
|
114
|
+
|
|
115
|
+
### Push
|
|
116
|
+
- Give a compelling reason to act now
|
|
117
|
+
- Limited-time offer, bonus, or guarantee
|
|
118
|
+
- Risk reversal (money-back guarantee, free trial)
|
|
119
|
+
|
|
120
|
+
## Headline Formulas
|
|
121
|
+
|
|
122
|
+
### Benefit-Driven
|
|
123
|
+
- "Get [Desired Outcome] Without [Common Objection]"
|
|
124
|
+
- "[Specific Result] in [Timeframe]"
|
|
125
|
+
- "The [Adjective] Way to [Achieve Goal]"
|
|
126
|
+
|
|
127
|
+
### Problem-Driven
|
|
128
|
+
- "Stop [Painful Activity]. Start [Better Alternative]."
|
|
129
|
+
- "Tired of [Problem]? There's a Better Way."
|
|
130
|
+
- "[Problem]? Not Anymore."
|
|
131
|
+
|
|
132
|
+
### Social Proof-Driven
|
|
133
|
+
- "[Number] Teams Trust [Product] to [Outcome]"
|
|
134
|
+
- "Why [Notable Company] Switched to [Product]"
|
|
135
|
+
- "Rated #1 for [Category] by [Authority]"
|
|
136
|
+
|
|
137
|
+
### Question-Driven
|
|
138
|
+
- "What If You Could [Desirable Outcome]?"
|
|
139
|
+
- "Ready to [Transformation]?"
|
|
140
|
+
- "Still [Painful Status Quo]?"
|
|
141
|
+
|
|
142
|
+
## CTA Best Practices
|
|
143
|
+
|
|
144
|
+
### Language
|
|
145
|
+
- Use first-person: "Start My Free Trial" > "Start Your Free Trial"
|
|
146
|
+
- Be specific: "Get My Report" > "Submit"
|
|
147
|
+
- Include benefit: "Start Saving Time" > "Sign Up"
|
|
148
|
+
- Add urgency naturally: "Start Free Today" > "Sign Up Now!!!"
|
|
149
|
+
|
|
150
|
+
### Placement
|
|
151
|
+
- Primary CTA above the fold
|
|
152
|
+
- Repeat after each major content section
|
|
153
|
+
- Sticky CTA on scroll (mobile especially)
|
|
154
|
+
- Exit-intent as last chance
|
|
155
|
+
|
|
156
|
+
### Design
|
|
157
|
+
- High contrast color (stands out from page palette)
|
|
158
|
+
- Sufficient whitespace around the button
|
|
159
|
+
- Large enough to tap on mobile (min 44x44px)
|
|
160
|
+
- Micro-copy below button to reduce anxiety ("No credit card required")
|
|
161
|
+
|
|
162
|
+
## Above-the-Fold Principles
|
|
163
|
+
|
|
164
|
+
The first viewport must accomplish these goals within 5 seconds:
|
|
165
|
+
1. **Communicate what you do** - Clear, jargon-free headline
|
|
166
|
+
2. **Show who it's for** - Audience identification
|
|
167
|
+
3. **Demonstrate value** - Primary benefit or outcome
|
|
168
|
+
4. **Provide next step** - Visible CTA button
|
|
169
|
+
5. **Build credibility** - One trust signal (logo bar, metric, badge)
|
|
170
|
+
|
|
171
|
+
### Above-the-Fold Checklist
|
|
172
|
+
- [ ] Headline states primary benefit (under 10 words)
|
|
173
|
+
- [ ] Subheadline adds specificity or addresses objection
|
|
174
|
+
- [ ] Hero image/video shows product in use
|
|
175
|
+
- [ ] CTA button is visible without scrolling
|
|
176
|
+
- [ ] At least one trust signal present
|
|
177
|
+
- [ ] No jargon or ambiguity in messaging
|