Introduction
In Chapter 1, you learned about being clear and specific. Now we're taking it to the next level: teaching Claude your style through examples.
Here's the problem: Words like "professional," "friendly," "concise," or "creative" mean different things to different people. Your "professional" might be warm and conversational. Mine might be formal and data-driven.
The solution? Show, don't tell.
When you provide examples of your work, Claude instantly understands your tone of voice, writing style, formatting preferences, personality markers, and level of formality.
This chapter will teach you how to use examples effectively to get Claude writing like YOU.
Why Examples Work Better Than Descriptions
Let me demonstrate with a real scenario.
Attempt 1: Describing the Style
Write a professional email to a client about a project update.
Use a friendly but professional tone.
Claude's Result:
Dear Valued Client,
I hope this email finds you well. I am writing to provide you with
an update regarding the status of your project...
It's... fine. But it's generic. It doesn't sound like ME.
Attempt 2: Showing an Example
I need to write an email to a client about a project update.
Here's my usual email style:
"Hi Sarah!
Quick update on the dashboard project: We wrapped up the user
testing phase this week (15 participants - great feedback!).
The team is excited about what we learned.
Next up: Incorporating the feedback into v2 designs.
Should have mockups ready for your review by Friday.
Any questions about the timeline? Happy to jump on a call.
Best,
Alex"
Now write a similar email for this situation:
- Client: Marcus at TechFlow
- Project: Mobile app redesign
- Update: Just completed the wireframe phase, moving to visual design
- Timeline: Visual designs ready in 2 weeks
- Note: Ahead of schedule by 3 days
Claude's Result:
Hi Marcus!
Quick update on the TechFlow mobile app: We just wrapped up the
wireframe phase (and we're actually 3 days ahead of schedule -
the team's been crushing it!).
Next step: Moving into visual design. You'll have the first round
of polished designs to review in 2 weeks.
Excited to show you what we've put together. Let me know if you
want a preview call before then!
Best,
[Your name]
Now THAT sounds like me!
Same enthusiasm, same structure, same casual-but-professional tone. Claude learned from the example.
The Example Pattern
Here's the basic structure that works:
I need to [TASK]. Here's an example of [SIMILAR WORK]:
[YOUR EXAMPLE]
Now create [NEW VERSION] for [SPECIFIC SITUATION] following
the same [tone/style/format].
The Key Elements
1. State your task — What you need to create
2. Provide your example — Real work you've done before
3. Specify the new situation — The different context/content
4. Explicitly ask to match — "Following the same tone/style/format"
What Claude Learns from Your Examples
When you provide examples, Claude picks up on:
1. Tone and Voice
- Formal vs casual
- Enthusiastic vs measured
- Direct vs diplomatic
- Humorous vs serious
2. Structure and Format
- How you open and close
- Paragraph length
- Use of bullets vs prose
- Headers and sections
3. Language Patterns
- Sentence length
- Vocabulary level
- Technical jargon usage
- Metaphors and analogies
4. Content Approach
- How detailed you get
- What you emphasize
- What you assume readers know
- How you explain concepts
5. Personality Markers
- Specific phrases you use
- Your enthusiasm indicators
- How you address the reader
- Your signature touches
Real Success Story
I used to spend 30 minutes writing client update emails, trying to get the tone just right.
Then I gave Claude three examples of my best client emails and said: "Write update emails following this same style and structure."
Now? 5 minutes. Claude drafts it in my voice, I review and send. The clients can't tell the difference — because it IS my voice, just faster.
Key Takeaways
- Examples teach better than descriptions — "Like this" beats "be professional"
- Use YOUR actual work — Your voice, your style, your patterns
- Be explicit — "Following the same tone and format" tells Claude to learn
- Multiple examples work — Blend different aspects from different examples
- Iterate if needed — First try might be close; refine to perfection