Dictate coding prompts into Cursor on Windows with Voktik.

Cursor's AI works best when you explain the change in full: which file, what's wrong, and what to leave alone. Saying that is often easier than typing it. With Voktik, click in Cursor's chat, hold Ctrl+Win, describe what you want, and let go. Your prompt lands in the box, tidied, for you to check and send.

Voktik types what you say into the box you've clicked in. It doesn't read your code or your screen, and it doesn't write code: Cursor's AI does that, from the prompt you give it.

Dictate a prompt into Cursor, step by step

1. Open Cursor's chat or agent panel and click in its message box.
2. Hold Ctrl+Win and describe what you want.
3. Let go. Your prompt arrives a moment later: ums and ers out, punctuation in, your words kept.
4. Read it, then press Enter to send.

For a longer brief, press Ctrl+Win+Space once and talk hands-free. Ctrl+Alt+P pauses while you think. Press Ctrl+Win+Space again to finish.

The Coding style (Pro)

The Coding style writes file names, paths, commands and code names the way a developer types them:

• Words are only joined into one name when you say how, with "underscore" or "camel case". Everything else stays as ordinary words.
• It never adds a capital to a name or a command, and never adds backticks or other formatting.
• The English around the names is tidied as usual, and it never answers or carries out your prompt.

On Pro, the ready-made Coding rule switches it on for you in Cursor, VS Code and terminals. The bar shows which style each dictation used. If it doesn't say Coding in Cursor, add Cursor to the Coding rule on the Styles page.

On the free plan, your prompt is tidied in your everyday style instead: fillers out, punctuation in.

Your files and functions, spelled right

Add the names you use all the time, such as your project, a component or a function, to your Dictionary: the name as it should appear ("OrderSummary"), and what Voktik typed instead. It's spelled your way every time after.

The free AI and coding word pack adds common names in a click, including Next.js, TypeScript, Tailwind, Supabase, Postgres, GitHub, VS Code and npm.

Snippets for instructions you repeat

If you end most prompts the same way, save that as a snippet:

1. Open Snippets and select Add snippet.
2. Under When you say, type a phrase, for example "my usual rules".
3. Under Voktik types, type the full text, for example: "Only change what I've asked for. Keep the existing style. When you're done, list the files you changed and why."
4. Save.

Now say "fix the login bug in auth dot ts", pause, then "my usual rules", and Voktik types your request with the whole instruction after it. A snippet's text goes in exactly as you saved it. Three snippets are free, and more is Pro. For more ideas, see AI prompts as snippets.

Tips for coding prompts by voice

• Start with where: the file or the feature, then what's wrong, then what should happen.
• Say what not to touch. "Don't change the tests" saves a lot of undoing.
• Read it once before you send. A misheard file name sends the agent to the wrong place.

FAQ

Does Voktik write code by voice?

No. It types your prompt into Cursor's chat, and Cursor's AI writes the code. The Coding style only makes sure file names, commands and code names come out the way you'd type them.

Does Voktik read my code?

No. It doesn't read your files or your screen. To pick the style, it reads the app's name on your PC.

Is the Coding style free?

No, it's a Pro style. Holding the key, hands-free, the dictionary and three snippets are free.

Does it work in other code editors and terminals?

Yes. Voktik types into any text box, and on Pro the Coding rule also covers VS Code, Windows Terminal, Command Prompt, PowerShell and Git Bash. In a terminal, a dictation always goes in as one line, so it never runs a command by itself.