Landing page
Production-ready AI agent profiles for Claude Code, Cursor, and Codex. Search, install, and contribute ForgeCat packages.
npx -y skills add nota-america/forgecat-agent-profiles --skill landing-pageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 24 stars24 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls.
SKILL.md
5.2 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it
Landing Page (High‑Conversion) — Web Design Skill
A landing page is not a homepage. A homepage serves multiple intents. A landing page wins one intent: one offer → one audience → one primary action.
Before you design/write
Gather (ask if missing):
1) Page purpose
- What is the ONE primary action? (trial, demo, buy, waitlist, download)
- What’s the offer? (exactly what do they get?)
- What counts as conversion? (click, signup, purchase)
2) Audience + context
- Who is the ICP?
- What problem are they trying to solve?
- Top 3 objections (why they don’t convert today)
- Traffic source: ads / search / social / email
- What do visitors already know when they land?
3) Proof + assets
- Any proof points: logos, testimonials, numbers, case studies
- Screenshots, demo video, product GIFs
- Guarantees / refund / cancellation terms
4) Constraints
- Brand voice: casual vs professional
- Design direction: minimal editorial vs playful 3D vs glass UI
- Mobile priority?
Core structure (what it should include)
Above the fold (must)
- Headline (outcome + audience)
- Subheadline (clarifies “how” + adds specificity)
- Primary CTA (clear verb + what they get)
- One proof signal (logo strip / stat / short testimonial)
- Hero visual (product screenshot/video) or a strong illustration
Mid page (argument)
- Problem → solution (1 section)
- Benefits (3–5, outcome-driven)
- How it works (3 steps)
- Social proof (testimonials/case study)
Bottom (objection handling)
- FAQ (6–12 Q/A)
- Risk reversal (trial, cancel anytime, guarantee)
- Final CTA (same as top)
Layout types (pick one)
A) Classic hero + sections (most common)
Best when:
- product is understandable with a hero screenshot
B) Long-form story (sales page)
Best when:
- you need to educate + overcome skepticism
C) Minimal conversion page
Best when:
- high-intent traffic (email → known users)
- short offer (download, waitlist)
D) Comparison landing page
Best when:
- search intent includes alternatives (“X vs Y”, “best for…”)—usually paired with SEO pages
High‑conversion strategies (practical)
1) Match message to source
If traffic is from ads:
- mirror the ad headline in the hero
- use the same promise and visual tone
2) Make the next step obvious
- one primary CTA
- avoid multiple competing CTAs above the fold
3) Write benefit-first
- Features: what it does
- Benefits: what that means for them
4) Use specificity
- ❌ “Save time and streamline”
- ✅ “Cut your weekly reporting from 4 hours to 15 minutes”
5) Reduce risk
Pick at least one:
- free trial
- free plan
- no credit card
- cancel anytime
- money-back guarantee
6) Objection handling is a section, not a footer
- add FAQ earlier if it’s a high-friction offer
- put proof right next to the claim it supports
Copywriting templates
Headline formulas
- “{Outcome} without {pain}”
- “The {category} for {audience}”
- “Ship {result} in {time}”
Subheadline rules
- 1–2 sentences
- clarify what it is + who it’s for
CTA rules
- Verb + what they get
- Avoid weak CTAs: “Learn more”, “Submit”
Examples:
- “Start free trial”
- “Book a demo”
- “Get the checklist”
Benefit bullets
Format:
- Benefit — proof/detail
Example:
- Faster iteration — generate 3 layout variants in one click.
Section-by-section workflow (designer-friendly)
Work in this order:
- Hero
- Benefits
- How it works
- Proof
- FAQ
- Final CTA
Rule: don’t rebuild the whole page each time. Iterate section-by-section to keep control.
SEO + AEO checklist (when relevant)
When landing pages should NOT be indexed
- ad-only campaigns
- highly time-bound offers
Use:
noindex(or keep it behind a non-indexed path)
When they SHOULD be indexed
- evergreen offers
- search intent matches the promise
Add:
- clear title + meta
- internal links from homepage/feature pages
- FAQ in plain Q/A for AEO
Optional:
- FAQ schema (if appropriate)
Common pitfalls
- Too many CTAs above the fold
- Vague value prop (“streamline”, “optimize”)
- Big feature list with no outcomes
- Proof hidden at the bottom
- Mobile layout breaks readability
- No clear next step
Output format (when generating a landing page)
Return:
- Page outline (sections + order)
- Hero copy (headline, subheadline, CTA, proof line)
- Benefits section (3–5 bullets)
- How it works (3 steps)
- FAQ (6–12 Q/A)
- SEO/AEO (indexing recommendation + title/meta if indexed)
- Layout recommendation (A/B/C/D + why)
Quick questions (if user says “make a landing page”)
- What’s the ONE primary CTA?
- Who is the ICP and what’s the main pain?
- Any proof (numbers/testimonials/logos)?
- What’s the offer and risk reversal?
- Where is traffic coming from?
What ships with it: 1 file
288 B alongside SKILL.md
- REFERENCES.md288 B