| schemaVersion | 2026-04-11T00:00:00.000Z |
| skillId | frontend/marketing-landing-page |
| name | marketing-landing-page |
| displayName | Marketing Landing Page |
| description | Use when the task is to design a campaign page, 营销落地页, launch page, feature promotion page, webinar signup page, or lead generation page. Focus on one conversion goal, persuasive sequencing, proof, CTA rhythm, and low-friction form design. |
| aliases | ["marketing-landing-page","Marketing Landing Page","marketinglandingpage","营销落地页","转化页","预约 demo","获客页","营销","落地页","campaign page","marketing","landing","预约 demo 页面","lead generation page"] |
| version | 0.1.0 |
| sourceHash | sha256:717fae828ee3b313a73569cc331ee88c0f7479b9e44e0a06652593d6ef19df50 |
| domain | frontend |
| departmentTags | ["frontend-platform"] |
| sceneTags | ["design"] |
Marketing Landing Page
Use this skill when the page exists to convert a specific campaign intent: signup, download, demo request, waitlist, registration, or lead capture.
Goal: keep the page single-minded. Every section should remove one objection or strengthen one reason to convert.
Conversion model
Before building, define:
- one audience
- one offer
- one primary CTA
- one strongest proof source
If the page has multiple goals, split the page or downgrade secondary actions.
Default sequence
- Hero: promise, audience fit, CTA, proof teaser
- Why now: pain, change, or opportunity
- Offer detail: what the visitor gets and how it works
- Proof: results, logos, testimonials, or product evidence
- Friction removal: FAQ, pricing cue, timeline, or requirements
- Final CTA: repeat the action with reduced hesitation
Hero rules
- State the benefit fast.
- Keep the CTA visible without scrolling.
- Show one dominant visual or one product demonstration, not both competing equally.
- Use supporting proof near the CTA if trust is the main blocker.
- Minimize top navigation unless the campaign requires exploration.
CTA rules
- Use one label consistently across the page.
- Repeat the CTA after each major proof or explanation block.
- Match the CTA to effort: "Book demo" and "Start free" are not interchangeable.
- If a form is above the fold, keep it short and explain what happens next.
Content rules
- Write to a specific problem, not to "everyone".
- Replace abstract claims with concrete outcomes.
- Use sections to handle objections one at a time.
- Put technical detail below value and proof unless the audience is highly technical.
Reject these failures
- Website-style nav with too many exits
- Multiple competing CTAs
- Long feature grids with no proof
- Testimonial quotes with no role, company, or context
- Forms that ask for more than the offer justifies
Final checks
- Can the visitor understand the offer in under five seconds?
- Is the primary CTA obvious in every major section?
- Does each section either explain, prove, or reduce friction?
