Writing Prompts That Land on the First Try

Thu, 22 Jan 2026 14:15:00 +0000

After using Claude Code for a while, you’ll notice most failed sessions trace back to your prompt, not the model. Claude can infer intent, but you can’t expect it to read your mind.

Lock down the scope

“Optimize this code” — what comes out is a lottery. Optimize for what? Performance? Readability? Removing dead code?

A good prompt names the file, the scenario, and how to verify:

Write an edge-case test for logged-out users in src/auth.ts. No mocks.

The tighter the scope, the more predictable the output. Vague prompts only make sense when you actually want the agent’s opinion — “what would you improve in this file” is fine, but keep it scoped so it doesn’t wander into hundreds of files.

Prompt on Time Friend

Writing Prompts That Land on the First Try

Lock down the scope