| Use when asked to structure a landing page, design page layout for conversion, for SaaS", "conversion-optimized layout"
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill draft-landing
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
User needs a landing page structure, section order, or conversion-optimized layout. Product type is known or discoverable.
python3 -m draft_agent.uiux search --domain landing --query "{product_type}" --limit 3
python3 -m draft_agent.uiux search --domain product --query "{product_type}" --limit 3
┌─ Landing Page IA — {product_type} ──────────────────────────────────┐
│ # │ Section │ Purpose │ CTA? │
├────┼────────────────────┼────────────────────────────┼───────────────┤
│ 1 │ {section_name} │ {purpose} │ Primary CTA │
│ 2 │ {section_name} │ {purpose} │ — │
│ 3 │ {section_name} │ {purpose} │ Secondary CTA │
│ … │ … │ … │ … │
└────┴────────────────────┴────────────────────────────┴───────────────┘
Conversion strategy: {strategy}
CTA copy guidance: {cta_guidance}
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.
Take jeremylongshore/draft-landing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.