| name | pitch-landing |
| description | Use when asked to structure a landing page for positioning, plan a
conversion-optimized page layout, or design a launch page. Examples: "landing
page for product launch", "conversion-optimized layout for SaaS"
|
| allowed-tools | Read, Bash, Glob, Grep |
| version | 0.6.6 |
| author | tonone-ai <hello@tonone.ai> |
| license | MIT |
pitch-landing โ Launch & Positioning Landing Page
Follow the output format defined in docs/output-kit.md โ 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
When to use
User needs a landing page structured around product positioning, launch messaging, or conversion for a specific audience.
Workflow
- Identify product type and positioning anchor from user request or brief
- Search landing page patterns:
python3 -m pitch_agent.uiux search --domain landing --query "{product_type}" --limit 3
- Search product reasoning for audience + messaging context:
python3 -m pitch_agent.uiux search --domain product --query "{product_type}" --limit 3
- Layer in positioning: CTA strategy, social proof placement, objection handling
- Output section order with conversion and messaging optimization
Output format
โโ Launch Landing Page โ {product_type} โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ # โ Section โ Purpose โ CTA? โ
โโโโโโผโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโค
โ 1 โ {section_name} โ {purpose} โ Primary CTA โ
โ 2 โ {section_name} โ {purpose} โ โ โ
โ 3 โ {section_name} โ {purpose} โ Secondary CTA โ
โ โฆ โ โฆ โ โฆ โ โฆ โ
โโโโโโดโโโโโโโโโโโโโโโโโโโโโดโโโโโโโโโโโโโโโโโโโโโโโโโโโโโดโโโโโโโโโโโโโโโโ
CTA strategy: {cta_strategy}
Social proof: {social_proof_placement}
Objection handling: {objection_section}
Positioning anchor: {positioning_anchor}
Anti-patterns
- Never structure copy without a clear positioning anchor (who it's for + what makes it different)
- Never add sections that don't serve conversion or objection handling
- Never place social proof after the primary CTA โ it should reinforce before the ask
- Never launch without a single, unambiguous primary CTA per viewport
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt โ box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
