Why prompts are where voice pays off
- Good prompts have parts. Role, goal, context, constraints and output format. Typing all five feels like homework, so people send one line and get a generic answer.
- The same structure, many tools. You might write similar prompts for a chat assistant, a research tool and a coding assistant. A habit that works everywhere beats learning each tool's own voice feature.
- Technical words. Function names, file names, library names and acronyms are easy to say and easy to get wrong.
- Iteration. Prompting is trial and error. Each round adds another paragraph to type.
A spoken prompt framework you can reuse
Say the five parts in order. Labels are optional, but saying them helps you not skip one.
- Role: "You are a senior support lead."
- Goal: "Write a reply template for customers asking to move their delivery date."
- Context: "Deliveries can move up to two days before dispatch, most requests come in on Mondays, and customers are often in a hurry."
- Constraints: "Under 120 words, no legal language, offer a call."
- Output format: "Give me two versions, one formal and one friendly."
That's easy to say and a chore to type.
How to dictate AI prompts with SayDart in 3 steps
- Click into the AI tool's prompt box. A chat window, a research tool or the AI chat panel in your code editor.
- Press your voice shortcut and speak the framework. Right Alt on Windows, Right Option on macOS, Left Ctrl + Left Alt + Space on Linux. Watch the transcript preview in the capsule, especially for technical terms.
- Transform if needed, then send. Read the prompt. Optionally select it, open Transforms and choose Create an AI prompt. Then send it from the AI tool.
SayDart features for AI prompts — Transforms: Create an AI prompt
Rambled? Select the text and run Create an AI prompt: one step, and you get a clean, structured prompt. Want your own format, such as role, goal, context, constraints and output format? Save it as a New transform with your own Instructions.
SayDart features for AI prompts — Style > Cleanup > Original for exact wording
When the prompt contains quoted text, exact error messages or code identifiers, choose Original in Style > Cleanup and keep the raw transcript.
SayDart features for AI prompts — Dictionary for technical terms
Add function names, framework names, product terms and acronyms you use in prompts. They are the words a voice tool is most likely to miss.
SayDart features for AI prompts — History as a prompt library
History keeps your dictations on your computer with the original transcript and saved result versions. Reuse a prompt that worked last week instead of rebuilding it.
SayDart features for AI prompts — Voice translation
Speak Chinese, get an English prompt. Press your Translation shortcut and talk: 30 languages in, 303 out.
SayDart features for AI prompts — Snippets
Say a short trigger phrase and your standing instruction drops in, word for word, every time.
Example: a coding prompt in an editor's AI chat
You say: "Refactor the parse invoice function so it handles missing dates. Keep the public signature the same, add a unit test for the empty file case, and explain the change in two sentences."
Add "parseInvoice" to your Dictionary before you start, and glance at the transcript preview to check how the function name came out before you send.
For ChatGPT-specific tips, such as follow-ups and long context, see dictation for ChatGPT. Most AI work happens on a PC? Read how to voice type on Windows.
Explain a code change to Cursor or Codex
Describe the behavior and scope. For example: “The settings menu stays open when I click outside it. Propose the smallest fix, preserve shortcuts and explain which files you would change before editing.”
Dictate into the agent's chat box, and paste exact paths, errors and identifiers.
Dictating coding prompts and requirements to AI agents
Coding agents such as Cursor, Claude Code and Codex act on what you give them. Spoken, a request naturally carries the context that gets cut when you type: what you saw, what you already tried and what must stay as it is. Use this order for a coding request; saying the labels out loud is optional.
- Goal: the change in one sentence. "Make the export button respect the active filters."
- Context: where it lives and what happens now. "It's on the reports page. Right now it exports every row."
- Constraints: what must not change. "Don't change the CSV columns, and don't add a dependency."
- Done when: how you will check it. "Add a test that exports a filtered list. Existing tests still pass."
- Ask for a plan first: "Tell me which files you will change before editing."
What to say and what to paste
- Say the intent, the reasoning and the trade-offs. That is where voice saves the most typing.
- Paste exact code, file paths, error messages, logs and stack traces. Do not read them out.
- Add files with your coding tool's own @ references, then dictate the prose around them.
- Read the prompt once before you send it. Check names, numbers and every "don't".
Turn a spoken ramble into a clear agent request
Speak freely, then tidy up. Select the text and run Create an AI prompt in Transforms. To make your own version, open Transforms, choose New transform and write Instructions such as: "Rewrite as a coding task with Goal, Context, Constraints and Done when. Keep every file name, number and negation exactly as spoken."
When you need your exact words, choose Original in Style > Cleanup. Auto cleanup removes filler words and tidies punctuation.
Turn on Settings > Voice & translation > Live transcription display to watch the transcript above the capsule while you talk.
Reuse what works: Snippets, History and Dictionary
- Snippets: save standing instructions you add to many coding requests, such as "Explain the plan before editing and keep the public API unchanged."
- History: find a prompt that worked last week and copy it into a new chat.
- Dictionary: add repository, framework and service names once, and they're in your dictionary on every computer you sign in to, so SayDart writes them your way. Import a whole list with More actions > Import terms.
Three spoken examples
- Bug fix: "Users get logged out after editing their profile. Expected: they stay signed in. Look at how the session is refreshed after the save. Don't change the cookie settings. Add a test for the profile save, and explain the cause before you fix it."
- New feature: "Add a dark mode toggle to the settings page. Use the existing theme variables, remember the choice per user, and don't change the default theme. Done when the toggle works after a reload."
- Refactor: "Split the order service into smaller functions without changing its behavior. Keep the public methods and their names. All existing tests must pass. Show me the plan first."
For Claude Code or Codex in a terminal, dictate into a notes field or chat box, review, then paste into the prompt. More on developer workflows: voice dictation for vibe coding, dictation for Cursor and the best dictation apps for vibe coding.
Pricing
SayDart is free every 7 days. Pro is unlimited for $8.25/month, billed yearly ($99), or $12 month to month. Prices exclude tax.
Comparing desktop voice tools for prompting? See SayDart vs Wispr Flow.
Say your next prompt in five parts
Open your AI tool, hold your voice shortcut and say the role, goal, context, constraints and output format.