The same words may not produce the same result
'Make a sign-up screen' says less than 'Show email errors immediately at a 390px phone width.' When you revise a request, note what condition you added and why. That gives your next task a useful starting point.
A prompt is not a guaranteed recipe. A different codebase, model, date, or input can change the result. The reusable asset is the wording together with the outcome you checked.
Record three things with every revision
If you changed 'summarize this table' to 'do not estimate values; include source row numbers,' record why evidence mattered. Keep passwords, keys, and unnecessary personal details out of saved examples.
- Write one sentence about the request's purpose and where it will be used.
- Note the constraint you added or the ambiguity you removed.
- Link the artifact produced by that version and the strengths and weaknesses you checked.
Read the prompt beside its result
Wellnote groups prompts by session, keeps their versions, and can link a prompt to a specific artifact version. Before reusing it, read the original purpose and observed result rather than copying the text alone.