1. A paraphrase drops the line that mattered
People summarize to be helpful. The summary is where the clue was. “The test failed” is not the failure. The failure is the twenty lines above that sentence, including the file name and the value that was wrong.
The same is true of the code. “Somewhere in the invoice area” sends Claude hunting. The file, or a screenshot of the screen you mean, ends the hunt.
2. The file, the error, and one pattern
Three inputs cover most ordinary tasks. Point at the real file. Paste the real error, the full stack, the log, or the failing test output. Show one existing thing and say “follow this.”
For a screen, a screenshot or a mock beats a paragraph about spacing. Pointing beats describing. For a bug, the log beats your theory of the log. You can still say what you think. Label it as your theory, so Claude does not treat it as a fact it already checked.
The invoice example from the previous page is the shape. Attach the orders-page button, paste the failing test output in full, and say the API stays. A second sentence that restates the same three things in grander words does not add information. It spends the window.
3. Say the outcome, the stack, and the non-goals
State what you want, which conventions to follow, and what not to touch. Non-goals are part of the brief. “Do not change the API” is a non-goal. “Make it pop” is not a goal.
Voice dictation is fine for a context dump, if you are somewhere you can talk. It is a poor way to produce the final sentence a customer will read. Talking does help you challenge the first proposal instead of accepting it.
4. Let it improve the request before it builds
Ask: “Rewrite this request so the result would be better, and ask me what is missing. Do not edit yet.” The questions are the spec you skipped. Answer them. Then let it build.
Give it something concrete to observe when you can: the current screen, a fixture, a log, a spec. Memory of how the screen “usually” looks is how two people describe two different screens.
5. What to try next
On the next bug, paste the full error and the file it names before you add your theory. On the next screen, attach the picture and name the existing component to copy.
The facts that should not have to be repeated every session belong in a short project memory file.