A prompt is a contract between the user's choices, the system's instructions, and past interactions. Any change to one part needs checking all three.
By Pawan Nayar · from the LLOS AI Learning record
A prompt is a contract between the user's choices, the system's instructions, and past interactions.
Any change to one part needs checking all three.
When changing a prompt, check three things. First, ensure every user choice leads to a specific instruction, not a general one. Second, make sure system instructions describe feelings or methods, not exact words. Third, confirm that past settings and outputs store and restore new values correctly. This prevents unexpected results.
A developer changes a prompt to add a new 'mood' option. The developer must check that the user interface sends the new mood, the server creates a unique instruction for it, and the system saves this mood in the user's history. If not, the user might pick the new mood but get the same output as an old one.
More from the same record, pulled by shared topic — not written new for this page.
The 'Three-Party Contract' means a prompt connects three things. It connects the user's choices in the interface.
Realistic diagrams often have parts that overlap. For example, a bicycle bell sits on a handlebar.
A developer must put important content at the top of the page. This content should be visible without scrolling.
A developer must place key content in the first viewport. This includes a badge, title, subtitle, search bar, and themes.
A prompt is a contract between the user's choices, the system's instructions, and past interactions. Any change to one part needs checking all three.