Developer AI Prompt Examples for Voice Dictation
Quick answer: The best prompts to dictate are the ones that need context: debugging requests, implementation briefs, code reviews, terminal-agent instructions, ticket details, and AI prompts that benefit from constraints and verification steps.
What happens after install
See the demo- Focus any Mac text field.Cursor, ChatGPT, Slack, email, docs, terminals, browser forms, and more.
- Hold the shortcut and speak.Use Fn/Globe or a custom hotkey only while you are talking.
- Release to paste.The transcript appears in the active app instead of a separate dictation workspace.
- Review before sending.Hold to Talk never auto-submits prompts, messages, emails, or commands.
Copyable prompt examples
Use these as starting points. Dictate them in your own words, then review the pasted text before sending.
Debug a stuck checkout flow
When you want Cursor to inspect a bug with enough context to avoid a vague first pass.
Please debug the checkout flow. The upgrade button stays disabled after Stripe returns success. Inspect the billing state reducer, webhook handler, and checkout success page. Find the root cause before changing UI copy. Add a regression test for the broken state and summarize the exact files you changed.How to dictate into Cursor
Ship a scoped implementation
When you want a terminal coding agent to make a concrete change without broad refactors.
Implement the smallest version of this feature. Read the existing patterns first, keep the change scoped to the relevant files, and do not refactor unrelated code. After the edit, run the targeted tests or build checks that prove the behavior works, then summarize any risk that remains.How to dictate into Claude Code
Ask for root-cause analysis before code
When the task could be caused by state, analytics, API, or UI behavior and you do not want a surface-level patch.
Find the root cause before editing. Trace the user action from the UI event through the server route, database query, and report output. Show the evidence for the failure, then make the smallest code change that fixes it. Add or update a regression test and run the relevant verification command.How to dictate into Codex
Improve a landing page section
When you need more specific copy feedback than a short typed prompt would usually contain.
I am writing a landing page section for a Mac dictation app. The audience is developers who use Cursor, Claude Code, ChatGPT, terminals, and Slack all day. Make the copy practical and specific, not hypey. Emphasize that the app pastes into the active field, keeps the user reviewing before send, and has zero server-side audio retention. Give me three headline options and one tight section outline.Dictation for ChatGPT prompts
Create a request-level analytics report
When you need an agent to build reporting that includes crawler and no-JS traffic.
Add a reusable request analytics report. It should read the sitemap, query Cloudflare request analytics by path, show total requests, visits, search crawler requests, AI crawler requests, and mobile requests. It should fail clearly if the token cannot access the zone. Add the command to package scripts and document the expected output.Terminal prompt dictation
Write a pull request review
When you want a review comment that explains the behavioral risk instead of just saying something is wrong.
This change looks like it fixes the immediate UI state, but I think it misses the backend status transition. Please add a test where the payment succeeds, the webhook is delayed, and the page refreshes before the subscription row is updated. Without that test, this could regress for slow webhook delivery.Dictate GitHub reviews
File a bug with acceptance criteria
When you need a ticket that includes reproduction steps, expected behavior, and the verification path.
Bug report: new users from the SEO pages are not showing source attribution in the activation funnel. Steps to reproduce: open a tracked SEO URL, click download, complete setup, then check the dashboard. Expected result: the original source and page path appear in the funnel report. Please trace the site event, download click, app activation event, and D1 query before closing this.Dictate Linear and Jira tickets
Send a precise status update
When you need a short update that includes what shipped, what changed, and what remains unknown.
Quick update: I added the new prompt library page, linked it from the homepage and examples page, regenerated the sitemap and LLM files, and submitted the URL through IndexNow. The crawler/request layer should show it first; real browser traffic will still depend on distribution.Voice dictation examples
Reply to product feedback
When you want to acknowledge feedback and state the next concrete action without overexplaining.
Thanks for the detailed notes. I agree that the developer workflow is the clearest positioning right now. I am going to keep the homepage broad, but push the SEO pages, examples, and external posts toward Cursor, Claude Code, terminal agents, GitHub reviews, and AI prompts. I will check crawler and browser traffic again after the next deploy.Developer dictation workflows
Turn notes into an implementation brief
When you have scattered context and want Copilot, chat, or an editor agent to start from a clear brief.
Turn these notes into a concrete implementation brief for this repo. The problem is that new SEO pages have crawler traffic but no first-party browser attribution. Include the suspected files, the data flow to inspect, the constraints, the tests to run, and the exact acceptance criteria. Do not propose broad rewrites.How to dictate into VS Code
Generate tests before changing code
When the behavior is easy to accidentally fix only in the happy path.
Before changing code, propose the regression tests that should fail for this bug. Cover the normal case, the delayed event case, and the missing attribution case. After the tests are clear, make the smallest code change that passes them and explain which path each test protects.Dictate GitHub Copilot prompts
Plan a multi-file change
When a coding task spans UI, server, database, and generated reports.
Before editing, map the files this change probably touches and the data flow between them. Identify the smallest implementation path, the tests that should prove it, and any generated files that must be regenerated instead of edited by hand. Then wait for me to confirm the plan.How to dictate into Cursor
Debug a failing integration test
When the failure might come from test setup, state leakage, async timing, or a real regression.
Investigate this failing integration test. First explain what behavior the test is supposed to protect. Then inspect the recent code path, fixtures, async waits, and cleanup behavior. Find the root cause before changing assertions, and only update the test if the product behavior is still correct.How to dictate into Claude Code
Make a migration safe
When schema, backfill, or analytics changes need careful rollout and verification.
Review this migration plan for safety. Check whether existing rows, delayed events, retries, and old app versions still work. Add the smallest migration or compatibility change needed, then show the rollback risk, verification query, and the exact command to confirm the new data is being written.How to dictate into Codex
Review a risky shell command
When a command could touch production, credentials, generated files, or local app state.
Before running this command, explain what it will read, write, delete, deploy, or submit. Identify any safer dry-run or read-only check. If the command is still appropriate, run the least risky version first and summarize the evidence before making any irreversible change.Terminal prompt dictation
Write a review that asks for evidence
When a pull request claims a behavior is fixed but does not prove the edge case.
Write a direct but constructive pull request review. Say which user-facing behavior is still unproven, name the missing edge case, and ask for either a regression test or a short explanation of why the existing test covers it. Keep the comment specific to this change.Dictate GitHub reviews
Turn a vague bug into a useful ticket
When a bug report needs reproduction steps, expected behavior, and acceptance criteria.
Turn this rough bug report into a ticket a developer can act on. Include the user impact, exact reproduction steps, expected result, actual result, likely code areas to inspect, acceptance criteria, and the verification command or dashboard query that should prove the fix.Dictate Linear and Jira tickets
Create a targeted test matrix
When a fix crosses app state, permissions, browser flow, or analytics attribution.
Create a compact test matrix for this change. Cover the normal path, one permission-denied path, one stale-state path, one delayed-event path, and one analytics attribution path. For each row, list the setup, action, expected result, and the narrowest command or manual check to verify it.How to dictate into VS Code
Post an incident triage update
When teammates need a useful status update without a long incident write-up.
Write a short incident triage update. Include what is affected, what is not affected, the current hypothesis, the next diagnostic step, the owner, and when I will update the channel again. Avoid certainty until the root cause is confirmed.Dictate Slack messages
Reply to a skeptical prospect
When someone asks whether a simple Mac dictation app is different from broader AI writing tools.
Draft a concise reply to a skeptical prospect. Acknowledge that many dictation tools exist, then explain the narrow workflow: hold a shortcut, speak, release, paste into the active Mac app, and review before sending. Mention zero server-side audio retention, the free plan, and when a different tool would be better.Developer voice-to-text guide
Draft release notes from changes
When a changelog needs to explain user impact instead of listing commits.
Turn these changes into release notes. Group them by user-facing improvements, reliability fixes, and developer or operations changes. Keep the language plain, mention any behavior users should verify after updating, and do not overstate performance or privacy claims.How to dictate into Claude
Hand off a self-contained agent task
When you want an autonomous coding agent to work from a complete task packet instead of a loose ask.
Please take this as a self-contained implementation task. Goal: improve the marketing report so it separates human browser views from crawler requests. Context: the status snapshot, owned indexing follow-up, SEO watchlist, and site attribution report already exist. Constraints: do not submit external forms, do not mark tracker rows, and keep existing report names stable. Verification: run the targeted marketing scripts and summarize the before and after counts.How to dictate into Devin Desktop
Narrow a refactor request
When you want Cascade or another editor agent to improve code without turning the task into a broad cleanup.
Refactor only the report formatting in this file. Keep the data model, command line flags, output filenames, and generated markdown headings unchanged. The goal is easier reading, not new behavior. After editing, run the existing report command and a diff check, then list anything you intentionally left alone.How to dictate into Windsurf
Investigate a failing command safely
When you want a terminal agent to diagnose a command before running anything risky.
Investigate why this command is failing, but do not run destructive commands. First explain what the command is expected to do, what files or environment variables it touches, and which read-only checks you will run. Then run the checks, identify the root cause, and propose the smallest safe fix.How to dictate into Warp
Ask the Agent Panel for a local fix
When you want a concise editor-agent request with enough context to avoid unrelated edits.
Use the current file and nearby tests to fix this bug locally. Keep the public API unchanged, preserve existing naming style, and do not edit generated files by hand. After the fix, run the narrowest relevant test and tell me the exact command and result.How to dictate into Zed AI
Summarize launch metrics
When you want a compact readout from analytics, crawler, and distribution notes.
Summarize this launch status in five bullets. Separate real browser traffic from crawler requests, call out whether any source-attributed views exist, list the next approval-gated action, and suggest one owned-site action that can happen without external posting.How to dictate into Raycast AI
Research positioning without overclaiming
When you need market research or competitor context but want a cautious source-backed answer.
Research Mac dictation apps for developers and AI prompts. Focus on workflow differences, privacy claims, pricing pages, and use cases. Cite sources for every comparison, separate confirmed facts from interpretation, and do not claim that one app is best unless the criteria are explicit.How to dictate into Perplexity
Rewrite a launch note for developers
When a social or community post needs to sound practical instead of promotional.
Rewrite this launch note for developers. Keep it specific and low-hype. Mention the hold-to-talk workflow, dictating into Cursor, Claude Code, Codex, terminals, GitHub reviews, and Slack, plus the review-before-send behavior. End with one concrete question that invites useful feedback without asking for likes or upvotes.How to dictate into Claude
How to adapt them
- Name the app or workflow you are using.
- Say the goal and the current context.
- Add constraints, risks, files, examples, or what not to change.
- Ask for a concrete verification step before the work is considered done.
Developer workflow guides
Use these guides when a prompt becomes a coding task, issue, review, terminal instruction, or ticket handoff.
Developer workflow guides
Specific guides for the developer dictation workflows that need the most context.
- Best Voice-to-Text App for Developers on MacHow to choose a Mac dictation app for coding prompts, reviews, tickets, and docs.
- Best Dictation App for AI Coding AgentsA buying guide for Cursor, Claude Code, Codex, Windsurf, Warp, Zed, and Copilot prompt workflows.
- How to Dictate into CursorSpeak prompts into Cursor chat, Composer, editor buffers, and terminal panes.
- How to Dictate into Claude CodeSpeak terminal-agent instructions while keeping review-before-run control.
- Voice Dictation for Terminal WorkflowsGive terminal agents goals, constraints, commands to run, and commands to avoid.
- How to Dictate GitHub Issues and PR ReviewsDictate GitHub issues, pull request descriptions, and review comments with enough context.
- Voice Dictation for Code Review CommentsSpeak review feedback with the observation, risk, requested change, and expected test.
- How to Dictate into Linear and JiraDraft bug reports, acceptance criteria, triage notes, and ticket handoffs by voice.
FAQ
What makes a good dictated prompt?
A good dictated prompt includes the goal, context, constraints, examples, risks, and verification steps. Speaking makes those details faster to include than typing.
Should dictated prompts be sent automatically?
No. Hold to Talk pastes the prompt into the active field so the user can review, edit, and decide when to send it.
Where can you use these prompt examples?
Use them in Cursor, Claude Code, Codex, Devin Desktop, Windsurf, Warp, Zed, ChatGPT, Claude, Gemini, Perplexity, Raycast AI, terminal agents, GitHub, Linear, Jira, Slack, email, and any Mac app with a focused text field.
Try Hold to Talk on Mac. Start with the free plan, then upgrade only if it fits your daily workflow.
Download Hold to Talk Watch the 8-second demo