A good coding prompt is a compact project brief. It identifies the user outcome, current state, constraints, and evidence that will prove the change works.
Ask for the smallest complete flow
A thin end-to-end feature is more useful than several disconnected components. Ask the AI to name assumptions and exclude later ideas from the first version.
Ask for evidence, not confidence
Require exact test steps, expected results, and a summary of changed files. When debugging, provide the error and reproduction before requesting a fix.
End with a review pass
Review correctness, security, accessibility, responsive behavior, empty states, and unnecessary complexity before moving to the next feature.