pitch-landing
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
Provided by Plugin
tonone
Engineering + Product + Operations + Legal + Design + Data Science + Security Operations + Developer Experience + Infrastructure Specialist + AI Operations team — 100 agents as Claude Code specialists. Infrastructure, DevOps, backend, security, ML/AI, mobile, UX, analytics, growth, revenue, content, PR, customer success, finance, people, operations, support, contracts, compliance, IP, governance, regulatory, color systems, typography, motion, accessibility, design tokens, forecasting, feature engineering, model training, drift monitoring, vector search, LLM fine-tuning, pen testing, detection engineering, incident response, zero trust, API docs, SDK design, developer onboarding, Kubernetes, Terraform, FinOps, service mesh, edge computing, caching, queuing, multi-cloud, chaos engineering, model deployment, LLM evaluation, AI observability, guardrails, prompt engineering, embeddings, ranking, and more.
Installation
This skill is included in the tonone plugin:
/plugin install tonone@claude-code-plugins-plusClick to copy
Instructions
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.