name: marketing-site
description: "Honest marketing-site method: audience, offer, proof, objections, privacy, art direction, handoff. Triggers: marketing site, landing page, company website, portfolio, campaign page, conversion, positioning, value proposition, CTA, social proof, privacy policy."
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
kernel:
kind: methodology
version: 1
side_effects: none
confirmation: none
<skill_load>skills/frontend/SKILL.md</skill_load>
- Audience: who arrives, what they know, and what situation brought them here.
- Desired action: install, buy, book, join, contact, learn, or compare.
- Offer: what changes for the visitor, how it works, and why this option is different.
- Friction: objections, risks, missing information, switching cost, and alternatives.
- Proof: product behavior, demo, screenshots, founder expertise, customer evidence, data.
- Brand and constraints: voice, assets, references, legal/privacy needs, stack, deadline.
Do not force an interview when the brief answers these. Ask only for a missing choice that
would materially change the page; otherwise make a reversible assumption and label it.
Then choose a page argument that fits the buying decision. A useful default is:
problem or desire → promise → mechanism → proof → objections → action.
It is a diagnostic spine, not a mandatory section order. A familiar plugin may need one sharp
idea and a demo; an expensive service may need process, proof, risk reduction, and detail.
Give each section one job. Prefer one primary CTA; secondary actions are allowed when they
serve a genuinely different visitor state. CTA copy should name the next step, not “Submit.”