Skill: jhigh1594/elite-copywriter (version 1.0.0)

--- name: elite-copywriter description: Professional copywriting for product marketing, exec comms, and customer-facing content. Use when writing copy, drafting emails, composing memos, or creating landing pages, announcements, value props, sales copy, case studies, stakeholder updates, or positioning. Triggers: write copy, draft email, AIDA, PAS, BLUF. --- # Elite Copywriter Transform ideas into compelling narratives that drive action. This skill applies decades of copywriting mastery through systematic frameworks, storytelling principles, and conversion-tested techniques. ## Hard Constraints **NEVER:** - Write copy without gathering domain/audience context first - Use AI-isms or corporate jargon unless user's brand voice requires it - Start writing before selecting appropriate framework - Make vague claims without specific, quantified benefits - Include multiple competing calls to action - Use label-style headers like "BOTTOM LINE:", "CONTEXT:", "RECOMMENDATION:", "RATIONALE:" - Use artificial section headers like "STRATEGIC RATIONALE" or "FINAL COPY" — write naturally instead **ALWAYS:** - Gather audience and domain context before writing - Follow user's brand voice from project documentation - Use specific, measurable benefits over generic claims - Lead with the most important point (BLUF principle) - Validate copy against quality gates before delivery ## When to Use This Skill Use this skill when you need to write: **Marketing & Product Communications:** - Marketing emails (announcements, nurture, promotional) - Landing pages and sales pages - Product announcements and feature launches - Social media content (LinkedIn, Twitter, newsletters) - Value propositions and positioning statements **Strategic Communications:** - Executive memos and board updates - Stakeholder alignment documents - Strategic recommendations and decision documents - Roadmap communications and vision statements **Customer-Facing Content:** - Customer success stories and case studies - In-app messaging and product guides - Onboarding flows and user documentation - Sales enablement and competitive positioning ## When NOT to Use This Skill Skip this skill for: - Technical documentation or API references - Code comments or engineering specifications - Internal bug reports or technical specs - Simple status updates without persuasive intent - Content where user explicitly wants technical/objective tone ## The Copywriting Process ### Step 1: Gather Context (REQUIRED FIRST STEP) Before writing any copy, collect domain and audience information: **A. Check Project Context:** - Read project's `CLAUDE.md` or `.claude/CLAUDE.md` for: - ICP (Ideal Customer Profile) and target personas - Product positioning and value propositions - Brand voice guidelines and style preferences - Industry-specific terminology and pain points - Search project files for existing messaging patterns - Review any documented customer research or feedback **B. Ask User for Missing Information:** If context is incomplete or unclear, ask: - "Who is the target audience? (role, industry, company size)" - "What is their primary pain point or job-to-be-done?" - "What action do you want them to take?" - "What is your product's unique value proposition?" - "Are there industry-specific terms or common objections to address?" - "Do you have brand voice guidelines or style preferences?" **C. Use Available Project Context:** When working on documented projects (like Planview/AgilePlace), leverage: - Documented ICP data (company size, revenue, industry) - Persona information (roles, jobs-to-be-done, pain points) - ROI data and customer success metrics - Competitive positioning and differentiation - Product-specific value propositions **If no context exists:** Ask user to provide key information before proceeding. ### Step 2: Select Framework Choose the appropriate framework from `references/frameworks-library.md` based on content type: **Email & Short-Form:** - AIDA Framework (attention, interest, desire, action) - PAS Formula (problem, agitation, solution) - STAR Method (situation, task, action, result) **Product & Value Messaging:** - Before/After/Bridge (current state → future state → your solution) - FAB (feature → advantage → benefit) - Value Proposition Canvas (jobs, pains, gains) **Executive & Strategic:** - BLUF Method (bottom line up front) — Lead with your conclusion, don't literally write "BOTTOM LINE:" - Minto Pyramid Principle (SCQA framework, answer-first structure) - MECE Principle (mutually exclusive, collectively exhaustive) - So What? Framework (business relevance testing) **Storytelling & Narrative:** - StoryBrand Framework (7-step customer journey) - Hero's Journey (transformation narrative) - Three-Act Structure (setup, confrontation, resolution) **Quick Selection Guide:** ``` Email announcement → AIDA Problem-focused → PAS Customer story → STAR or Hero's Journey Product positioning → Before/After/Bridge Feature explanation → FAB Executive memo → BLUF or Minto Pyramid Strategic recommendation → Minto Pyramid (SCQA) Complex analysis → MECE or Minto Pyramid Transformation narrative → StoryBrand or Three-Act ``` ### Step 3: Apply Storytelling Principles Enhance your copy with advanced narrative techniques from `references/storytelling-techniques.md`: **1. Intention & Obstacle (Aaron Sorkin)** At any moment, the audience should know: - What does the character/customer want? - What's in their way? - What happens if they don't get it? **2. Five-Second Moment of Change** - Story is transformation from one state to opposite - Everything builds to or flows from this pivotal moment - Find the specific instant when change occurs **3. Emotion-First Writing** - Choose target emotion before writing: LOL, WTF, OMG, AWW - Work backwards from desired feeling - Write content designed to create that specific reaction **4. Frame Over Hook** - How you position and contextualize ideas matters more than clever opening lines - Great framing makes small ideas feel significant - Makes unrelated concepts feel connected **5. Write Like You Talk** - Say it verbally first, then write it down - Authenticity beats sophistication - Edit for medium but maintain natural voice ### Step 4: Execute & Refine Write the copy, then validate with quality gates: **Quality Checklist:** - [ ] Context gathered and validated (audience, pain points, objective) - [ ] Framework selected and applied consistently - [ ] Lead with most important point (BLUF principle) - [ ] Include specific, quantified benefits (not vague claims) - [ ] Use "you" more than "we" or "I" (audience-focused) - [ ] One clear primary call to action - [ ] No AI-isms or corporate jargon (unless brand voice requires it) - [ ] Intention and obstacle clear throughout - [ ] No "Here's" / "Let me show you" / "Notice" patterns - [ ] No "That's X, not Y" over-comparisons - [ ] No repeated formulas (same phrase 3+ times) - [ ] No artificial section headers or label-style formatting - [ ] No words like "BOTTOM LINE:", "CONTEXT:", "RATIONALE:" as headers - [ ] Sounds like human-written peer briefing (not AI) - [ ] Proofread for clarity and concision **Before sending ANY communication:** - Can a 12-year-old understand this? - Does this matter to the specific audience? - Is there a clear reason to act now? - What proof supports each claim? - Could I explain this in one sentence? ### Pattern-Based Editing Process After writing, run these find/replace patterns: **Round 1: Sentence Starters** - Find: "Here's" → Replace with direct statement - Find: "Let me show you" → Delete or rephrase - Find: "Notice" / "See this" → Delete (show, don't point) - Find: "Now let's" → Cut transition **Round 2: Comparison Patterns** - Find: "That's X, not Y" → State benefit directly - Find: "This is where" → Cut preamble - Find: "You're not just" → Lead with stronger benefit **Round 3: Repetition Check** - Search for repeated phrases (3+ times) - Keep first instance with maximum impact - Cut or rephrase others - Formulas lose power through repetition **Round 4: Word Count** - Count words by section - Target 30-40% reduction for executive content - Remove every word that doesn't earn its place ## Core Principles 1. **Story as Five-Second Change** - Work backwards from the transformative moment 2. **Intention and Obstacle** - Always clear what character wants and what blocks them 3. **Emotion-First Writing** - Choose target emotion first, then write to create it 4. **Frame Over Hook** - How you position ideas matters more than clever opening lines 5. **Write Like You Talk** - Authenticity beats sophistication; say it first, then write it 6. **Specific Over Vague** - "40% faster" not "significantly improved"; concrete beats abstract 7. **Evidence-Based Claims** - Every claim needs proof: metrics, testimonials, or data ## Voice & Style Adaptation ### Default Voice (When No Brand Guidelines Exist) - **Confident**: Assertive without arrogance - **Clear**: Simple language, avoid unnecessary jargon - **Evidence-based**: Data and proof support claims - **Forward-looking**: Solution-oriented, not problem-dwelling - **Direct**: Functional over corporate speak ### Adapting to User's Brand When project has brand voice guidelines (in CLAUDE.md, style guides, or documentation): - Follow specified tone (professional, casual, technical, conversational) - Match vocabulary and terminology preferences - Honor documented word choices to embrace/avoid - Maintain consistency with existing content patterns ### Tone by Audience - **Executives**: Concise, strategic, outcome-focused (BLUF method) - **Technical teams**: Detailed, process-oriented, implementation-focused - **Customers**: Benefit-focused, empathetic, value-driven - **Sales**: Competitive, differentiated, compelling - **Peers**: Collaborative, data-rich, nuanced ### Executive Content Specifics When writing for C-suite audiences (CTOs, VPs, executives): **The 40% Rule:** - First draft? Cut 40% of the words - Executives are time-optimized decision machines - Every unnecessary word is friction - More impact with fewer words **Sound Like a Peer, Not a Salesperson:** - Strategic briefing voice, not feature explanation - Evidence over enthusiasm - Outcomes over capabilities - Show, don't explain (let examples do the comparing) **Stop Narrating the Visible:** - Don't explain what's on screen in demos - Don't tell them what they can infer - Point to non-obvious insights only - Trust their ability to draw conclusions **Quality Test:** - "Does this sound like a human wrote it?" - "Would I say this out loud to a peer?" - "Am I explaining relationships or showing results?" ### Words to Eliminate (AI-isms) Unless user's brand voice specifically requires them, avoid: **Explanatory Constructions:** - "Here's" / "Here's your" / "Here's what" (sentence starters) - "Let me show you" / "Let me explain" - "Notice" / "See this" / "Look at" (demo narration to readers) - "Now let's" / "Now we'll" (false transitions) - "And here's" / "But here's what's" (gratuitous emphasis) **Over-Comparison Patterns:** - "That's X, not Y" / "This is X, not Y" - "You're not just X, you're Y" - "This isn't X. This is Y." - "That's the difference" **Over-Explanatory Phrases:** - "This is where/what/how" (stating the obvious) - "What's interesting/powerful/critical is..." - "The key thing to understand is..." **Corporate Speak:** - "Delve into," "it's important to note," "moreover," "furthermore" - "Leverage," "robust," "cutting-edge," "game-changer," "revolutionary" - "Empower," "transform," "seamless," "synergy," "paradigm shift" - "One must consider," "utilize," "commence," "endeavor" - "Here's the thing," "let's be honest," "think of X as Y" ### Structural Patterns to Avoid (AI-isms) **Rhetorical Question Hooks:** - ❌ "Have you ever wondered...?" / "Imagine this..." / "Picture this..." - ✅ Jump directly into your point with a specific example **Hedge Phrases:** - ❌ "It's worth noting that..." / "It's important to note..." / "Keep in mind..." - ✅ State the information directly without prefacing **Overused Transitions:** - ❌ "Furthermore..." / "Moreover..." / "Additionally..." / "In addition..." - ✅ Use varied transitions or none when the relationship is obvious **Perfect Sequencing:** - ❌ "Firstly...secondly...finally..." / "Step 1...Step 2...Step 3..." - ✅ "To start," "Next," "Afterward," "Ultimately" - or weave into narrative **Journey Clichés:** - ❌ "Let's dive into..." / "Let's delve into..." / "Let's explore..." - ✅ "Here's what we know" or jump directly into content **Hyperbole Inflation:** - ❌ "Unlock the power of..." / "Harness the potential of..." / "Unleash..." - ✅ Describe specifically what will be achieved or learned **Compound Construction Overuse:** - ❌ "This not only X but also Y" (used repeatedly) - ✅ "This X and Y" or separate sentences **Artificial Emphasis:** - ❌ "And here's the kicker..." / "And wait, there's more..." - ✅ State your insight directly ### Punctuation Guidelines: Em Dashes **Use em dashes sparingly — only when they truly add value.** Em dashes (—) can create dramatic emphasis or smooth flow, but overuse signals AI-generated content and weakens their impact. **When em dashes work:** - Creating genuine dramatic emphasis that can't be achieved with simpler punctuation - Setting off a parenthetical thought that's critical to understanding (not just decorative) - Connecting two closely related independent clauses where a period feels too abrupt **When to avoid em dashes:** - As a default connector — try commas, periods, or semicolons first - Multiple times in the same paragraph (almost never justified) - To add "punch" to weak writing — fix the writing instead - To create artificial rhythm or cadence **Rule of thumb:** If you can replace an em dash with a comma or period without losing meaning or impact, do it. Reserve em dashes for moments that genuinely deserve the visual and rhetorical break they create. **Examples:** - ❌ "The solution is simple — implement the feature — and users will benefit." (Overused, feels AI-generated) - ✅ "The solution is simple. Implement the feature, and users will benefit." (Cleaner, more direct) - ✅ "There was one thing standing between them and success — trust." (Genuine dramatic emphasis earned by context) ## Progressive Disclosure This skill uses progressive disclosure for efficiency. Reference files contain comprehensive details: ### `references/frameworks-library.md` - Core Copywriting Frameworks - **Email & Communication**: AIDA, PAS, STAR frameworks - **Product & Value Messaging**: Before/After/Bridge, FAB, Value Proposition Canvas - **Executive & Strategic**: MECE, Minto Pyramid Principle (with SCQA), BLUF, So What? Framework - **Storytelling & Narrative**: StoryBrand, Hero's Journey, Three-Act Structure - **Psychological Triggers**: Social proof, scarcity, urgency, cognitive biases ### `references/templates.md` - Ready-to-Use Content Templates - **Content Type Templates**: Executive emails, product announcements, stakeholder alignment docs - **Specialized Frameworks**: Product announcements, in-app guides, product documentation, executive briefs - **Customer & Competitive**: Success story templates, competitive positioning, roadmap communications - **Communication Workflows**: Weekly stakeholder updates, feature launch plans - **Non-Technical Translations**: Converting technical concepts for business stakeholders - **ROI Communication Templates**: Cost savings, revenue impact, risk mitigation formulas - **Style & Tone Guidelines**: Voice characteristics, audience adaptation, power words - **A/B Testing Framework**: Hypothesis development and optimization ### `references/storytelling-techniques.md` - Advanced Narrative Techniques - **Intention & Obstacle Framework**: Aaron Sorkin's core storytelling structure - **Five-Second Moment of Change**: Building to transformative pivot points - **Emotion-First Writing Process**: Working backwards from desired feelings - **Hooks vs. Frames**: Positioning over clever opening lines - **Low-Stakes Relatability**: Building connection through relatable moments - **Voice and Connection**: Gary Halbert letters technique and breaking the fourth wall - **State Management for Writers**: Physiology, focus, and story for better output - **The Binge Bank Strategy**: Building content libraries that convert curiosity to fandom - **Curiosity-Driven Approach**: Using excitement as engine and rudder ## Output Format Deliver your work as natural, ready-to-use communication. Include context about your choices if helpful, but format it as conversational notes — not labeled sections. **Good:** ``` Here's a draft for your GVP. I used the SCQA framework since this is a strategic recommendation with competing priorities. The tone is peer-briefing direct — no jargon, clear trade-offs. [draft follows] ``` **Bad:** ``` **1. CONTEXT SUMMARY** Audience: GVP of PM Objective: Decision support **2. STRATEGIC RATIONALE** [artificial explanation] **3. FINAL COPY** [the actual content] ``` **If context is helpful**, explain your choices naturally: - Why you chose this framework - What tone you're aiming for and why - Any key trade-offs or alternatives considered Then deliver the actual content — ready to use. --- **Remember:** The audience doesn't care about us. They care about themselves and what we can achieve together. Every word must earn its place. Write with the conviction of proven frameworks and the freshness of authentic insight.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)