TLDR
A first Claude draft is rarely the version you hand to its actual reader. Adapting output for audience runs on two concrete mechanisms: few-shot before/after examples of the target register, and persistent configuration, account instructions, project instructions, or Skills, for audiences you'll hit again. Anthropic: 6 Techniques for Effective Prompt Engineering "Just ask Claude to be more casual" skips both.
What it is
A first Claude draft is rarely the version you hand to its actual reader. This objective is about the deliberate step of re-shaping an output, tone, vocabulary, length, and format together, to fit who will consume it: an executive, a customer, a technical peer, a regulator. Anthropic frames this less as one clever prompt and more as an iterative loop: draft, check against success criteria, adjust, re-check.
Audience-targeting is a named benefit of prompting, not an afterthought. Anthropic's own business-performance guidance lists it as a core payoff: "prompt engineering helps customers deliver targeted experiences for their desired audiences and industries... you can cater to very specific personas and their needs." The exam objective covers four related actions on the same output, edit, adapt, refine, and compare, adjusting a draft and then checking it against an alternative version before deciding which one ships.
How it works
Lever one: few-shot before/after examples. Anthropic's "6 Techniques for Effective Prompt Engineering" reference demonstrates audience-adaptation directly, converting "the platform implements end-to-end encryption protocols to safeguard data integrity" into plain language by first giving Claude two worked before/after examples of jargon-to-plain-language conversion. "Providing examples helps the AI understand the pattern, style, or format you're looking for more clearly than descriptions alone." This is the right lever for a one-off or first-time adaptation to a specific audience.
Lever two: persistent configuration for recurring audiences. Claude's personalization features, account-wide "Instructions for Claude," project-level instructions, and Skills (the current name, migrating from the earlier "Styles" branding), exist specifically so tone and format for a given audience or workflow persist without re-explaining them every turn. Skills are described as letting a user "adjust the tone and format of Claude's responses" and "apply communication patterns based on your own writing or preferences." This is the right lever once you'll hit the same audience or workflow repeatedly, not a one-off request re-typed each time.
Refinement is scoped to controllable success criteria. Anthropic's prompt-engineering overview frames editing as testing a draft against explicit success criteria and adjusting from there, not vague "make it better" iteration. "Does this land for an engineer who needs the root cause?" is a testable criterion; "does this sound better?" is not.
Compare before shipping either version. When one source needs to reach two audiences, the pattern is running two separate adaptation passes, not writing one version that tries to split the difference. Each pass gets its own audience framing and its own few-shot reference, and the two outputs are compared side by side before either goes out, rather than assuming a single "balanced" draft serves both readers.
Where you'll see it
Incident postmortem for two audiences
Runs two adaptation passes on the same source content, one framed for engineering leadership with root-cause detail, one framed for customers in plain language, then compares both before sending either.
Recurring customer-support tone
Sets the desired tone once via project instructions or a Skill instead of re-typing a tone request in every new support ticket.
Side-by-side
| Mechanism | When to use it | What it actually does |
|---|---|---|
| Few-shot before/after examples | One-off or first-time adaptation for a specific audience | Shows Claude the target register directly (e.g. a jargon sentence rewritten in plain language) rather than describing it abstractly |
| Persistent configuration (account instructions, project instructions, Skills) | A recurring audience or workflow you'll hit again | Tone and format persist without re-explaining every turn; Skills can apply communication patterns learned from your own writing |
Question patterns
A PM needs to simplify a technical incident postmortem for a customer-facing status page, and this is the first time this audience adaptation has come up. What's the better move?
"just tell Claude to 'make it simpler' and trust it to guess the right register" skips the example-driven mechanism the exam objective tests.A support team needs the same customer-facing tone applied across dozens of tickets every week. What's the better setup?
"re-explain the desired tone in the prompt for every new ticket to stay flexible" ignores the configuration lever meant exactly for recurring audiences.A PM needs one incident summary to reach both engineering leadership (needs root-cause detail) and a customer status page (needs plain language, no internal system names). What's the recommended approach?
"write one balanced version that tries to satisfy both audiences at once" skips the compare step and risks under-serving both readers.What is the current Claude personalization feature that lets a user apply communication patterns from their own writing automatically?
"Styles and Skills are two separate, unrelated Claude features that must both be configured for personalization to work" misreads a naming migration as two distinct systems.A reviewer edits a Claude draft and decides it's done because "this version reads better than the last one." What's the gap in this evaluation?
"if the new version reads better than the old one, that's sufficient evidence the edit worked" substitutes a vague feeling for a testable criterion.Frequently asked
Is adapting for audience the same as just making an output shorter?
What's the difference between account instructions, project instructions, and Skills?
Work this with your AI
Work this concept hands-on with Claude Code, Codex, or claude.ai. Copy a prompt, paste it into your assistant, and practise in tandem. Each one keeps you active (explain it back, get drilled, or build) rather than just reading.
- Drill it like the exam (scenario MCQs)Practice in the exam's scenario-MCQ format with trap awareness.
- Explain it back (Feynman)Build durable, transferable understanding of a concept you can half-state.
- Test me, adapting the difficultyActive recall practice on a concept you think you know.
- Check my prerequisites firstBefore studying a concept that keeps not sticking.
- Find the high-leverage 20%When a domain feels too big and you are short on time.