Why do users struggle with prompts? A simple solution before sending
That’s really interesting — I like the structured approach you built, especially the idea of controlling how prompts are handled within the flow.
What I had in mind is slightly different and more from a product/UX perspective:
Instead of generating a single improved prompt within the response, the idea is to present multiple prompt options before sending , each reflecting a different interpretation or level of detail.
For example:
- A concise version
- A more detailed version
- A structured/task-oriented version
The user would then choose the option that best matches their actual intent.
The key idea is not just improving the prompt, but helping the user realize what they actually meant to ask.
In a way, this creates a small “pause moment” before the system responds — where the system tries to understand the intent, and the user actively confirms it. This adds a sense of transparency, control, and mutual alignment between the user and the system, instead of the system just “guessing” and responding.
Your approach already shows there’s real friction here — which is exactly what made me think about this direction.
Curious — do you think having multiple options instead of a single recommendation would be useful in your setup?
Discussion in the ATmosphere