AI CODING TOOLS / LESSON 06
Effective Prompting.
Communicate clearly with Claude for the best results
Loading the lesson…
Loading activities…
Browse lessons
AI CODING TOOLS / LESSON 06
Communicate clearly with Claude for the best results
Loading the lesson…
Loading activities…
How you ask Claude Code for help changes what you get back. Like, a LOT. This lesson starts with the basics and works up to the patterns power users lean on every day.
Quick warning before we start. The internet is crawling with "prompt engineering" gurus selling secret templates (oh sure, he's a PrOmPt ExPeRt after three weeks of Claude Code). Three weeks doesn't make anybody an expert. The real secret is boring as heck... it's clear communication, and that's all this lesson is.
A prompt is just what you type to Claude. Your message, your request or your question. Better prompts get better answers.
Think about asking for directions. "Where's the place?" won't get you very far. "Where's the nearest coffee shop that's open right now?" gets you a latte.
Vague prompts get vague results, and specific prompts get exactly what you need.
Claude Code can see your files, but it still helps to point it in the right direction.
That hands Claude the location, what's happening (a crash) and what SHOULD happen (an error message).
Tell Claude what you're trying to pull off, on top of the thing you want it to do.
Once Claude gets your goal, it can suggest better approaches you might never have thought of.
The biggest prompting mistake out there is dictating the how when you should be delegating the what.
Why delegation works better.
When Claude over-engineers something or wanders off in the wrong direction, add explicit constraints.
Good constraints tell Claude what not to do.
| Constraint Type | Example |
|---|---|
| Scope | "Only modify this one file" |
| Complexity | "No abstractions, just inline logic" |
| Dependencies | "No new packages" |
| Coverage | "Don't add tests yet, just the implementation" |
| Style | "Match the pattern used in the existing userUtils.ts" |
Got a big task? Break it into explicit steps.
That keeps Claude from sprinting ahead and gives you checkpoints along the way.
Problem. Cramming a pile of unrelated jobs into one session.
Why it fails. Context fills up with unrelated code. Later tasks come out worse because Claude's working memory is cluttered with earlier stuff that doesn't matter anymore.
Fix. One task per session. Use /clear between unrelated tasks.
Problem. Jumping on every little imperfection with a correction until you're stuck in a back-and-forth spiral.
Why it fails. Every correction adds context. After 10 of them, Claude has lost the big picture.
Fix. Batch your feedback. Wait until you can describe the whole end result in one message.
Problem. Open-ended prompts with no clear finish line.
Why it fails. Claude has no idea when it's done, so it might go refactor things that were totally fine.
Fix. Spell out what "better" means. "Reduce the dashboard load time to under 2 seconds" is something Claude can actually hit.
When Claude is mid-action and heading the wrong way, here's the move.
If Claude already made changes you don't want, use /rewind to roll back to an earlier point in the conversation.
For the bigger requests, use this structure.
Is it fancy? Nope. Does it work? Every single time.