skills/marketing/copywriting/SKILL.md
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," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
npx skillsauth add pedronauck/skills copywritingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
If you have to choose between clear and creative, choose clear.
Features: What it does. Benefits: What that means for the customer.
Use words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets.
Each section should advance one argument. Build a logical flow down the page.
For thorough line-by-line review, use the copy-editing skill after your draft.
Get to the point. Don't bury the value in qualifications.
❌ Slack lets you share files instantly, from documents to images, directly in your conversations
✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires.
Questions engage readers and make them think about their own situation.
Analogies make abstract concepts concrete and memorable.
Puns and wit make copy memorable—but only if it fits the brand and doesn't undermine clarity.
Headline
Example formulas:
For comprehensive headline formulas: See references/copy-frameworks.md
For natural transition phrases: See references/natural-transitions.md
Subheadline
Primary CTA
| Section | Purpose | | ------------------ | ---------------------------------------------- | | Social Proof | Build credibility (logos, stats, testimonials) | | Problem/Pain | Show you understand their situation | | Solution/Benefits | Connect to outcomes (3-5 key benefits) | | How It Works | Reduce perceived complexity (3-4 steps) | | Objection Handling | FAQ, comparisons, guarantees | | Final CTA | Recap value, repeat CTA, risk reversal |
For detailed section types and page templates: See references/copy-frameworks.md
Weak CTAs (avoid):
Strong CTAs (use):
Formula: [Action Verb] + [What They Get] + [Qualifier if needed]
Examples:
Before writing, establish:
Formality level:
Brand personality:
Maintain consistency, but adjust intensity:
When writing copy, provide:
Organized by section:
For key elements, explain:
For headlines and CTAs, provide 2-3 options:
development
Deep review of branch diffs, working trees, or GitHub PRs at any size. Use when the user asks for CodeRabbit-grade review, an incremental re-review after new pushes, publication of findings to a PR, a cross-LLM peer-review verdict round, or conformance review against spec artifacts. Don't use for applying fixes, reviewing specs or PRDs as documents, or quick single-file feedback.
tools
Orchestrate Claude and Codex worker TUIs from a controller agent through herdr panes and the herdr socket CLI. Use when delegating bounded tasks to herdr worker panes, running user-activated plan-first delegations (Claude Code plan mode, Codex Plan mode), waiting on native agent status (idle, working, blocked, done), or verifying worker reports. Workers launch as interactive TUIs via herdr agent start — never through headless runners (compozy exec, claude -p, codex exec). Not for cmux workspaces (see cmux-orchestration) and not for end-user herdr control.
tools
TanStack Query, Router, and Form patterns for React. Use when writing useQuery/queryOptions, mutations, caching, file-based routes, search params, loaders, or TanStack Form validation. Don't use for TanStack Start, TanStack DB/collections, Zustand client state, or non-TanStack routing.
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.