Landing structure
Skill Dragoon0x/product-skills/skills/conversion/landing-structure
Information architecture that guides visitors from curiosity to commitment. Enforces section order, content hierarchy, and scroll-depth logic. Use when building landing pages, product pages, or any conversion surface.From its SKILL.md
npx -y skills add Dragoon0x/product-skills --skill landing-structureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 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.
SKILL.md
1.7 KB, 343 tokens by cl100k_base, as published. Nobody here has run it
Landing Structure
Information architecture that guides visitors from curiosity to commitment.
How to use
/landing-structureApply these constraints to landing page work in this conversation.
Constraints
Section Order (high-intent traffic)
- Hero: Problem + solution in one screen. CTA visible without scrolling.
- Social proof: logos, numbers, or one strong testimonial.
- How it works: 3 steps max. Show, don't tell.
- Features/benefits: lead with outcomes, support with features.
- Deeper social proof: case studies, detailed testimonials.
- Pricing or next step.
- FAQ: handle remaining objections.
- Final CTA: repeat the primary action.
Section Order (low-intent traffic)
- Hero: Lead with the problem. Make them feel understood.
- Problem amplification: show the cost of the status quo.
- Solution introduction.
- How it works: simple, visual, concrete.
- Social proof: trust before asking for commitment.
- Low-commitment CTA: free trial, demo, newsletter.
Rules
- MUST have exactly one primary CTA per page (repeated, not different)
- MUST make the hero scannable in under 5 seconds
- MUST answer "what is this, who is it for, why should I care" before first scroll
- Hero headline: 6-12 words. Subheadline: 15-25 words
- NEVER start with "Welcome to..." or the company name
- NEVER bury CTA below 3+ scrolls
- NEVER have two consecutive text-heavy sections without visual break
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.