For precise edits, say what to keep
Make each revision a deliberate refinement, not a fresh start.
Set boundaries for the edit
When a work is already close to your idea, the most valuable next instruction may be what not to change. For example: “Keep the homepage colors, title and images. Only adjust the bottom navigation; open course details on tap and preserve my position when I return.” This specifies what to preserve, what to change and how it should behave.
Test one complete action at a time
Do not just check that a button exists. Follow a real path: open a list, select an item, view details and return. Record what happens, then describe what you expected. Screenshots clarify visual issues; words should identify the action and device.
Use versions as a shared reference
When comparing versions, identify the one to build on. If something regresses, find the last correct version and request a narrow change. Conversation reduces repeated explanations, but important constraints are worth restating. This is easier to verify than “improve everything again.”