Goal
Design a composer that makes input scope and active capabilities understandable before submission.
Step-by-step
- Start with the primary task.
- expose only useful modes.
- preview attachments.
- test incompatible inputs and keyboard behavior.
Worked scenario
Switch from a local document question to web research without losing the draft.
Write down the current behavior, the intended change, and the evidence you would need before deciding it worked. Use synthetic or anonymized material for exploration.
Acceptance check
Users know what context and tool the next request will use.
Common failure
A convincing artifact can hide untested assumptions. Keep an explicit list of unknowns and test the highest-consequence transition before expanding the work.
Next step
Apply the guide to one bounded task, review the evidence, and adjust the approach. The linked reference is a separate publication; this guide is Knoveya's independent treatment of the topic.