Vibe coding moves the work from typing code to describing it. The keyboard time does not disappear, it changes shape: prompts, implementation notes, bug reports, PR descriptions, acceptance criteria. That is prose, and prose is what dictation is good at.
TL;DR
- Vibe coding is requirements, prompts, and review, not just code generation.
- Dictate the prose: what should happen, edge cases, acceptance criteria, why.
- The loop is voice, generate, test, review checklist.
What “vibe coding” means
Simon Willison coined the current usage and is careful about a distinction most coverage drops: not all AI-assisted programming is vibe coding. Vibe coding is accepting the generated code without reading it closely. Reviewing what the model wrote is something else (Willison, 2025).
That distinction is the whole reason the review step below exists.
Why vibe coding pairs well with dictation
The writing load in a vibe-coding session lands in five places: prompts, implementation notes, bug reports, PR descriptions, and tickets. None of it is syntax. All of it is faster spoken than typed, and all of it still needs a keyboard pass for identifiers and links.
The pairing matters most if you write many tickets in Linear or Jira, many PR descriptions in GitHub, or if you are managing wrist pain and want the keystroke count down.
A Mac workflow that works (voice → generate → verify)
Step 1: Dictate requirements (not code)
Before you prompt, dictate these:
- what the feature should do (1 paragraph)
- what it should not do (scope)
- edge cases (bullets)
- acceptance criteria (checklist)
On macOS you can start with built-in Dictation (Apple Dictation guide).
If you do this daily, a hold-to-dictate hotkey is easier to stick with: /voice-typing-mac
Step 2: Paste into Cursor/VS Code and generate
Use your editor’s AI features to draft the code. Treat the output as a first draft, which is what the checklist in step 3 is for.
Related how-tos:
- Cursor: /how-to/cursor-mac-dictation
- VS Code: /how-to/vscode-mac-dictation
Step 3: Run the “vibe coding review checklist”
Dictation makes generation faster. Review makes it safe.
Checklist:
- Does this change have tests?
- Are error cases handled?
- Are inputs validated?
- Is auth/permissions correct?
- Did we leak secrets/log PII?
- Is the code readable and maintainable?
Step 4: Dictate the PR description (so reviewers trust it)
PRs are mostly explanation:
- what changed
- why
- how to test
Dictate the prose, type the identifiers: /how-to/github-pull-request-mac-dictation
Where Voice Type fits (product)
Voice Type is on-device voice typing for macOS. The workflow is simple:
- hold a hotkey
- speak
- release to finalize
It’s not “voice code.” It’s “voice the parts that are prose,” especially when you’re moving between editors, browsers, and ticket tools.
Keep going
- Dictation in GitHub Issues: /how-to/github-issues-mac-dictation
- Dictation in Linear: /how-to/linear-mac-dictation
- Dictation in Jira: /how-to/jira-mac-dictation
- RSI workflow: /solutions/rsi
Sources (definitions + references)
- “Not all AI-assisted programming is vibe coding …” (context + critique): Simon Willison, 2025
- Explainer: Cloudflare: “What is vibe coding?”
- Mainstream overview: PCMag: “Vibe Coding Is Everywhere…”
- Apple Dictation: Use Dictation on Mac