{
    "slug": "copywriting",
    "name": "copywriting",
    "description": "When the user wants to write, rewrite, or improve marketing copy for any page, including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says \"write copy for,\" \"improve this copy,\" \"rewrite this page,\" \"marketing copy,\" \"headline help,\" \"CTA copy,\" \"value proposition,\" \"tagline,\" \"subheadline,\" \"hero section copy,\" \"above the fold,\" \"this copy is weak,\" \"make this more compelling,\" \"this sounds like AI,\" \"AI slop,\" \"make it sound human,\" or \"help me describe my product.\" Use this whenever someone is working on website text that needs to persuade or convert. Drafts never use AI tells like \"it's not X, it's Y\" reveals, \"no X, no Y, no Z\" lists, or sentences that trail into extra comma clauses. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.",
    "frontmatter": {
        "name": "copywriting",
        "description": "When the user wants to write, rewrite, or improve marketing copy for any page, including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says \"write copy for,\" \"improve this copy,\" \"rewrite this page,\" \"marketing copy,\" \"headline help,\" \"CTA copy,\" \"value proposition,\" \"tagline,\" \"subheadline,\" \"hero section copy,\" \"above the fold,\" \"this copy is weak,\" \"make this more compelling,\" \"this sounds like AI,\" \"AI slop,\" \"make it sound human,\" or \"help me describe my product.\" Use this whenever someone is working on website text that needs to persuade or convert. Drafts never use AI tells like \"it's not X, it's Y\" reveals, \"no X, no Y, no Z\" lists, or sentences that trail into extra comma clauses. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.",
        "metadata": "",
        "version": "2.1.0"
    },
    "body": "# Copywriting\n\nYou are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.\n\n## Before Writing\n\n**Check for product marketing context first:**\nIf `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nGather this context (ask if not provided):\n\n### 1. Page Purpose\n- What type of page? (homepage, landing page, pricing, feature, about)\n- What is the ONE primary action you want visitors to take?\n\n### 2. Audience\n- Who is the ideal customer?\n- What problem are they trying to solve?\n- What objections or hesitations do they have?\n- What language do they use to describe their problem?\n\n### 3. Product/Offer\n- What are you selling or offering?\n- What makes it different from alternatives?\n- What's the key transformation or outcome?\n- Any proof points (numbers, testimonials, case studies)?\n\n### 4. Context\n- Where is traffic coming from? (ads, organic, email)\n- What do visitors already know before arriving?\n\n---\n\n## Copywriting Principles\n\n### Clarity Over Cleverness\nIf you have to choose between clear and creative, choose clear. Clarity also converts. Clearer positioning and copy is associated with +81% conversions, a 38% shorter sales cycle, 28% lower CAC, and 175% more referrals. When a reader has to decode your line, you've lost them.\n\n**For message-market fit tools** (the \"Now you can\" test, the Human Action Model (discomfort → vision → path), the Perception Gap, and the clarity metrics): See [references/copy-frameworks.md](references/copy-frameworks.md#clarity--message-market-fit)\n\n### Benefits Over Features\nFeatures: What it does. Benefits: What that means for the customer.\n\n### Specificity Over Vagueness\n- Vague: \"Save time on your workflow\"\n- Specific: \"Cut your weekly reporting from 4 hours to 15 minutes\"\n\n### Customer Language Over Company Language\nUse words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets.\n\n### One Idea Per Section\nEach section should advance one argument. Build a logical flow down the page.\n\n---\n\n## Writing Style Rules\n\n### Core Principles\n\n1. **Simple over complex**: \"Use\" not \"utilize,\" \"help\" not \"facilitate\"\n2. **Specific over vague**: Avoid \"streamline,\" \"optimize,\" \"innovative\"\n3. **Active over passive**: \"We generate reports\" not \"Reports are generated\"\n4. **Confident over qualified**: Remove \"almost,\" \"very,\" \"really\"\n5. **Show over tell**: Describe the outcome instead of using adverbs\n6. **Honest over sensational**: Fabricated statistics or testimonials erode trust and create legal liability\n\n### Quick Quality Check\n\n- Any AI tells? (see No AI Tells below)\n- Jargon that could confuse outsiders?\n- Sentences trying to do too much?\n- Passive voice constructions?\n- Exclamation points? (remove them)\n- Marketing buzzwords without substance?\n\nFor thorough line-by-line review, use the **copy-editing** skill after your draft.\n\n---\n\n## No AI Tells\n\nClients and buyers reject copy that reads as AI-written, and a reader who spots a tell tends to doubt the claims around it. Write like a senior copywriter: specific, uneven in rhythm, and built from facts rather than formulas.\n\n### Never write these\n\n1. **Contrast reveals.** \"It's not X, it's Y.\" \"Not because X. Because Y.\" \"Not just X, but Y.\" State Y directly, with the reason.\n2. **Negation lists.** \"No setup call, no templates, no waiting on IT. No contract.\" Say what does happen. State a real absence once, near the CTA (\"No card required\"), and turn the others into what happens.\n3. **Trailing pile-ons.** A full claim followed by a comma and more clauses: \"...the data you already have, no exports, no spreadsheets, no second copy.\" End the sentence at the claim.\n4. **Self-answered questions and colon reveals.** \"The result? 3x faster.\" \"The best part: it learns.\" Just say it. FAQ questions and a reader's own question (\"Need to share a screenshot?\") are fine.\n5. **Stock openers and phrases.** \"In today's fast-paced world,\" \"Whether you're X or Y,\" \"Here's the thing,\" \"Say goodbye to,\" \"X, reimagined,\" \"Unlock the power of,\" \"Take it to the next level.\"\n6. **Em dashes in short copy.** Headlines, subheads, ads, social posts, and subject lines use none.\n\n### Keep these rare\n\n- At most one fragment and one list of three per section (a hero, a page section, or one short post). CTA microcopy and a real three-feature list are fine.\n- Words like seamless, robust, powerful, unlock, and streamline: replace them with the fact they stand in for.\n- Swap test: if a line would work unchanged on a competitor's site, rewrite it. If you lack the differentiator to fix it, flag `[NEED: differentiator]`.\n\n### Check before delivering\n\nBefore handing over any draft, run the self-check in [references/ai-tells.md](references/ai-tells.md#the-self-check): search for the banned patterns, read every sentence over 20 words, and read it aloud. Fix from the facts, since swapping synonyms creates new tells, and flag missing proof as `[NEED: ...]` rather than inventing it.\n\n**For the full blacklist with examples and rewrites**: See [references/ai-tells.md](references/ai-tells.md)\n\n---\n\n## Best Practices\n\n### Be Direct\nGet to the point. Don't bury the value in qualifications.\n\n❌ Slack lets you share files instantly, from documents to images, directly in your conversations\n\n✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires.\n\n### Use Rhetorical Questions\nA question that names the reader's pain can open a section well.\n- \"Hate returning stuff to Amazon?\"\n- \"Tired of chasing approvals?\"\n\nA question in the reader's voice followed by what to do is fine (see Be Direct). A question that labels your own claim (\"The result? 3x faster.\") is an AI tell.\n\n### Use Analogies When Helpful\nAnalogies make abstract concepts concrete and memorable.\n\n### Pepper in Humor (When Appropriate)\nPuns and wit make copy memorable when they fit the brand and don't cost clarity.\n\n---\n\n## Page Structure Framework\n\n### Above the Fold\n\n**Headline**\n- Your single most important message\n- Communicate core value proposition\n- Specific > generic\n\n**Example formulas:**\n- \"{Achieve outcome} without {pain point}\"\n- \"The {category} for {audience}\"\n- \"Never {unpleasant event} again\"\n- \"{Question highlighting main pain point}\"\n\n**For comprehensive headline formulas**: See [references/copy-frameworks.md](references/copy-frameworks.md)\n\n**Structure the hero as a transformation**: current discomfort → better vision → path to action (the Human Action Model), then run every headline through the \"Now you can\" test. See [references/copy-frameworks.md](references/copy-frameworks.md#clarity--message-market-fit)\n\n**For natural transition phrases**: See [references/natural-transitions.md](references/natural-transitions.md)\n\n**Subheadline**\n- Expands on headline\n- Adds specificity\n- 1-2 sentences max\n\n**Primary CTA**\n- Action-oriented button text\n- Communicate what they get: \"Start Free Trial\" > \"Sign Up\"\n\n### Core Sections\n\n| Section | Purpose |\n|---------|---------|\n| Social Proof | Build credibility (logos, stats, testimonials) |\n| Problem/Pain | Show you understand their situation |\n| Solution/Benefits | Connect to outcomes (3-5 key benefits) |\n| How It Works | Reduce perceived complexity (3-4 steps) |\n| Objection Handling | FAQ, comparisons, guarantees |\n| Final CTA | Recap value, repeat CTA, risk reversal |\n\n**For detailed section types and page templates**: See [references/copy-frameworks.md](references/copy-frameworks.md)\n\n---\n\n## CTA Copy Guidelines\n\n**Weak CTAs (avoid):**\n- Submit, Sign Up, Learn More, Click Here, Get Started\n\n**Strong CTAs (use):**\n- Start Free Trial\n- Get [Specific Thing]\n- See [Product] in Action\n- Create Your First [Thing]\n- Download the Guide\n\n**Formula:** [Action Verb] + [What They Get] + [Qualifier if needed]\n\nExamples:\n- \"Start My Free Trial\"\n- \"Get the Complete Checklist\"\n- \"See Pricing for My Team\"\n\n---\n\n## Page-Specific Guidance\n\n### Homepage\n- Serve multiple audiences without being generic\n- Lead with broadest value proposition\n- Provide clear paths for different visitor intents\n\n### Landing Page\n- Single message, single CTA\n- Match headline to ad/traffic source\n- Complete argument on one page\n\n### Pricing Page\n- Help visitors choose the right plan\n- Address \"which is right for me?\" anxiety\n- Make recommended plan obvious\n\n### Feature Page\n- Connect feature → benefit → outcome\n- Show use cases and examples\n- Clear path to try or buy\n\n### About Page\n- Tell the story of why you exist\n- Connect mission to customer benefit\n- Still include a CTA\n\n---\n\n## Voice and Tone\n\nBefore writing, establish:\n\n**Formality level:**\n- Casual/conversational\n- Professional but friendly\n- Formal/enterprise\n\n**Brand personality:**\n- Playful or serious?\n- Bold or understated?\n- Technical or accessible?\n\nMaintain consistency, but adjust intensity:\n- Headlines can be bolder\n- Body copy should be clearer\n- CTAs should be action-oriented\n\n---\n\n## Output Format\n\nWhen writing copy, provide:\n\n### Page Copy\nOrganized by section:\n- Headline, Subheadline, CTA\n- Section headers and body copy\n- Secondary CTAs\n\n### Annotations\nFor key elements, explain:\n- Why you made this choice\n- What principle it applies\n\n### Alternatives\nFor headlines and CTAs, provide 2-3 options:\n- Option A: [copy]. Rationale: [why]\n- Option B: [copy]. Rationale: [why]\n\n### Meta Content (if relevant)\n- Page title (for SEO)\n- Meta description\n\n---\n\n## Related Skills\n\n- **copy-editing**: For polishing existing copy (use after your draft)\n- **cro**: If page structure/strategy needs work, not just copy\n- **emails**: For email copywriting\n- **popups**: For popup and modal copy\n- **ab-testing**: To test copy variations\n",
    "references": {
        "ai-tells.md": {
            "name": "Ai Tells",
            "path": "ai-tells.md",
            "content": "# AI Tells: The Copy Blacklist\n\nPatterns that make marketing copy read as machine-written. Clients and buyers spot these fast, and a reader who decides a page was generated starts doubting its claims too.\n\nMost of these are old human rhetoric. AI copy gives itself away by using them **by default**, **stacked**, and **with nothing specific behind them**. So the rules below are a mix of hard bans (for patterns that are tells even once) and frequency caps (for devices that are fine when chosen on purpose).\n\n**Confidence key**\n- **Ban**: a tell even once. Don't write it.\n- **Cap**: fine once, a tell when repeated or stacked. Stay under the cap.\n\n**What the scopes mean**\n- **Short copy**: headlines, subheads, the hero, CTAs, ads, social posts, email subject lines.\n- **Long copy**: body sections of a page, articles, long emails.\n- **Section**: one hero, one page section, or one whole short post.\n- CTA microcopy (\"No card required\") doesn't count toward the fragment cap.\n\n**Still fine:** FAQ questions, a single \"No card required,\" a list of three when there really are three features, a single \"without\" headline, and a formal brand voice that makes specific claims.\n\n---\n\n## Contents\n- Structural Patterns (the worst offenders)\n- Openers, Closers, and Setups\n- Marketing Phrases\n- Vocabulary\n- Hedges, Puffery, and Weasels\n- Tone\n- Formatting\n- Rewrite Rules\n- The Self-Check\n- Sources\n\n---\n\n## Structural Patterns\n\nThese matter more than any word list. A draft can avoid every banned word and still read as AI because of its shape.\n\n### 1. The contrast reveal: \"Not X. Y.\" (Ban)\n\nSets up an assumption nobody stated, denies it, then gives the \"real\" answer.\n\nVariants: \"It's not X, it's Y.\" \"Not because X. Because Y.\" \"This isn't X. This is Y.\" \"Not just X, but Y.\" \"Less X, more Y.\" \"The question isn't X, it's Y.\" \"X? Think again.\"\n\n- ✗ Most marketing teams have a list of campaign ideas that never launch. Not because they're bad. Because each one needs a developer.\n- ✓ Most marketing teams have a list of campaign ideas that never launch, because each one needs a developer they can't get.\n\n**Why it's a tell:** It's one of the most frequently cited AI patterns. Wikipedia's AI-cleanup guide calls it \"negative parallelism,\" and EQ-Bench's Slop Score gives \"not X, but Y\" patterns their own weighted category.\n\n**Rewrite:** State Y directly and attach the concrete reason or cost. If the reader holds a wrong belief you need to correct, state the correct fact and the evidence; don't stage the denial.\n\n### 2. The negation list: \"No X, no Y, no Z.\" (Ban)\n\nDefines the product by what's absent, usually in threes, often with a fragment tacked on.\n\nVariants: \"No X. No Y. Just Z.\" \"Without X, without Y.\" \"Zero X, zero Y.\"\n\n- ✗ No setup call, no templates to fill in, no waiting on IT. No contract.\n- ✓ Install it from the app store and it's running on your data in five minutes.\n\n**Rewrite:** Say what does happen, in the order it happens. If an absence really is a selling point (no card required, no install), state it once, plainly, next to the CTA: \"Free to start. No card required.\" A brief with several absences doesn't need a list: turn the rest into what happens (\"no signup form\" becomes \"Log in with your Shopify account\").\n\nA single \"without\" or \"Never X again\" headline is fine. Don't follow it with a negation list in the subhead.\n\n### 3. The trailing pile-on (Ban)\n\nA complete claim, then a comma, then a run of add-ons: a negation list, an \"-ing\" clause, or a string of extra benefits.\n\n- ✗ Reports pull directly from the data you already have, no exports, no spreadsheets, no second copy to keep updated.\n- ✗ It syncs your calendar automatically, ensuring nothing slips through the cracks.\n- ✓ Reports pull from the data you already have. There's nothing to export.\n\n**Rewrite:** End the sentence when the main claim ends. If the benefit matters, give it its own short sentence with one concrete detail. Test: after the main clause is complete, cut anything past the next comma that doesn't add a new fact. A clause that adds one (\"Imports run nightly, keeping your existing IDs\") can stay; a string of restatements can't.\n\n### 4. Rhetorical question, then answer (Ban)\n\n\"The result? 3x faster onboarding.\" \"The catch? There isn't one.\" \"Why does this matter? Because...\"\n\n- ✗ The result? Onboarding that takes minutes, not weeks.\n- ✓ New hires finish onboarding on day one.\n\n**Rewrite:** Delete the question and keep the answer.\n\nStill fine: FAQ questions (\"Does it work with Shopify?\"), and a question in the reader's voice about their own need, followed by what to do (\"Need to share a screenshot? Drop it in the thread.\"). The tell is a question that labels your own claim (\"The result?\" \"The catch?\" \"Why does this matter?\").\n\n### 5. The colon reveal (Ban)\n\n\"The best part: it learns.\" \"Here's the secret: consistency.\" \"One word: speed.\"\n\n**Rewrite:** Write it as a normal sentence (\"It learns from every correction\"). Save colons for lists, labels, and quotes.\n\n### 6. Fragment drumbeat (Cap: one per section)\n\nStacked fragments or one-line paragraphs for manufactured punch. \"Simple. Fast. Done.\" \"That's it. That's the whole thing.\"\n\n**Rewrite:** Merge them into one full sentence that carries a fact. One fragment that lands a real payoff is a copywriting device. A paragraph of them is a tic.\n\n### 7. Reflexive threes (Cap: one per section)\n\nEverything comes in threes: adjectives, benefits, clauses, bullets. \"Fast, secure, and scalable.\" \"Save time, cut costs, and grow revenue.\"\n\n**Rewrite:** Use as many items as the facts support: one, two, or four. Usually the fix is the single strongest concrete claim: \"Fast, secure, and scalable\" → \"Handles 40,000 webhooks a second on the free plan.\"\n\n### 8. Em dashes (Ban in short copy; cap at 1–2 per page in long copy)\n\nThe dash as the default pause, several per paragraph, often carrying a contrast reveal (\"It's not a tool — it's a teammate\").\n\n**Rewrite:** Use a period, a comma, a colon, or parentheses. In heroes, ads, subject lines, and social posts, use none.\n\n### 9. Uniform rhythm (Cap)\n\nEvery sentence 12–18 words. Every paragraph is topic sentence → elaboration → wrap-up. Every section the same length. Three pros, three cons, every time.\n\n**Rewrite:** Vary on purpose. A long sentence, then a short one. Let a section be two lines if that's all it needs. Put the payoff first sometimes.\n\n### 10. Dodging \"is\" and \"has\" (Cap)\n\n\"Serves as a central hub.\" \"Stands as a testament.\" \"Boasts a library of 200 templates.\" \"Represents a new approach.\"\n\n**Rewrite:** Use \"is\" and \"has\", or better, the actual verb: \"Tracks every contract, renewal date, and owner in one place.\"\n\n### 11. Abstract subjects (Cap)\n\n\"The platform empowers teams to...\" \"Our solution enables...\" Nobody does anything.\n\n**Rewrite:** Make the customer the subject. \"Your team ships experiments without filing a ticket.\"\n\n### 12. False ranges (Cap)\n\n\"From startups to enterprises.\" \"From onboarding to renewal.\" The two ends don't describe a real span.\n\n**Rewrite:** Name the segment you actually serve, or the steps you actually cover.\n\n### 13. Synonym cycling (Cap)\n\nCalling the same thing a dashboard, an interface, a portal, and a hub in one page to avoid repeating a word.\n\n**Rewrite:** Pick the word your customer uses and repeat it.\n\n---\n\n## Openers, Closers, and Setups (Ban)\n\n| Pattern | Example | Instead |\n|---------|---------|---------|\n| Era opener | \"In today's fast-paced world...\" | Open with the customer's problem |\n| False-choice opener | \"Whether you're a solo founder or a Fortune 500...\" | Name who the page is for |\n| \"Imagine...\" | \"Imagine never chasing an invoice again.\" | Show the actual before and after |\n| \"When it comes to...\" | \"When it comes to billing, ...\" | Start with the subject |\n| Throat-clearing | \"Here's the thing:\" \"The truth is\" \"Let me be clear\" \"Here's what nobody tells you\" | Cut it. If the claim can't stand alone, it needs evidence, not a drumroll |\n| Announcing | \"In this guide, we'll explore...\" \"Let's dive in\" | Start with the content |\n| Recap ending | \"In conclusion\" \"Ultimately\" \"At the end of the day\" | End on the last concrete point or the CTA |\n| Fake-profound kicker | \"Because growth shouldn't wait.\" \"And that changes everything.\" | Cut it. End on a concrete sentence |\n| Filler transitions | \"It's worth noting\" \"Moreover\" \"Additionally\" \"Importantly\" | Delete. The sentence usually works without it |\n\n---\n\n## Marketing Phrases (Ban)\n\n| Phrase | Instead |\n|--------|---------|\n| \"Say goodbye to X\" / \"Say hello to Y\" | Show the new workflow: \"Reconciliation runs nightly. You review the exceptions.\" |\n| \"Unlock / unleash the power of X\" | Name the outcome and the number |\n| \"X, reimagined\" / \"X, redefined\" | Say what's actually different: \"Billing that retries on payday\" |\n| \"Take X to the next level\" | Name the level: the metric and the target |\n| \"Transform the way you work\" | A before and after with numbers |\n| \"The X you deserve\" | The specific gap you close |\n| \"The future of X is here\" | What ships today |\n| \"Built for teams who move fast\" | The real customer and trigger: \"For subscription teams past $1M ARR fighting failed payments\" |\n| \"Everything you need to X\" / \"all-in-one\" | The 2–3 things buyers actually check for |\n| \"Effortless\" / \"in just a few clicks\" | The real step count or time: \"3 steps, about 4 minutes\" |\n| \"Join thousands of happy customers\" | The real count, logos, or a named quote |\n| \"Game-changer\" / \"this changes everything\" | What changes, for whom, by how much |\n\n---\n\n## Vocabulary\n\nSwapping a banned word for a synonym just creates a new tell. Replace the word with the fact it was standing in for: \"robust\" → \"99.99% uptime over two years\"; \"seamless\" → \"imports your Stripe data in about 90 seconds.\"\n\n**Ban:** delve, tapestry, testament to, realm, embark, beacon, multifaceted, paradigm, synergy, myriad, plethora, meticulous, intricate, utilize, leverage (as a verb), supercharge, turbocharge, game-changer, \"ever-evolving landscape,\" \"plays a crucial role\"\n\n**Cap (two in a paragraph means rewrite it):** seamless, robust, streamline, empower, elevate, unlock, unleash, harness, foster, enhance, optimize, cutting-edge, innovative, revolutionary, transformative, holistic, comprehensive, pivotal, crucial, vital, powerful, next-level, world-class, best-in-class, landscape, navigate, ecosystem, journey (unless literal)\n\n**Cap (empty intensifiers):** truly, genuinely, incredibly, deeply, fundamentally, significantly, simply, actually, literally, quietly\n\nFavored words drift as models change (\"delve\" peaked in 2024; \"enhance,\" \"showcase,\" \"foster,\" and \"align with\" rose after). Treat the lists as current examples, and lean on the structural patterns and the tests below, which don't go stale.\n\n---\n\n## Hedges, Puffery, and Weasels\n\n- **Hedge stacks** (Cap): \"can help you potentially reduce...\" State what you know, or scope the claim honestly.\n- **Importance puffery** (Ban): \"marks a pivotal moment,\" \"redefines the category.\" State the fact; let the reader judge.\n- **Weasel sources** (Ban): \"experts agree,\" \"studies show,\" \"trusted by industry leaders.\" Name the source or the customer, or cut it.\n- **Invented labels** (Cap): \"the integration tax,\" \"the growth trap.\" Only coin a term you'll define and use across the site.\n\n---\n\n## Tone\n\n- **Chummy openers** (Ban in email and social): \"Great question!\" \"Let's be honest...\" \"We get it.\"\n- **Fake vulnerability** (Ban): \"I'll be honest, I was skeptical too...\" with no real story behind it.\n- **Over-explaining** (Cap): \"Let's break this down,\" \"Think of it as...\" Give the explanation directly.\n- **Hype punctuation** (Ban): \"Ready to level up?!\" Exclamation points and interrobangs in body copy.\n\n---\n\n## Formatting\n\n- **Emoji as structure** (Ban in B2B): 🚀 ✨ ✅ leading bullets or headings.\n- **Bold label on every bullet** (Cap): \"**Seamless integration:** ...\" Keep it for reference tables, not every list.\n- **Parallel bullet openers** (Cap): every bullet starting \"Ensures... / Provides... / Enables...\" Start bullets with the customer outcome and vary the grammar.\n- **Title Case Everywhere** (Cap): use sentence case unless the brand style guide says otherwise.\n- **Unicode decoration** (Ban): arrows, ×, 𝗯𝗼𝗹𝗱 letters in body copy.\n- **Label headings** (Cap): \"What / Why / How\" sections. Write headings that make a claim.\n\n---\n\n## Rewrite Rules\n\n1. **Rewrite from the facts.** Go back to what's true (the mechanism, the number, the customer, the step) and write that. Synonym swaps and \"humanizer\" substitutions produce new tells.\n2. **Specificity test.** Every claim sentence needs a number, a name, a mechanism, or a concrete action.\n3. **Swap test.** If the line would work unchanged on a competitor's site, rewrite it.\n4. **Stacking test.** Two or more Cap patterns in one paragraph means rewrite the whole paragraph.\n5. **Don't invent to de-slop.** Replacing \"industry-leading\" with a made-up stat is worse. Mark it `[NEED: proof]` and ask.\n6. **Choose devices on purpose.** A fragment you picked once, for a reason, is copywriting. The same device on every line is slop.\n7. **Keep the brand's register.** A formal sentence that makes a specific claim is fine. Don't flatten an enterprise voice into clipped startup copy, which is its own tell.\n8. **Vary the fixes.** The ✓ examples show one way out. Don't reuse them as templates. If every reveal becomes \", because...\" and every negation list becomes \"There's nothing to X,\" those are the new tics.\n9. **Flag a missing differentiator.** If no headline can pass the swap test with what you have, write the best one and mark `[NEED: differentiator vs. named competitors]`.\n\n---\n\n## The Self-Check\n\nRun this on every draft before delivering it:\n\n1. **Search for the bans.** Look for \"not \", \"isn't\", \"no \", \"without\", \"?\", \":\" and \"—\" in headlines, subheads, and short copy, and check each hit against patterns 1–5 and 8.\n2. **Read every sentence over 20 words.** If it has more than two commas, check for a trailing pile-on (pattern 3).\n3. **Count the caps.** Fragments, threes, and Cap vocabulary per section.\n4. **Read it aloud.** Mark anywhere you'd sound like a press release or a LinkedIn post.\n5. **Apply the swap test** to the headline, subhead, and every section heading.\n\nIf a fix needs information you don't have (a number, a customer, a mechanism), flag it rather than writing around it.\n\n---\n\n## Sources\n\nPatterns and evidence drawn from, and rewritten in our own words:\n\n- Wikipedia, [Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing) (WikiProject AI Cleanup)\n- Kobak et al., excess vocabulary in 15M+ PubMed abstracts ([arXiv 2406.07016](https://arxiv.org/abs/2406.07016))\n- Juzek & Ward, [Why Does ChatGPT \"Delve\" So Much?](https://aclanthology.org/2025.coling-main.426/) (COLING 2025)\n- Paech et al., Antislop ([arXiv 2510.15061](https://arxiv.org/abs/2510.15061)) and [EQ-Bench Slop Score](https://eqbench.com/slop-score.html)\n- [tropes.fyi](https://tropes.fyi/tropes-md) catalog of AI writing tropes\n- Charlie Guo, [The Field Guide to AI Slop](https://www.ignorance.ai/p/the-field-guide-to-ai-slop)\n- Blake Stockton, [Don't write like AI: negation](https://www.blakestockton.com/p/dont-write-like-ai-1-101-negation)\n- Counter-view: [A case for the defense](https://robotsatemyhomework.substack.com/p/ai-writing-patterns) (devices are fine when chosen, not defaulted)\n\nFor a broader word-level list used in content audits, see the seo-audit skill's `references/ai-writing-detection.md`.\n"
        },
        "copy-frameworks.md": {
            "name": "Copy Frameworks",
            "path": "copy-frameworks.md",
            "content": "# Copy Frameworks Reference\n\nHeadline formulas, page section types, and structural templates.\n\n## Contents\n- Headline Formulas (outcome-focused, problem-focused, audience-focused, differentiation-focused, proof-focused, additional formulas)\n- Landing Page Section Types (core sections, supporting sections)\n- Page Structure Templates (feature-heavy page, varied engaging page, compact landing page, enterprise/B2B landing page, product launch page)\n- Section Writing Tips (problem section, benefits section, how it works section, testimonial selection)\n- Clarity & Message-Market Fit (the \"Now you can\" test, Human Action Model, the Perception Gap, the SavvyCal case, clarity metrics)\n\n## Headline Formulas\n\nThese are starting points. Fill every slot with specifics, and check the result against [ai-tells.md](ai-tells.md): a \"without\" or \"Never X again\" headline is fine once, but don't follow it with a negation list.\n\n### Outcome-Focused\n\n**{Achieve desirable outcome} without {pain point}**\n> Understand how users are really experiencing your site without drowning in numbers\n\n**{Achieve desirable outcome} by {how product makes it possible}**\n> Generate more leads by seeing which companies visit your site\n\n**Turn {input} into {outcome}**\n> Turn your hard-earned sales into repeat customers\n\n**[Achieve outcome] in [timeframe]**\n> Get your tax refund in 10 days\n\n---\n\n### Problem-Focused\n\n**Never {unpleasant event} again**\n> Never miss a sales opportunity again\n\n**{Question highlighting the main pain point}**\n> Hate returning stuff to Amazon?\n\n**Stop [pain]. Start [pleasure].**\n> Stop chasing invoices. Start getting paid on time.\n\n---\n\n### Audience-Focused\n\n**{Key feature/product type} for {target audience}**\n> Advanced analytics for Shopify e-commerce\n\n**{Key feature/product type} for {target audience} to {what it's used for}**\n> An online whiteboard for teams to ideate and brainstorm together\n\n**You don't have to {skills or resources} to {achieve desirable outcome}**\n> With Ahrefs, you don't have to be an SEO pro to rank higher and get more traffic\n\n---\n\n### Differentiation-Focused\n\n**The {opposite of usual process} way to {achieve desirable outcome}**\n> The easiest way to turn your passion into income\n\n**The [category] that [key differentiator]**\n> The CRM that updates itself\n\n---\n\n### Proof-Focused\n\n**[Number] [people] use [product] to [outcome]**\n> 50,000 marketers use Drip to send better emails\n\n**{Key benefit of your product}**\n> Sound clear in online meetings\n\n---\n\n### Additional Formulas\n\n**The simple way to {outcome}**\n> The simple way to track your time\n\n**Finally, {category} that {benefit}**\n> Finally, accounting software that doesn't suck\n\n**{Outcome} without {common pain}**\n> Build your website without writing code\n\n**Get {benefit} from your {thing}**\n> Get more revenue from your existing traffic\n\n**{Action verb} your {thing} like {admirable example}**\n> Market your SaaS like a Fortune 500\n\n**What if you could {desirable outcome}?**\n> What if you could close deals 30% faster?\n\n**The {adjective} {category} built for {audience}**\n> The lightweight CRM built for startups\n\n---\n\n## Landing Page Section Types\n\n### Core Sections\n\n**Hero (Above the Fold)**\n- Headline + subheadline\n- Primary CTA\n- Supporting visual (product screenshot, hero image)\n- Optional: Social proof bar\n\n**Social Proof Bar**\n- Customer logos (recognizable > many)\n- Key metric (\"10,000+ teams\")\n- Star rating with review count\n- Short testimonial snippet\n\n**Problem/Pain Section**\n- Articulate their problem better than they can\n- Create recognition (\"that's exactly my situation\")\n- Hint at cost of not solving it\n\n**Solution/Benefits Section**\n- Bridge from problem to your solution\n- 3-5 key benefits (not 10)\n- Each: headline + explanation + proof if available\n\n**How It Works**\n- 3-4 numbered steps\n- Reduces perceived complexity\n- Each step: action + outcome\n\n**Final CTA Section**\n- Recap value proposition\n- Repeat primary CTA\n- Risk reversal (guarantee, free trial)\n\n---\n\n### Supporting Sections\n\n**Testimonials**\n- Full quotes with names, roles, companies\n- Photos when possible\n- Specific results over vague praise\n- Formats: quote cards, video, tweet embeds\n\n**Case Studies**\n- Problem → Solution → Results\n- Specific metrics and outcomes\n- Customer name and context\n- Can be snippets with \"Read more\" links\n\n**Use Cases**\n- Different ways product is used\n- Helps visitors self-identify\n- \"For marketers who need X\" format\n\n**Personas / \"Built For\" Sections**\n- Explicitly call out target audience\n- \"Perfect for [role]\" blocks\n- Addresses \"Is this for me?\" question\n\n**FAQ Section**\n- Address common objections\n- Good for SEO\n- Reduces support burden\n- 5-10 most common questions\n\n**Comparison Section**\n- vs. competitors (name them or don't)\n- vs. status quo (spreadsheets, manual processes)\n- Tables or side-by-side format\n\n**Integrations / Partners**\n- Logos of tools you connect with\n- \"Works with your stack\" messaging\n- Builds credibility\n\n**Founder Story / Manifesto**\n- Why you built this\n- What you believe\n- Emotional connection\n- Differentiates from faceless competitors\n\n**Demo / Product Tour**\n- Interactive demos\n- Video walkthroughs\n- GIF previews\n- Shows product in action\n\n**Pricing Preview**\n- Teaser even on non-pricing pages\n- Starting price or \"from $X/mo\"\n- Moves decision-makers forward\n\n**Guarantee / Risk Reversal**\n- Money-back guarantee\n- Free trial terms\n- \"Cancel anytime\"\n- Reduces friction\n\n**Stats Section**\n- Key metrics that build credibility\n- \"10,000+ customers\"\n- \"4.9/5 rating\"\n- \"$2M saved for customers\"\n\n---\n\n## Page Structure Templates\n\n### Feature-Heavy Page (Weak)\n\n```\n1. Hero\n2. Feature 1\n3. Feature 2\n4. Feature 3\n5. Feature 4\n6. CTA\n```\n\nThis is a list, not a persuasive narrative.\n\n---\n\n### Varied, Engaging Page (Strong)\n\n```\n1. Hero with clear value prop\n2. Social proof bar (logos or stats)\n3. Problem/pain section\n4. How it works (3 steps)\n5. Key benefits (2-3, not 10)\n6. Testimonial\n7. Use cases or personas\n8. Comparison to alternatives\n9. Case study snippet\n10. FAQ\n11. Final CTA with guarantee\n```\n\nThis tells a story and addresses objections.\n\n---\n\n### Compact Landing Page\n\n```\n1. Hero (headline, subhead, CTA, image)\n2. Social proof bar\n3. 3 key benefits with icons\n4. Testimonial\n5. How it works (3 steps)\n6. Final CTA with guarantee\n```\n\nGood for ad landing pages where brevity matters.\n\n---\n\n### Enterprise/B2B Landing Page\n\n```\n1. Hero (outcome-focused headline)\n2. Logo bar (recognizable companies)\n3. Problem section (business pain)\n4. Solution overview\n5. Use cases by role/department\n6. Security/compliance section\n7. Integration logos\n8. Case study with metrics\n9. ROI/value section\n10. Contact/demo CTA\n```\n\nAddresses enterprise buyer concerns.\n\n---\n\n### Product Launch Page\n\n```\n1. Hero with launch announcement\n2. Video demo or walkthrough\n3. Feature highlights (3-5)\n4. Before/after comparison\n5. Early testimonials\n6. Launch pricing or early access offer\n7. CTA with urgency\n```\n\nGood for ProductHunt, launches, or announcements.\n\n---\n\n## Section Writing Tips\n\n### Problem Section\n\nStart with phrases like:\n- \"You know the feeling...\"\n- \"If you're like most [role]...\"\n- \"Every day, [audience] struggles with...\"\n- \"We've all been there...\"\n\nThen describe:\n- The specific frustration\n- The time/money wasted\n- The impact on their work/life\n\n### Benefits Section\n\nFor each benefit, include:\n- **Headline**: The outcome they get\n- **Body**: How it works (1-2 sentences)\n- **Proof**: Number, testimonial, or example (optional)\n\n### How It Works Section\n\nEach step should be:\n- **Numbered**: Creates sense of progress\n- **Simple verb**: \"Connect,\" \"Set up,\" \"Get\"\n- **Outcome-oriented**: What they get from this step\n\nExample:\n1. Connect your tools (takes 2 minutes)\n2. Set your preferences\n3. Get automated reports every Monday\n\n### Testimonial Selection\n\nBest testimonials include:\n- Specific results (\"increased conversions by 32%\")\n- Before/after context (\"We used to spend hours...\")\n- Role + company for credibility\n- Something quotable and specific\n\nAvoid testimonials that just say:\n- \"Great product!\"\n- \"Love it!\"\n- \"Easy to use!\"\n\n---\n\n## Clarity & Message-Market Fit\n\nHeadline formulas give you the shape of a line. These tools tell you whether the line is actually *working*: whether it's clear, whether it maps to how the reader already thinks, and whether it lands with the right person. Positioning is the prologue to your novel: it sets up everything that follows. Get it clear and the rest of the page writes itself.\n\n### The \"Now you can\" Test\n\nA fast gut-check for any headline or benefit line. Mentally prefix it with **\"Now you can…\"**. If the result is both **compelling** and **true**, the line is doing its job. If it reads as vague, obvious, or a stretch, rewrite it.\n\nThe test works because \"Now you can…\" forces the copy into the reader's world. It has to name a concrete new ability they didn't have before. Feature-speak and buzzwords collapse under it.\n\n| Original line | \"Now you can…\" version | Verdict |\n|---------------|------------------------|---------|\n| \"Powerful analytics platform\" | Now you can… have a powerful analytics platform | Fails. not a new ability, just a description |\n| \"See which companies visit your site\" | Now you can… see which companies visit your site | Works. compelling + true |\n| \"Streamline your workflow\" | Now you can… streamline your workflow | Fails. vague, unfalsifiable |\n| \"Send unlimited docs, images, and audio in one place\" | Now you can… send unlimited docs, images, and audio in one place | Works. concrete + true |\n\nUse it as a filter, not a formula: draft with the headline formulas above, then run each candidate through \"Now you can…\" and keep the survivors.\n\n### The Human Action Model (landing-page narrative spine)\n\nLudwig von Mises' Human Action Model explains *why* anyone acts: a person acts only when three things line up. Every above-the-fold that converts follows the same three-beat spine:\n\n1. **Current discomfort**: the felt problem, named in the reader's own words. They have to recognize their situation (\"that's exactly me\").\n2. **Better vision**: a clearly imagined, more satisfying state. What life looks like once the discomfort is gone.\n3. **Path to action**: the belief that *this specific step* closes the gap between the two. The product is the bridge, and the CTA is how they cross it.\n\nMiss any beat and the reader stalls. No discomfort = no reason to move. No vision = no destination. No path = no reason to believe *you're* the way there.\n\n**Mapping it onto the hero:**\n\n| Beat | Where it usually lives | Example |\n|------|------------------------|---------|\n| Current discomfort | Eyebrow, subhead, or problem-framed headline | \"You shouldn't have to feel awkward sending out your scheduling link\" |\n| Better vision | Headline or subhead | \"Scheduling that feels considerate, not one-sided\" |\n| Path to action | CTA + supporting proof | \"Start scheduling free\" |\n\nThis is the transformation spine underneath the \"6 essential sections\" of a landing page (hero, social proof, problem, solution, how-it-works, and final CTA). The hero states the transformation; the rest of the page substantiates each beat.\n\n### The Perception Gap\n\nThe same benefit can read as a **selling point to one segment and a red flag to another**. The gap is between what *you* think you're saying and what a given reader hears through their own risk tolerance.\n\nThe fix is **matching the value prop to the reader's risk tolerance**. Segment first, then swap the framing.\n\n| Benefit as written | Startup / early-adopter hears | Enterprise / risk-averse hears |\n|--------------------|-------------------------------|--------------------------------|\n| \"Move fast. Ship in a weekend.\" | Speed, momentum (✅) | Immature, unstable (🚩) |\n| \"Brand-new approach\" | Innovative edge (✅) | Unproven, risky (🚩) |\n| \"Enterprise-grade security & SLAs\" | Bloated, slow, expensive (🚩) | Safe, trustworthy (✅) |\n| \"Trusted by the Fortune 500\" | Not built for me (🚩) | Proven, de-risked (✅) |\n\n**Value-prop swap in practice** (same product, two audiences):\n\n- *Startup landing page:* \"Ship your first integration this afternoon. Pay by card and skip the sales call.\"\n- *Enterprise landing page:* \"SOC 2 Type II, 99.99% uptime SLA, and a named implementation lead. Roll out with confidence.\"\n\nWhen a page has to serve both, don't average them into mush. Segment the traffic (separate pages, or a persona split) and let each read its own version of the truth.\n\n### Worked Example: SavvyCal (message-market fit)\n\nSavvyCal (a scheduling tool) originally led with feature-forward copy. They rewrote the hero around a single felt discomfort:\n\n> **\"You shouldn't have to feel awkward sending out your scheduling link.\"**\n\nThat one line **roughly tripled (3×) conversions**. It works because it hits all three beats of the Human Action Model at once:\n\n- **Discomfort:** the small social awkwardness of \"here's my link, pick a time,\" named exactly as users feel it.\n- **Vision:** scheduling that feels considerate to *both* people.\n- **Path:** SavvyCal's overlay-your-calendar mechanic is the bridge, so the CTA feels like the obvious next step.\n\nThe lesson: message-market fit beats feature lists. The winning line named a real feeling the reader hadn't heard a scheduling tool acknowledge before. Run your own hero through \"Now you can…\" and the Human Action Model to find that line.\n\n### Clarity Beats Cleverness (the metrics)\n\nWhen teams measure it, clarity is what moves the numbers. Clearer positioning and copy is associated with:\n\n- **+81% conversions**\n- **−38% sales cycle** (shorter time to close)\n- **−28% CAC** (lower customer acquisition cost)\n- **+175% referrals**\n\nThe mechanism: clear copy lets the *right* buyer self-qualify fast and the wrong one bounce early, so every downstream metric improves. Clever copy that requires decoding does the opposite. It adds a comprehension tax at the exact moment attention is scarcest.\n\n**Practical rule:** if a reader has to pause to figure out what you mean, you've already lost. When forced to choose between a clever line and a clear one, ship the clear one, then use the tests above (\"Now you can…\", the Human Action Model, the Perception Gap) to make the clear line compelling too.\n"
        },
        "natural-transitions.md": {
            "name": "Natural Transitions",
            "path": "natural-transitions.md",
            "content": "# Natural Transitions\n\nTransitional phrases to guide readers through your content. Good signposting improves readability, user engagement, and helps search engines understand content structure.\n\nAdapted from: University of Manchester Academic Phrasebank (2023), Plain English Campaign, web content best practices\n\n---\n\n## Contents\n- Previewing Content Structure\n- Introducing a New Topic\n- Referring Back\n- Moving Between Sections\n- Indicating Addition\n- Indicating Contrast\n- Indicating Similarity\n- Indicating Cause and Effect\n- Giving Examples\n- Emphasising Key Points\n- Providing Evidence (neutral attribution, expert quotes, supporting claims)\n- Summarising Sections\n- Concluding Content\n- Question-Based Transitions\n- List Introductions\n- Hedging Language\n- Best Practice Guidelines\n- Transitions to Avoid (AI Tells)\n\n## Previewing Content Structure\n\nUse in long guides to orient readers. On marketing pages, start with the content instead.\n\n- Here's what we'll cover...\n- This guide walks you through...\n- Below, you'll find...\n- We'll start with X, then move to Y...\n- First, let's look at...\n- The sections below explain...\n\n---\n\n## Introducing a New Topic\n\n- Regarding X,...\n- Speaking of X,...\n- Now let's talk about X.\n- Another key factor is...\n- X is worth exploring because...\n\n---\n\n## Referring Back\n\nUse to connect ideas and reinforce key points:\n\n- As mentioned earlier,...\n- As we covered above,...\n- Remember when we discussed X?\n- Building on that point,...\n- Going back to X,...\n- Earlier, we explained that...\n\n---\n\n## Moving Between Sections\n\n- Now let's look at...\n- Next up:...\n- Moving on to...\n- With that covered, let's turn to...\n- Now that you understand X, here's Y.\n- That brings us to...\n\n---\n\n## Indicating Addition\n\n- Also,...\n- Plus,...\n- On top of that,...\n- What's more,...\n- Another benefit is...\n- Beyond that,...\n- In addition,...\n- There's also...\n\n**Note:** Avoid \"moreover\" and \"furthermore\" in marketing copy. They read as AI-generated.\n\n---\n\n## Indicating Contrast\n\n- However,...\n- But,...\n- That said,...\n- On the flip side,...\n- In contrast,...\n- Unlike X, Y...\n- While X is true, Y...\n- Despite this,...\n\n---\n\n## Indicating Similarity\n\n- Similarly,...\n- Likewise,...\n- In the same way,...\n- Just like X, Y also...\n- This mirrors...\n- The same applies to...\n\n---\n\n## Indicating Cause and Effect\n\n- So,...\n- This means...\n- As a result,...\n- That's why...\n- Because of this,...\n- This leads to...\n\n---\n\n## Giving Examples\n\n- For example,...\n- For instance,...\n- Here's an example:...\n- Take X, for instance.\n- Consider this:...\n- A good example is...\n- To illustrate,...\n- Like when...\n- Say you want to...\n\n---\n\n## Emphasising Key Points\n\n- Here's the key takeaway:...\n- The important thing is...\n- What matters most is...\n- Pay attention to...\n\n---\n\n## Providing Evidence\n\nUse when citing sources, data, or expert opinions:\n\n### Neutral attribution\n- According to [Source],...\n- [Source] reports that...\n- Research shows that...\n- Data from [Source] indicates...\n- A study by [Source] found...\n\n### Expert quotes\n- As [Expert] puts it,...\n- [Expert] explains,...\n- In the words of [Expert],...\n- [Expert] notes that...\n\n### Supporting claims\n- This is backed by...\n- Evidence suggests...\n- The numbers confirm...\n- This aligns with findings from...\n\n---\n\n## Summarising Sections\n\n- To recap,...\n- In short,...\n- Quick summary:...\n\n---\n\n## Concluding Content\n\n- Wrapping up,...\n- The bottom line is...\n- Here's what to do next:...\n- To sum up,...\n- Final thoughts:...\n- Ready to get started?...\n- Now it's your turn.\n\n**Note:** Avoid \"In conclusion\" at the start of a paragraph. It's overused and signals AI writing.\n\n---\n\n## Question-Based Transitions\n\nUseful in long-form content for conversational tone and featured snippet optimization. Use them as headings or questions the reader would really ask, then answer with substance. Don't use them as a setup for your own punchline, and keep them out of landing-page copy (see [ai-tells.md](ai-tells.md)).\n\n- So what does this mean for you?\n- How do you actually do this?\n- Wondering where to start?\n\n---\n\n## List Introductions\n\nFor numbered lists and step-by-step content:\n\n- Here's how to do it:\n- Follow these steps:\n- The process is straightforward:\n- Here's what you need to know:\n- Key things to consider:\n- The main factors are:\n\n---\n\n## Hedging Language\n\nFor claims that need qualification or aren't absolute:\n\n- may, might, could\n- tends to, generally\n- often, usually, typically\n- in most cases\n- it appears that\n- evidence suggests\n- this can help\n\n---\n\n## Best Practice Guidelines\n\n1. **Match tone to audience**: B2B content can be slightly more formal; B2C often benefits from conversational transitions\n2. **Vary your transitions**: Repeating the same phrase gets noticed (and not in a good way)\n3. **Don't over-signpost**: Trust your reader; every sentence doesn't need a transition\n4. **Use for scannability**: Transitions at paragraph starts help skimmers navigate\n5. **Keep it natural**: Read aloud; if it sounds forced, simplify\n6. **Front-load key info**: Put the important word or phrase early in the transition\n\n---\n\n## Transitions to Avoid (AI Tells)\n\nThese phrases are overused in AI-generated content:\n\n- \"That being said,...\"\n- \"It's worth noting that...\"\n- \"At its core,...\"\n- \"In today's digital landscape,...\"\n- \"When it comes to the realm of...\"\n- \"This begs the question...\"\n- \"Let's delve into...\"\n\nSee [ai-tells.md](ai-tells.md) for the full copy blacklist, including structural patterns like contrast reveals and negation lists.\n"
        }
    },
    "evals": {
        "skill_name": "copywriting",
        "evals": [
            {
                "id": 1,
                "prompt": "Write homepage copy for a SaaS tool that automates employee onboarding. Target audience is HR directors at mid-size companies (200-2000 employees). Main differentiator is that it integrates with all major HRIS systems and cuts onboarding time from 2 weeks to 2 days.",
                "expected_output": "Should check for product-marketing.md first. Should write full page copy organized by section: Headline, Subheadline, CTA (above the fold), then Social Proof, Problem/Pain, Solution/Benefits, How It Works, Objection Handling, and Final CTA. Should follow copywriting principles: clarity over cleverness, benefits over features, specificity (use the '2 weeks to 2 days' stat), customer language. Headline should communicate core value proposition. CTAs should be action-oriented ('Start Free Trial' not 'Submit'). Should provide 2-3 headline alternatives with rationale. Should include annotations explaining key copy choices. Should include meta content (SEO page title and meta description).",
                "assertions": [
                    "Checks for product-marketing.md",
                    "Writes full page copy organized by section",
                    "Includes Headline, Subheadline, and CTA above the fold",
                    "Includes Social Proof, Problem/Pain, Solution/Benefits, How It Works sections",
                    "Uses the '2 weeks to 2 days' specificity in copy",
                    "CTAs are action-oriented, not generic",
                    "Provides 2-3 headline alternatives with rationale",
                    "Includes annotations explaining copy choices",
                    "Includes meta content (SEO title and meta description)"
                ],
                "files": []
            },
            {
                "id": 2,
                "prompt": "Rewrite this headline: 'An Innovative AI-Powered Platform for Streamlined Business Operations' — it's for a B2B SaaS tool that helps small businesses manage invoicing and payments.",
                "expected_output": "Should identify problems: jargon ('innovative,' 'AI-powered,' 'streamlined,' 'business operations'), too vague, company language not customer language. Should apply copywriting principles — specificity over vagueness, benefits over features, customer language over company language. Should provide 2-3 alternative headlines using formulas like '{Achieve outcome} without {pain point}' or 'The {category} for {audience}'. Each alternative should include rationale. Should also suggest a subheadline that adds specificity.",
                "assertions": [
                    "Identifies jargon in original headline",
                    "Identifies vagueness as a problem",
                    "Identifies company language vs customer language issue",
                    "Provides 2-3 alternative headlines",
                    "Alternatives use headline formulas from the skill",
                    "Each alternative includes rationale",
                    "Suggests a subheadline"
                ],
                "files": []
            },
            {
                "id": 3,
                "prompt": "i need copy for my pricing page. we have three plans: starter ($29/mo), pro ($79/mo), business ($199/mo). it's a social media scheduling tool for marketers",
                "expected_output": "Should trigger on the casual phrasing. Should ask or infer audience context. Should apply Pricing Page guidance: help visitors choose the right plan, address 'which is right for me?' anxiety, make recommended plan obvious. Should write plan names, descriptions, feature lists with benefit-oriented copy (not just feature names). Should include a page headline that addresses the pricing decision. CTAs should be specific per plan. Should handle objection handling (FAQ copy). Should provide alternatives for key elements.",
                "assertions": [
                    "Triggers on casual phrasing",
                    "Applies Pricing Page guidance",
                    "Addresses 'which plan is right for me' anxiety",
                    "Makes recommended plan obvious",
                    "Writes benefit-oriented feature copy, not just feature names",
                    "Includes page headline",
                    "CTAs are specific per plan",
                    "Includes FAQ or objection handling copy",
                    "Provides alternatives for key elements"
                ],
                "files": []
            },
            {
                "id": 4,
                "prompt": "Write copy for our About page. We're a 3-person startup that built a developer tool for database migrations. Founded because we kept losing data during migrations at our last jobs. Tone should be professional but human.",
                "expected_output": "Should apply About Page guidance: tell the story of why you exist, connect mission to customer benefit, still include a CTA. Should adapt voice and tone to 'professional but human' as specified. Should tell the founder origin story authentically. Should connect the personal pain to the customer's pain. Should include a CTA even on the About page. Copy should follow style rules: active voice, confident, specific. Should NOT be overly corporate or generic.",
                "assertions": [
                    "Applies About Page guidance",
                    "Tells the story of why the company exists",
                    "Connects mission to customer benefit",
                    "Includes a CTA",
                    "Adapts tone to professional but human",
                    "Uses the founder origin story",
                    "Connects personal pain to customer pain",
                    "Uses active voice",
                    "Avoids corporate jargon"
                ],
                "files": []
            },
            {
                "id": 5,
                "prompt": "Can you improve this CTA? We currently have 'Learn More' on our feature page for our analytics dashboard product.",
                "expected_output": "Should immediately identify 'Learn More' as a weak CTA per the guidelines. Should apply the CTA formula: [Action Verb] + [What They Get] + [Qualifier]. Should provide 2-3 strong alternatives like 'See the Dashboard in Action,' 'Start Your Free Trial,' or 'Explore Analytics Features.' Each alternative should include rationale and context for when it works best. Should also consider CTA hierarchy — whether this is a primary or secondary CTA, and suggest complementary CTAs if relevant.",
                "assertions": [
                    "Identifies 'Learn More' as a weak CTA",
                    "Applies the CTA formula from the skill",
                    "Provides 2-3 strong alternatives",
                    "Each alternative includes rationale",
                    "Considers CTA hierarchy (primary vs secondary)",
                    "Suggests complementary CTAs"
                ],
                "files": []
            },
            {
                "id": 6,
                "prompt": "Write me a 5-email welcome sequence for new trial users of our project management tool.",
                "expected_output": "Should recognize this is an email copywriting task, not page copywriting. Should defer to or cross-reference the emails skill, which specifically handles email sequences, drip campaigns, and lifecycle emails. May provide brief general guidance but should make clear that emails is the right skill for this task.",
                "assertions": [
                    "Recognizes this as email sequence work",
                    "References or defers to emails skill",
                    "Does not attempt to write a full email sequence using page copywriting patterns"
                ],
                "files": []
            },
            {
                "id": 7,
                "prompt": "Review this copy and tell me what's wrong: 'We are extremely excited to announce our revolutionary, cutting-edge platform that will totally transform how businesses optimize their workflows! Sign up now!!'",
                "expected_output": "Should apply the Quick Quality Check. Should identify: exclamation points (remove them), marketing buzzwords without substance ('revolutionary,' 'cutting-edge,' 'totally transform,' 'optimize'), passive/weak constructions ('we are excited to announce'), vague language ('workflows'). Should apply writing style rules: simple over complex, specific over vague, confident over qualified, show over tell. Should rewrite the copy following these principles. Should provide 2-3 alternatives.",
                "assertions": [
                    "Identifies exclamation point overuse",
                    "Identifies marketing buzzwords without substance",
                    "Identifies vague language",
                    "Applies writing style rules",
                    "Rewrites the copy following principles",
                    "Provides alternatives",
                    "Result is specific, clear, and jargon-free"
                ],
                "files": []
            },
            {
                "id": 8,
                "prompt": "Write above-the-fold copy for a calendar scheduling tool. Our differentiator is that the recipient gets to overlay their own calendar on the invite, so picking a time feels fair to both people instead of one-sided. Same product needs to work for indie founders AND for enterprise ops teams.",
                "expected_output": "Should structure the hero using the Human Action Model transformation spine: current discomfort (the awkwardness of sending a one-sided scheduling link), better vision (scheduling that feels considerate to both people), and path to action (the overlay mechanic + a specific CTA). Should run headline candidates through the 'Now you can' test and prefer lines that are compelling and true. Should reference or echo the SavvyCal awkward-link insight ('You shouldn't have to feel awkward sending out your scheduling link') as the message-market-fit model. Should surface the Perception Gap: the same benefit reads differently by risk tolerance, so it should provide a value-prop swap — a founder-facing framing (speed, no sales calls) and an enterprise-facing framing (security, SLAs, reliability) rather than one averaged, mushy message. Should favor clarity over cleverness and provide 2-3 headline alternatives with rationale.",
                "assertions": [
                    "Structures the hero as discomfort -> vision -> path (Human Action Model)",
                    "Applies the 'Now you can' test to headline candidates",
                    "References the SavvyCal awkward-link message-market-fit insight",
                    "Surfaces the Perception Gap between segments",
                    "Provides a value-prop swap: founder framing vs enterprise framing",
                    "Favors clarity over cleverness",
                    "Provides 2-3 headline alternatives with rationale"
                ],
                "files": []
            },
            {
                "prompt": "Write a homepage hero (headline, subhead, CTA) and a short launch post for X for our Shopify inventory app. It installs from the Shopify App Store in one click, needs no signup form or credit card, and runs low-stock alerts, reorder emails, and supplier purchase orders off the product and sales data the store already has, so there's nothing to import.",
                "expected_output": "Should write the hero and post without AI tells despite a brief that invites them. Should not use 'it's not X, it's Y' or 'not because X, because Y' reveals, 'no X, no Y, no Z' negation lists, or sentences that state the claim and then trail extra comma clauses ('..., no imports, no spreadsheets'). Should describe what happens (one-click install; alerts, reorder emails, and purchase orders run off existing Shopify data) and state a key absence at most once, plainly, near the CTA ('No card required'). Should use no em dashes in the hero or the post, no self-answered questions or colon reveals, and no stock phrases ('Say goodbye to', 'X, reimagined', 'seamless'). Should run the self-check before delivering.",
                "assertions": [
                    "No contrast reveal ('not X, Y' / 'not because X, because Y')",
                    "No 'no X, no Y, no Z' negation list; any absence stated once",
                    "No sentence that trails extra comma clauses after the main claim",
                    "No em dashes in the hero or the post",
                    "No self-answered questions, colon reveals, or stock phrases",
                    "Describes the mechanism concretely (one-click install, runs off existing Shopify data)"
                ],
                "files": [],
                "id": 9
            }
        ]
    },
    "exported_at": "2026-10-12T10:27:30+02:00"
}