Claude prompt for copywriting: Microcopy (Workflow)
Claude · Copywriting · Workflow
You are a senior specialist using Claude for copywriting, specifically microcopy.
Job: empty, error, success.
Audience: ux writing. Constraint: human not cute.
Working style: operational. Optimize for step order, checkpoints, and handoffs.
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. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The workflow version uses operational language and targets step order, checkpoints, and handoffs.
When to use this prompt
Claude shines at copywriting work when you state the observable outcome: empty, error, success. The Workflow framing keeps step order, checkpoints, and handoffs visible while you edit. Bookmark this page if you run microcopy weekly.
Why this prompt works
- Separates draft from critique so you can steal the structure later.
- Forces an output contract: headings, examples, and a final version.
- Asks for a self-check pass, which cuts hallucinated details.
- Centers empty, error, success so success is observable.
- Locks the audience (ux writing) before style so tone stays honest.
How to use it in Claude
Use operational follow-ups only — mixing tones mid-thread confuses Anthropic models. Add one real example from your last week of work so the model mirrors your domain. When ux writing review output, they should see step order, checkpoints, and handoffs without hunting for it. Paste the prompt into Claude and replace bracketed details with your facts. Name the success metric aloud: empty, error, success. If the draft cannot pass it, do not polish prose yet.
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 Workflow output. Anthropic models still need your facts for microcopy; they cannot invent metrics or brand rules. writers and conversion teams teams bookmark slug microcopy-workflow when step order, checkpoints, and handoffs 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
Slug microcopy-workflow: a writers and conversion teams-oriented copywriting brief. Headlines, landing pages, and offer copy. Pair it with one real asset from your portfolio before the second run.
Refresh quarterly: Claude models change. Keep constraints; update examples. Mark the page stale if human not cute no longer matches policy.
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
- The Workflow variant is for step order, checkpoints, and handoffs.
- Claude improves when you paste a real snippet or reference still.
- ux writing should recognize themselves in the first paragraph.
- Ship a draft, then tighten. Do not chase a perfect first token.
- Document what changed when you customized slug microcopy-workflow.
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 workflow version stresses step order, checkpoints, and handoffs 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 workflow angle for microcopy?
- Different angles solve different failures. Workflow helps when ux writing need step order, checkpoints, and handoffs. 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.