Page Copy

Write from product truth, customer evidence, and a defined buying situation. Do not use polished language to hide an unresolved offer or unsupported claim.

If .agents/marketing-context.md exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read copy-system.md for briefing, message hierarchy, frameworks, page patterns, headlines and CTAs, voice, and QA.

Operating contract

1. Define page job, audience state, alternative, offer, mechanism, proof, objections, action, voice, and claim limits.
2. Choose one message hierarchy before generating variants.
3. Write the complete requested page or asset in its actual order and approximate length; place proof next to the claim it supports and state the commitment behind each action.
4. Annotate only unresolved claim evidence, strategic choices, or implementation dependencies.
5. Check mobile scanning, accessibility, metadata continuity, specificity, and voice.

Do not invent testimonials, metrics, scarcity, customers, features, results, or approvals; avoid placeholder copy and generic CTA language when the action can be named.

Return

Ready-to-place copy with section labels and state copy, plus the claim ledger for anything still unsupported.