Be Clear & Specific

Introduction

If I had to teach you only ONE thing about working with Claude, it would be this: clarity is everything.

The difference between getting mediocre results and exceptional results from Claude isn't about knowing secret tricks or complex techniques. It's about being clear and specific in what you ask for.

In this chapter, you'll learn why clarity matters, see real examples of weak vs. strong prompts, and practice the technique yourself.

Why Clarity Matters

Think about asking a colleague for help. Which request would get you better results?

Request A: "Can you help me with a presentation?"

Request B: "Can you create a 10-slide presentation for our Q2 sales meeting next Tuesday? It should cover our Q2 performance highlights, top-selling products, and Q3 sales targets. Please provide an outline with 3-4 key points for each slide."

Request B gives your colleague everything they need: the context (Q2 sales meeting), the deliverable (10 slides), the content areas (performance, products, targets), and the format (outline with key points).

Claude works exactly the same way.

Claude is incredibly capable, but it can't read your mind. When you're vague, Claude has to guess what you mean. When you're specific, Claude can focus all its intelligence on exactly what you need.

The Golden Rule

More details = Better results
More context = Smarter responses

This isn't about writing longer prompts for the sake of it. It's about including the essential information Claude needs to help you effectively:

1. WHAT you need — The specific deliverable or outcome
2. WHY you need it — The context or purpose
3. HOW you want it — The format, tone, or structure

Real-World Examples

Example 1: Presentations

What improved:

• Specific number of slides (10)
• Clear topics to cover
• Defined audience
• Stated purpose
• Requested format (outline with key points)

Example 2: Email Writing

What improved:

• Full context provided
• Specific points to address
• Desired tone defined
• Relationship dynamics included
• Clear outcome specified

The Three Essential Questions

Before you send a prompt to Claude, ask yourself these three questions:

1. What exactly do I need?

Be specific about the deliverable:

• "An email" → "A 200-word apology email to a client"
• "A plan" → "A 3-month content calendar with 2 posts per week"
• "Help with code" → "A Python function that validates email addresses"

2. Why do I need it?

Context helps Claude understand your situation:

• "For a job application"
• "To present to the board"
• "To explain to my team"
• "For social media marketing"

3. What format do I want?

Structure helps Claude organize the response:

• "As a bullet-point list"
• "In conversational tone"
• "With code examples"
• "Using markdown formatting"

Common Mistakes to Avoid

Mistake 1: Being Too Vague

Don't: "Make this better"
Do: "Make this more concise - reduce to under 500 words while keeping all key points"

Mistake 2: Assuming Context

Don't: "Write an email to them"
Do: "Write an email to our client Sarah at TechCorp, following up on last week's proposal meeting"

Mistake 3: No Format Guidance

Don't: "Explain this concept"
Do: "Explain this concept in 3 short paragraphs suitable for beginners, using a real-world analogy"

Mistake 4: Ambiguous Goals

Don't: "Help me with my project"
Do: "Help me outline the architecture for a task management web app with user auth, task CRUD, and team collaboration"

When to Be More Specific

You don't always need maximum detail. Simple questions get simple answers:

These are fine as-is:

• "What's the capital of France?"
• "Convert 100 USD to EUR"
• "Define 'recursion' in programming"

These need more detail:

• "Help me with my business"
• "Write content for me"
• "Analyze this data"
• "Create a strategy"

Rule of thumb: If the answer requires understanding YOUR specific situation, provide that situation.