Dictating prompts into Claude Code, Cursor, and the terminal. Real workflows from daily use.
Claude Code can look at a screenshot of a UI and build it, or look at a screenshot of a bug and fix it. Here is the workflow I actually use, including the prompts that work.
You copied a screenshot, pressed Ctrl+V in Claude Code, and got no image found in clipboard. The image is right there. Here is why Claude Code can't see it and the fixes, ranked.
There are four ways to get an image into Claude Code, and which one works depends entirely on your terminal. Here is the full map: paste, drag, file paths, and the one-hotkey option.
Claude Code takes natural-language prompts all day, and typing them is the bottleneck. Here's how I dictate prompts straight into Claude Code with local, GPU-fast voice-to-text.
I write most of my prompts by voice now, into Claude Code, Cursor, the terminal. Here's the actual setup, the hotkeys, and why it turned out faster than typing.
Everyone talks about 150 WPM vs 40 WPM. Speed isn't the real win. The real win is that spoken prompts are actually better than typed ones.
Terminal emulators like Hyper, Wezterm, and Windows Terminal can't paste images into Claude Code. Invoke's screenshot-to-path feature fixes that with one hotkey.
I dictate thousands of prompts a month. Every transcription tool I tried was either too slow, too expensive, or too dumb. So I built my own.
You can dictate prompts directly into Cursor's chat and composer. Here's how to set it up with local Whisper transcription.
Download Invoke and start dictating in under a minute. Free for 7 days.