Coding Prompt Style: Organize Dictated Requirements for Your Editor

A useful coding handoff keeps the requested behavior and technical details together. Coding Prompt style organizes dictated requirements and any code you actually speak, using formatting preferences you choose in its advanced settings.

Choose Coding Prompt for dictated development text and set its programming language and output preferences in Rewrite. Choose Vibe coding when you want to organize a spoken goal, requested changes, requirements, and constraints into a brief for your coding tool. Dictate the relevant context, then review the draft before using it.

Configure the writing stage

• In Styles, select Coding Prompt and open its gear for Rewrite.
• Check Speech transcription, then choose an available Text formatting model. The fresh style has no formatter selected, so No formatting will not run the AI organization stage.
• Under Output Format, inspect Language, Include comments, Format Style and Code Blocks.
• Select the style and use Today's Start listening for a small test, then stop and review the result.
• For global shortcut dictation into another app, link the destination through Linked apps or Linked websites, or set Default style to Coding Prompt for unmatched destinations. Linked matches take priority over the default.

The initial style is linked to Cursor and VS Code. Inspect your own links before relying on that behavior: an existing profile may have different assignments. Selecting a style card alone does not determine the style chosen when global recording starts.

Understand the options before changing them

Language describes the programming-language preference for the formatted output, with Auto-detect as its initial choice. It is separate from the speech recognition language in Settings. Set Speech language for the language you speak; set this option for the code context you intend.

Include comments and Code Blocks initially remain on. Format Style begins at Structured, with Minimal and Detailed alternatives. These options guide representation of spoken content. They do not authorize the formatter to invent an implementation, missing requirement or unspoken code.

The style also starts with numbered-list, money and digit cleanup enabled. Check quantities, identifiers and explicit list markers after processing.

Dictate a bounded request

For example: “Add a loading indicator to the import button. Keep the existing CSV parser. Show an error if the file has no rows. Do not change the billing page.” A useful brief retains all four instructions. It should not add a new parser library, retry policy or release date unless you supplied those requirements.

Review every path, function name and boundary before handing the text to a coding tool. If formatting did not run, check the selected formatter and destination-selected style. If an identifier was misrecognized, edit it or consider vocabulary rather than adding more layout rules.

See the Coding Prompt instructions, custom rules, and the distinct Vibe coding preview.