Voice for Developer Documentation

The short answer: open your README file, code comment block, or commit message field, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak your explanation for 30-45 seconds, and AICHE transcribes and inserts the formatted text.

Typing documentation and detailed code comments takes 15-20 minutes per component and interrupts your coding flow with context switches between implementation and explanation.

1. Open the file where you want to add text (README.md, code comment block, or commit message editor).
2. Position your cursor at the insertion point.
3. Press your AICHE hotkey to start recording.
4. Speak your explanation naturally (example: "this function validates email addresses by checking format, verifying the domain exists, and rejecting disposable email services").
5. Press the hotkey again-AICHE transcribes, applies Message Ready formatting, and inserts the text.
6. Edit for technical accuracy if needed, then continue coding.

Heads-up: AICHE transcribes your spoken words literally. If you say "function that validates email," it inserts that sentence-not function code syntax. Use AICHE for writing documentation that explains code to humans, not for dictating code syntax itself.

The pro-tip: when writing function documentation or code comments, speak while looking at the implementation on screen. This produces more accurate descriptions than trying to remember what the code does from memory.

Result: a comprehensive README that takes 22 minutes to type becomes 6 minutes of dictation, and inline code comments get written immediately instead of being skipped for later.

Do this now: open any undocumented function in your codebase, add a comment block above it, press your hotkey, and dictate what the function does, why it exists, and what edge cases it handles.