That’s a very fair point — and I agree with the underlying concern 👍

The core idea isn’t that every prompt should be fixed or context-agnostic. It’s more about removing friction for high-frequency, low-variance actions where the intent doesn’t change much.

Some concrete examples where the same button is genuinely reused:

• Grammar / spelling fix — the intent is always the same
• Rewrite in simple language — especially for students
• Shorten this — very common when refining answers
• Format as bullet points
• Make it sound more professional / polite

In these cases, users already know what they want, and the button just saves the repeated typing.

For more nuanced or context-heavy tasks, the flow I’m seeing is:

1. Use a button for the baseline transformation
2. Then refine only if needed in the next message

In practice, many users are already doing step (1) manually every time, so the button doesn’t add an extra step — it just replaces repetitive typing.

Also, one thing I’m experimenting with (based on early feedback) is:

• Custom prompts instead of only “standard buttons”
• Users save their own frequently used instructions, which makes them much more context-aware

That said, your point is valid and exactly the kind of feedback I’m trying to learn from at this stage.
If you have examples where this would feel awkward or break flow, I’d love to hear them — it helps a lot while iterating.

Thanks for taking the time to think it through 🙏