1---2name: marketing-site3description: "Honest marketing-site method: audience, offer, proof, objections, privacy, art direction, handoff. Triggers: marketing site, landing page, company website, product website, portfolio, campaign page, client website, conversion, positioning, offer, value proposition, CTA, social proof, testimonial, privacy policy."4allowed-tools: Read, Write, Edit, Bash, Grep, Glob5kernel:6 kind: methodology7 version: 18 side_effects: none9 confirmation: none10---1112<skill id="marketing-site">1314<purpose>15Turn a product or service into a focused, credible website. The page should help a specific16person understand the offer, trust it, and take the next useful action—without marketing17theater or a generic template wearing different nouns.18</purpose>1920<skill_load>skills/frontend/SKILL.md</skill_load>2122<inputs>23Recover what the user and repository already supplied before asking questions:24251. Audience: who arrives, what they know, and what situation brought them here.262. Desired action: install, buy, book, join, contact, learn, or compare.273. Offer: what changes for the visitor, how it works, and why this option is different.284. Friction: objections, risks, missing information, switching cost, and alternatives.295. Proof: product behavior, demo, screenshots, founder expertise, customer evidence, data.306. Brand and constraints: voice, assets, references, legal/privacy needs, stack, deadline.3132Do not force an interview when the brief answers these. Ask only for a missing choice that33would materially change the page; otherwise make a reversible assumption and label it.34</inputs>3536<truth-rules>37Never invent customers, testimonials, metrics, guarantees, awards, integrations, press logos,38scarcity, fake urgency, or “trusted by” claims. Placeholder proof must be visibly marked as a39placeholder and cannot ship. Describe capabilities at the strength the evidence supports.40Specific and modest beats impressive and false.41</truth-rules>4243<strategy>44Write a one-sentence positioning statement:45“For [audience in situation], [offer] helps [outcome] by [mechanism/difference].”4647Then choose a page argument that fits the buying decision. A useful default is:48problem or desire → promise → mechanism → proof → objections → action.49It is a diagnostic spine, not a mandatory section order. A familiar plugin may need one sharp50idea and a demo; an expensive service may need process, proof, risk reduction, and detail.5152Give each section one job. Prefer one primary CTA; secondary actions are allowed when they53serve a genuinely different visitor state. CTA copy should name the next step, not “Submit.”54</strategy>5556<copy>57- Lead with the visitor's outcome or tension, then make the mechanism concrete.58- Use the user's language and real nouns. Delete adjectives that the page cannot prove.59- Keep the headline, subhead, visual, and CTA mutually reinforcing.60- Answer the strongest objection near the claim that creates it.61- Let product screenshots, examples, demos, and specifics carry more weight than slogans.62- Match detail to consequence: higher price/risk needs more explanation and reassurance.63</copy>6465<art-direction>66Use `skills/frontend/SKILL.md`. Derive the visual direction from audience, brand, offer,67content, and references. A provocative page earns its tension through the idea; it does not68need random visual aggression. Preserve an existing design system when present.69</art-direction>7071<privacy-and-trust>72The privacy page must describe the actual implementation: what data is collected, why, where73it goes, retention/deletion, cookies or analytics, form/email providers, user choices, contact,74and effective date. If the site collects nothing, say so plainly and still disclose hosting75logs or third parties that may receive technical data. Do not copy a broad boilerplate policy76that claims tools the site does not use. Flag jurisdiction-specific legal review when stakes77require it; do not present generated copy as legal advice.78</privacy-and-trust>7980<client-delivery>81For client work, confirm who approves copy/design, who owns supplied assets, the domain and82accounts, analytics/consent choices, editable-source handoff, launch/rollback plan, and who83maintains the site. Keep credentials in the client's account or secure environment—not source.84Read `skills/marketing-site/references/client-delivery.md` for the compact handoff checklist.85</client-delivery>8687<verification>88Check the rendered page at target widths and follow every conversion path. Verify all claims89against supplied evidence, every CTA and legal link, keyboard/focus behavior, performance,90metadata/share preview, form success/error states, and the deployed privacy behavior.91</verification>9293<output>94State the audience, desired action, positioning, page argument, proof used, art direction,95assumptions/placeholders, privacy reality, and what was actually verified.96</output>9798</skill>
hashgraph-online