Learn

What is the difference between a prompt and a command?

A command should do exactly one thing every time. A prompt can produce a different result on different days, which is fine for drafting and dangerous for anything irreversible.

What matters here

  • Commands are deterministic, prompts are probabilistic
  • Commands belong in buttons, prompts in conversation
  • Anything destructive should be a command or confirmed
  • Prompts are better for drafting and restructuring
  • Mixing them hides which one you just ran

Where each belongs

Marking a task done is a command: one click, one outcome. Write a summary of this project is a prompt, because the output legitimately varies. Designing the interface around that split prevents most surprises.

The confirmation rule

Anything that deletes or sends should require explicit confirmation when triggered by a prompt. The model can propose a delete; it should not perform one because a sentence sounded like permission.

Why wording matters less than you think

People spend a lot of time on prompt phrasing for actions that would be better as a button. If the same instruction is typed every week, it should become a command, not a better prompt.

Frequently asked questions

Keep reading

Turn talk into a plan

Capture a thought in plain language and let Prysm Note shape it into tasks and a timeline.

Try Prysm Note

Disclaimer

This page is general information, not professional, legal, financial or medical advice. It describes common ways of working and how Prysm Note approaches them. Software changes over time, so details may differ from what you see in the product. Any product, company or brand names that appear are the property of their respective owners and are used only for identification. We do not claim any endorsement or affiliation. Where we compare approaches, we aim to describe each one honestly, including where a different approach may suit you better. Try the tools that matter to you and judge for yourself.