autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with…
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
$ npx -y skills add MaximoCorrea1/ultra-powers --skill copywriting --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/copywritingContext preview
The summary Claude sees to decide when to auto-load this skill.
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
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," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. 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.0.1
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 `.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.
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.
---
1. **Simple over complex** — "Use" not "utilize," "help" not "facilitate" 2. **Specific over vague** — Avoid "streamline," "optimize," "innovative" 3. **Active over passive** — "We generate reports" not "Reports are generated" 4. **Confident over qualified** — Remove "almost," "very," "really" 5. **Show over tell** — Describe the outcome instead of using adverbs 6. **Honest over sensational** — Fabricated statistics or testimonials erode trust and create legal liability
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](references/copy-frameworks.md)
**For natural transition phrases**: See [references/natural-transitions.md](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](references/copy-frameworks.md)
---
**Weak CTAs (avoid):**
**Strong CTAs (use):**
**Formula:** [Action Verb] + [What They Get] + [Qualifier if needed]
Examples:
---
The everything-Flow for building, shipping, and growing software — 40 hand-picked skills from 7 open-source suites, behind one FLOW.md router that fires the right skill on intent (and disambiguates the overlaps), with mandatory routing that survives context
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with…
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.…
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and…
Document a recently solved problem to compound your team's knowledge
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue…
Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI…