Description
Turn a vague "it's broken" into the precise context-paste that earns a working fix.
Challenge
- Challenge 01
Your widget threw this when you clicked send: "TypeError: Cannot read properties of undefined (reading 'content') at handleSend (ChatWidget.svelte:42)". A teammate's bug report only says "the chat thing is broken, it doesn't send." Write the message you'd actually paste to Claude — the exact error, the lines around line 42, what you expected vs what happened, and what you already tried.
- Challenge 02
Then say in one line why the precise paste gets a fix on the first loop and the vague report sends the AI guessing.
- Challenge 03
You get this error stack: "ReferenceError: userStore is not defined at fetchUserProfile (server.ts:18) at GET /api/user (hooks.server.ts:5)". Your first attempt to Claude was "the API is broken." Rewrite your bug report for Claude: include the exact error, the relevant code lines from both files, what was working before (if anything), and what you changed recently. Then paste it in a real prompt and report back what Claude asked for that your first vague report lacked.
- Challenge 04
Write a precise error description for this scenario: Your form validation rule works in the dev server but fails in production. You notice it silently (no error message). For Claude, write out: the validation rule, what input triggers the failure, what the rule should return, what it's actually returning, the difference between your dev and prod environment, and your hypothesis for why the envs differ. Then evaluate: is your description complete enough for Claude to fix it, or are you still guessing?
- Challenge 05
A database query you wrote returns 0 rows when you expect 50. You paste this to Claude: "My query is broken." The AI asks: "What does the query return vs expect? What data did you insert? Have you checked the WHERE clause?" Rewrite your original description to include all three answers without forcing Claude to ask. Then compare: how many lines of code or output had to be pasted?
- Challenge 06
You have a layout bug: a button overlaps text on mobile but not desktop. Write a precise description for Claude that includes: the browser/device details, the exact visual problem (don't say "it's broken"), the CSS rule you suspect, the HTML structure around it, and the breakpoint where it breaks. Then run it through Claude and log: did Claude ask for any of this info again, or could it fix it on the first response?
- Challenge 07
You're importing a component and get "Cannot find module '@components/Button'". Before asking Claude, list: the exact import line, the exact file path where that module should live, whether the file exists, what the actual folder structure is, and the import path you're using. Then write what you'd paste to Claude. Did including the context prevent Claude from asking follow-up questions?
- Challenge 08
A teammate fixed a bug you reported by changing three lines of code, but your error report was vague ("data isn't loading"). You don't understand why their fix worked. Before asking them, write: the exact error you saw, the code that threw it, what data you expected and got, the three lines they changed, and a hypothesis for why the change fixed it. Then ask them: were there any clues in your original error report that would have led you to the fix yourself?