Dictate Your Prompts Instead of Typing Them
If you're typing every prompt to Claude Code with your keyboard, you're bottlenecking the fastest part of the workflow.
Voice dictation streams your words directly into any input field as you speak. No copy-paste, no window-switching, no lag. On macOS you can enable it in System Settings and trigger it with a double-tap of the Fn key. Windows has a built-in shortcut too:
# macOS: enable dictation
# System Settings > Keyboard > Dictation > On
# Then double-tap Fn to start dictating into any field
# Windows: Win + H to open voice typing
# Works in the terminal, in any input field
The shift is subtle but real. Typing a long, complex prompt takes concentration and slows you down. Speaking it is faster and often more natural, especially for detailed instructions like "refactor this function to use dependency injection, add a docblock, and extract the validation logic into its own private method."
Works in the Claude Code terminal input, in IDE chat panels, anywhere you'd normally type a prompt. You can dictate multi-line instructions with punctuation commands ("new line", "period") or just free-form and clean it up.
The keyboard becomes optional. Your ideas flow into Claude Code at speaking speed.
If you find yourself dreading long prompts, try speaking them instead.
via @superscribeio
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.