Dictation changes filenames and code identifiers
Whisper Key supports a voice-input workflow when paired with appropriate transcription software. Filenames and code identifiers are a demanding part of that workflow because they often contain unusual spelling, punctuation or capitalisation. A recogniser can produce a plausible ordinary phrase where you intended an exact symbol. Keep those exact references anchored to the source rather than trusting how natural the sentence sounds.
Which parts of the prompt require exact matching?
Identify filenames, function names, command flags, branch names and other tokens that must match existing material. Separate them from the explanatory prose you can comfortably dictate. A good description of the task does not repair a path that points to the wrong file.
Copy exact identifiers from the relevant source when appropriate, or type them deliberately into the reviewed draft. Confirm the surrounding context so you do not copy a similarly named symbol from another project. Avoid dictating private credentials as a shortcut for transferring them between tools.
Can custom vocabulary reduce repeated corrections?
If your transcription software supports a vocabulary or correction feature, follow its documented process for frequently used project terms. Test the result in a harmless phrase and note whether punctuation and case are preserved. Support varies by tool and language, so do not assume a microphone or keypad adds this feature itself.
A vocabulary entry is an aid, not a guarantee that every occurrence is correct. Similar-sounding terms and changing sentence context can still produce different text. Keep the exact identifier visible during review instead of treating a successful test as permanent proof of accuracy.
How should voice and keyboard input be combined?
Use speech for the problem, rationale and expected behaviour, then insert exact tokens during editing. For example, describe what a function should do and add its precise name from the source afterward. This reduces the need to speak every punctuation mark while preserving a clear reference.
Check that manual edits do not accidentally join words or remove spacing around a path. If the tool continues listening while you type, understand its documented behaviour and stop recording when necessary. A mixed-input draft still needs a final pass as one coherent instruction.
What should you inspect before sending the prompt?
Compare each exact reference with the intended file or symbol, including capitalisation and punctuation where relevant. Verify that the task still points to the correct project and that no recognised word changed a condition such as do not. Keep uncertain references out of automatic execution. The Whisper Key product page describes the voice-input device; identifier accuracy is a transcription and review responsibility in the full setup.