Better Instructions | Claude Code Guide

The quality of what Claude Code builds depends entirely on the quality of your instructions. Vague instructions get vague results. Specific instructions get exactly what you want. This isn't a Claude Code limitation. It's a communication principle. Try telling a contractor "make the house nice" versus "paint the bedroom walls sage green, replace the carpet with light oak hardwood, and add recessed lighting." Same contractor, wildly different outcomes. (My wife operates on a different principle: give her permission to "improve" anything, and she'll find something to change, tear down, or rebuild. The specificity of instructions is irrelevant. The outcome is renovation.) ## Vague vs. Specific Watch the difference: **Vague:** "Make me a website." Claude will build something. It'll be generic. Wrong colors, wrong content, wrong layout. You'll spend the next twenty minutes correcting everything. **Specific:** "Create a one-page website for a coffee shop called Bean There. Dark brown background, cream text. Three sections: hero with the shop name and tagline 'Coffee worth the detour,' a menu section with six items, and a contact section with address and hours." Claude builds exactly that. Maybe you tweak the font or adjust spacing. But you're refining, not rebuilding. The time you spend writing a clear instruction saves you five times that in back-and-forth corrections. That said, Claude Code gets smarter with each update. If your instruction is missing something important, Claude will often ask clarifying questions before diving in. And if it doesn't ask but you wish it would, just say "before you start, ask me any questions you need answered." You can always clarify as you go. ## Three Levels of Instructions Not everything needs a detailed brief. Match your instruction level to the task: **Level 1: Quick ask** For simple, obvious things - especially if you're already in a conversation and this is a follow-up. ```text Change the heading color to white ``` **Level 2: Guided task** For tasks with specific requirements. ```text Create a contact page with a form. Fields: name, email, message. Dark background matching the home page. Submit button in green. Add a heading that says "Let's Talk" ``` **Level 3: Big project (let Claude ask questions)** For complex work where you might miss details. ```text I want to add a blog section to my website. Before you build anything, ask me questions about what I need. Things like layout, categories, how many posts to show, that sort of thing. ``` Level 3 is underrated. Letting Claude interview you before it starts building often produces better results than trying to specify everything upfront. Claude asks questions you wouldn't think of. ## Useful Slash Commands Claude Code has a few built-in commands that start with `/`. You don't need to memorize them all, but these four are worth knowing: - **`/help`** shows available commands and tips - **`/compact`** summarizes the conversation so Claude has more room to think (useful in long sessions) - **`/clear`** wipes the conversation and starts fresh - **`/exit`** closes Claude Code The most useful one is `/clear`. When a conversation gets long and Claude starts giving weird results, `/clear` resets everything. Claude re-reads your files and starts fresh. Think of it as rebooting a confused conversation. It's also useful when you finish one task and move to something completely unrelated - a fresh start helps Claude focus instead of carrying baggage from the previous work. You know that feeling of "let me sleep on this and tackle it tomorrow with fresh eyes"? `/clear` gives Claude that same reset. ## Plan Mode: Look Before You Leap Look below the input field where you type - you'll see a mode indicator. Press **Shift + Tab** to cycle through modes, or just click it. One of them is Plan Mode. In Plan Mode, Claude doesn't do anything. It reads your files, thinks about your request, and shows you a plan. "Here's what I would do: create three files, modify two, add these sections." You review the plan, give feedback, and only then does Claude start building. This is essential for big changes. If you're asking Claude to restructure your site or add a major feature, Plan Mode prevents surprises. You see the approach before any files change. When to use it: - Adding a new page or section to an existing project - Reorganizing files or folders - Anything that touches more than two or three files When to skip it: - Quick edits ("change this color") - Single-file tasks ("create a contact page") ## The "Think Harder" Trick For particularly complex tasks, add the words "think carefully" or "think step by step" to your prompt: ```text I need to reorganize my website navigation. Think carefully about which pages should be in the main menu vs. the footer. Currently I have: Home, About, Services, Portfolio, Blog, Contact, FAQ, Pricing ``` This isn't magic. It tells Claude to spend more time reasoning before answering. The difference is noticeable on complex tasks. On simple tasks, it doesn't matter much. ## Common Instruction Mistakes **Too abstract:** "Make the design better." Better how? Cleaner? Bolder? More colorful? **Too technical (for you):** "Refactor the CSS to use BEM methodology." If you don't know what that means, don't ask for it. Describe the outcome you want instead. **Moving the goalposts:** "Build a portfolio page." Then "Actually make it a grid." Then "Wait, cards instead." Then "No, go back to the grid." Pick a direction and commit, at least for one iteration. You can always change it later with a clear instruction. **No context:** "Fix the header." Which header? What's wrong with it? "The header on the home page overlaps the content when I scroll down on my phone" is a fix Claude can actually make. ## How I Give Instructions I never type "fix my CSS." That's useless. I type something like "the navigation bar overlaps the hero section on mobile, fix the breakpoint in nav.css." That instruction has: - **What's wrong** (nav overlaps hero) - **When it happens** (mobile under 640px) - **Where to look** (nav.css) - **What to fix** (the breakpoint) Four pieces of information. Takes ten seconds to type. Saves minutes of Claude guessing. The pattern is: **what's wrong** + **when/where it happens** + **which file or area** + **what the fix should be** (if you know). You don't always need all four, but more context always helps. > Next up: making Claude Code work on multiple things at once. Yes, it can clone itself.

Giving Claude Code Better Instructions

Vague vs. Specific

Sign In to Unlock

Check Your Email