Agent Skills
› NeverSight/learn-skills.dev
› landing-page-composition
landing-page-composition
GitHub用于规划或重构营销网站页面结构，遵循叙事逻辑链。适用于首页、服务页等，指导章节排序、证明放置及CTA节奏，确保内容聚焦购买决策并优化阅读体验。
Trigger Scenarios
规划或重组主页、服务页、关于我们或活动页的结构
调整叙事流、章节顺序、信任背书位置或CTA节奏
进行页面级组合决策以优化购买路径
Install
npx skills add NeverSight/learn-skills.dev --skill landing-page-composition -g -y
SKILL.md
Frontmatter
{
"name": "landing-page-composition",
"description": "Use when planning or restructuring homepage, service page, about page, campaign page, or section order for this marketing website. Trigger for narrative flow changes, section sequencing, proof placement, CTA pacing, and page-level composition decisions."
}
Landing Page Composition
Build the buying narrative before building sections.
Narrative Order
Move the reader through this chain:
- What is this?
- Why should I care now?
- Why should I trust you?
- What exactly do you do?
- What happens next?
If a section does not help answer one of those questions, it is probably clutter.
Default Flow
For most marketing pages in this repo:
- Hero with value proposition and direct CTA
- Relevance or proof block that validates the buyer quickly
- Core services, offers, or use-case paths
- Process, methodology, or decision framework
- Supporting proof, industry relevance, case material, or metrics
- Objection-handling content such as FAQ, scope guidance, or fit criteria
- Final CTA
Service Page Rules
For the main services page:
- Lead with what AUXO does and how the library is organized.
- Help buyers self-select by problem or operating stage.
- Show the service catalog with short, differentiated summaries.
- Add industries, engagement models, or other relevance layers only if they sharpen fit.
- End with one clear recommendation CTA.
For individual service pages:
- Hero: service name, buyer problem, concrete outcome, direct CTA.
- Best-fit block: who it is for, primary stakeholders, primary output, trigger conditions.
- Overview: why the problem matters and what gets fixed.
- Deliverables or benefits: tangible artifacts, not slogan cards.
- Process: what happens, in what order, with what outputs.
- Outcomes and FAQ: expected change plus objection handling.
- Final CTA.
Rules
- Put proof earlier than most marketing teams are comfortable with.
- Keep each section responsible for one job.
- Alternate dense and light sections so the page has pacing.
- Repeat CTA intent without repeating the same copy mechanically.
- Avoid stacking three abstract sections in a row.
- Use industries, personas, or use cases only when they sharpen buyer self-selection.
- Long pages need progressive CTA pacing: early primary access, mid-page assistive guidance, final close.
- Prefer specific labels such as
Primary outputorBest whenover generic labels when the page is helping buyers choose. - If a section can be cut without harming the buying decision, cut it.
Version History
- e0220ca Current 2026-07-05 23:25
