Prompt for Code That Works

Describe what you want, what already exists and what must not change. Paste the exact error message when something breaks, not your guess about it. Ask the tool to explain what it changed.

Habits that help

• Start each request with the goal, then the constraint.
• Tell it which files it may edit.
• Ask for the smallest change that works.
• Save a working version before every big request.

Worked example

Sam writes, 'Goal: let a user mark a chore done. Existing: a board page in board.tsx. Don't change the layout. Only edit board.tsx and the data file. Smallest change that works.' The tool changes eight lines instead of rewriting the page.

Common mistakes

• Pasting your guess about a bug instead of the actual error.
• Not naming which files may change.
• Accepting large rewrites you can't review.

Exercise

Write one prompt with a goal, the existing state, a constraint and a file list. Run it.