landing-page

Landing page

Produce a coherent marketing page for one audience and one primary decision. Own the page-level argument: what the visitor must understand, believe, and do. Preserve the product's existing brand and implementation system unless evidence supports changing them.

Keep the boundary clear

This skill coordinates a landing-page outcome without replacing specialist work:

• Use the landing-copy skill when the core problem is positioning, claims, proof, objections, or CTA language.
• Use the interface-design skill when the core problem is a broader design system, application workflow, or component implementation.
• Use the mobile-first skill for a measured responsive audit or repair after the page structure is sound.
• Use performance-diagnosis, social-sharing, or remove-ai-slop when those are the actual requested outcomes.

When a specialist skill is unavailable, handle the necessary portion here, but do not pretend to have verified evidence you could not inspect.

Choose the working mode

Infer the narrowest mode from the request and existing project:

• Build — create and implement a new page or substantial section.
• Repair — change an existing page whose message, structure, proof, or conversion path is underperforming.
• Audit — return evidence-backed findings without changing files.
• Handoff — produce an implementation brief or sequenced prompts because another person or agent will execute the work.

State the selected mode and scope in one sentence. Do not offer the modes as a menu.

Recover evidence before asking

Inspect the supplied brief, repository, live page, analytics, search data, customer language, product states, existing brand tokens, and reference sites that are in scope. Separate observed facts from assumptions.

Resolve these decisions from evidence when possible:

• the visitor, their entry context, and the job they are trying to complete;
• the single primary action and any legitimate secondary path;
• the differentiated claim and the proof available to support it;
• implementation constraints, visual system, and required states;
• how success will be measured after release.