Claude ChatLesson 12

Tips & Best Practices

Small changes to your prompt often change the reply. Five practices that help in regular Claude Chat use.

1. Write clear, specific prompts

Vague prompts force Claude to guess your intent. Specific prompts give it audience, format, length, and context — so the first reply is close to what you need.

Include these when relevant
Who: for a beginner / for executives
What: a 3-paragraph summary
Tone: professional, friendly, technical
Length: under 100 words
Format: bullet list, table, JSON
Context: this is for a job application
✗ Weak prompt
"Help me with my resume."
Claude doesn't know the role, format, or what kind of help you want.
✓ Strong prompt
"Review my resume for a senior developer role. Highlight 3 strengths and 2 areas to improve. Use bullet points."
Role, task, format, and scope are all defined.

2. Use positive and negative examples

Examples are faster than long descriptions. Show Claude one response you like and one you don't — it will match the style and avoid the pitfalls you point out.

Positive example — Shows the tone, length, and style you want
Negative example — Shows what to avoid — too long, too casual, off-brand
Write 3 tweet-length product taglines for a meditation app.

Good example: "Find calm in 5 minutes a day."
Bad example: "The best meditation app ever!!!" (too hype, no specifics)
C
1. "Five minutes. One breath. A calmer you."
2. "Meditation that fits your lunch break."
3. "Quiet your mind without quitting your schedule."
Show Claude what you want and what to avoid — it matches the style of your good example

3. Ask Claude to show its reasoning

For logic, maths, debugging, or multi-part analysis, add phrases like "think step by step" or "show your reasoning". Claude breaks the problem into stages, which improves accuracy and lets you spot errors early.

Useful phrases
"Think step by step."
"Show your reasoning before the final answer."
"Break this into steps and explain each one."
"Work through this carefully — check your logic."
claude.ai
A store sells notebooks for $4 and pens for $2. Maria buys 3 notebooks and 5 pens. How much does she spend? Think step by step.
C
Step 1: Notebooks → 3 × $4 = $12
Step 2: Pens → 5 × $2 = $10
Step 3: Total → $12 + $10 = $22
"Think step by step" prompts Claude to show its reasoning, not only the final answer

4. Break complex tasks into smaller prompts

One giant prompt — "build my entire marketing plan" — often produces shallow results. Split the work into a sequence of focused prompts and build on each answer.

✗ Weak prompt
"Create a complete marketing plan with strategy, content calendar, email templates, social posts, and budget."
Too many deliverables at once — each section will be thin.
✓ Strong prompt
"Step 1: Define 3 target audience personas for our SaaS product. [then] Step 2: Based on those personas, suggest 5 content themes."
One focused task per prompt; each step informs the next.
Complex task split into 4 smaller prompts
✓
"List the 5 main sections a SaaS landing page should have."
✓
"Write hero headline and subheading for a project management tool."
3
"Write 3 feature blocks with title and one-sentence description."
← current step
4
"Draft a call-to-action section with a signup button label."
One prompt per sub-task is clearer than asking for everything at once

5. Iterate and ask follow-up questions

Your first prompt does not need to be perfect. Treat the first reply as a draft and tighten it with short follow-ups.

Common follow-up phrases
"Make it shorter."
"Change the tone to more formal."
"Expand on point 2."
"Add an example for each bullet."
"That's not quite right — try again focusing on X."
"Translate this to French."
claude.ai — iterating on a draft
Write a product description for a wireless keyboard. 80 words, professional tone.
C
[First draft — 82 words, slightly formal…]
Make it shorter — under 60 words. More energetic, less formal.
C
[Revised draft — 58 words, punchier tone…]
Add one sentence about the 2-year battery life.
C
[Final version with battery life added…]
Refine with follow-ups — shorter, change tone, add a detail — instead of starting over

Quick reference

PracticeOne-line rule
Be specificInclude who, what, tone, length, and format
Show examplesGive one good example and one bad example
Show reasoningAsk for step-by-step work on logic, maths, and analysis
Split big tasksOne focused prompt per sub-task
IterateRefine with follow-ups instead of rewriting from scratch
Summary:
  • Specific prompts beat vague ones — define audience, format, and length.
  • Positive and negative examples teach Claude your preferred style faster than rules alone.
  • Step-by-step reasoning improves accuracy on complex problems.
  • Smaller prompts for complex work — build up one layer at a time.
  • Follow-up questions let you refine without starting over.

What's Next

Claude Code Overview — coding in your terminal and IDE with direct access to project files.