Claude prompt for copywriting: Microcopy (Common Fixes)
Claude · Copywriting · Common Fixes
You are a senior specialist using Claude for copywriting, specifically microcopy.
Job: empty, error, success.
Audience: ux writing. Constraint: human not cute.
Working style: diagnostic. Optimize for typical failures and how to repair the prompt.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.A strong Claude copywriting microcopy prompt names the job, audience, and finish line. This page does that for ux writing. In practice, one customization pass is enough when the brief is this specific. The common fixes version uses diagnostic language and targets typical failures and how to repair the prompt.
When to use this prompt
Claude shines at copywriting work when you state the observable outcome: empty, error, success. The Common Fixes framing keeps typical failures and how to repair the prompt visible while you edit. Bookmark this page if you run microcopy weekly.
Why this prompt works
- Asks for a self-check pass, which cuts hallucinated details.
- Locks the audience (ux writing) before style so tone stays honest.
- Repeats the hard constraint: human not cute.
- Centers empty, error, success so success is observable.
- The common fixes angle adds typical failures and how to repair the prompt without extra fluff.
How to use it in Claude
Save the winning variant for microcopy — teams with a short library ship faster. For copywriting work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. When ux writing review output, they should see typical failures and how to repair the prompt without hunting for it. Redact client names; keep structure. Slug microcopy-fixes is your canonical URL for this brief. Ask for a shorter version after the long one; compression reveals weak claims.
Have Claude list assumptions about copywriting before drafting. Delete any you cannot defend. For microcopy in copywriting, the failure mode is usually no example. This prompt blocks that by design — especially "human not cute". Expect two minutes customizing and two minutes editing for Common Fixes output. Anthropic models still need your facts for microcopy; they cannot invent metrics or brand rules. writers and conversion teams teams bookmark slug microcopy-fixes when typical failures and how to repair the prompt matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (ux writing, offer, timeline).
- Confirm the constraint is still visible: human not cute.
- If output is vague, ask Claude to restate assumptions as questions first.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Microcopy, 3 short sections, bullet list of recommendations, closing line that states human not cute. Facts you supply appear; nothing invented.
Common mistakes
- Deleting "human not cute" to save space — that is usually the whole point.
- Accepting the first draft without checking empty, error, success.
- Skipping the audience (ux writing) and hoping Claude infers it.
Expert notes
Anthropic users working on microcopy in copywriting should treat "human not cute" as non-negotiable. Headlines, landing pages, and offer copy. When ux writing run the Common Fixes variant, they usually care about typical failures and how to repair the prompt more than length.
If text output feels generic, re-paste human not cute as the first follow-up message — do not rewrite the whole prompt.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a microcopy piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Ship a draft, then tighten. Do not chase a perfect first token.
- Document what changed when you customized slug microcopy-fixes.
- Compare against other Claude angles on the same use case before you standardize.
- Keep human not cute visible in the prompt, not only in your head.
- ux writing should recognize themselves in the first paragraph.
FAQ
- What is a Claude prompt for microcopy?
- It is a structured brief that tells Claude how to produce copywriting output for ux writing. This common fixes version stresses typical failures and how to repair the prompt and keeps "human not cute" in the instructions.
- How do I customize this Claude copywriting prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "human not cute" should stay unless your brief truly changed.
- Why use the common fixes angle for microcopy?
- Different angles solve different failures. Common Fixes helps when ux writing need typical failures and how to repair the prompt. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.