title: "Anti-Pattern: Over-Prompting" last_updated: 2026-03-21 status: proven difficulty: beginner prerequisites:

• Basic experience with any agentic coding tool

Over-Prompting

What It Looks Like

You write a 300-word prompt explaining exactly how to add a field to a form, describing HTML structure, CSS classes, state management approach, validation logic, and error message wording -- when the agent already knows your framework.

Why Developers Do This

Habits from working with earlier, less capable models. Fear that the agent will get it wrong without exhaustive detail. A belief that more words equals more precision.

Why It Fails

Long prompts burn context tokens on instructions instead of reserving them for code. Worse, conflicting details buried in walls of text confuse the agent. It tries to honor every micro-instruction and produces awkward, over-constrained code that satisfies the letter of your prompt but misses the spirit.

The Symptoms

• Prompts longer than the code you want generated
• Agent output feels rigid and over-literal
• You spend more time writing prompts than reviewing output
• Small changes require rewriting the entire prompt

What to Do Instead

State the goal and constraints. Let the agent figure out the implementation.

# Wrong
claude "Create a React component called EmailField using a controlled input
with type='email', a useState hook named emailValue initialized to empty
string, an onChange handler that calls setEmailValue with e.target.value,
and a regex validation on blur using /^[^\s@]+@[^\s@]+\.[^\s@]+$/..."

# Right
claude "Add an email input field to the signup form with client-side validation"

If the output misses something, give targeted follow-up feedback rather than front-loading every detail.