AICHE +

S

Sublime Text Integration

The short answer: open Sublime Text, position your cursor in a comment or documentation file, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak for 30-60 seconds, and AICHE inserts formatted text at your cursor.

Sublime Text users chose their editor for a specific reason: speed. It opens instantly. It handles large files without lag. It does not clutter the interface with panels and toolbars. Everything about Sublime is designed to minimize the time between thought and action.

AICHE matches that philosophy. One hotkey. No configuration UI inside the editor. No plugin to install. No sidebar panel consuming space. Press the key, speak, press the key again, text appears. The overhead is close to zero, which is exactly what Sublime users expect from their tools.

The friction Sublime users hit is documentation. You navigate, edit, and refactor code at thought speed using Goto Anything (Cmd+P), multiple cursors, and the command palette. Then you need to write a comment explaining a tricky function, and suddenly you are back to hunt-and-peck prose typing at 60 words per minute while your brain works at 150.

1. Open Sublime Text with your project or file.
2. Position your cursor where you need text - above a function, inside a docstring, in a markdown file, or at the top of a config file.
3. Press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux) to start AICHE recording.
4. Speak your complete explanation naturally. Do not worry about formatting or punctuation.
5. Press the hotkey again. AICHE transcribes and inserts the text.
6. Use Sublime's multiple cursors (Cmd+Shift+L or Ctrl+Shift+L on selected lines) to add comment prefixes to each line.
7. Adjust indentation and formatting to match your file's style.

Heads-up: AICHE inserts plain text without language-specific comment markers. You add the comment syntax (// or # or ''' or /* */) manually. Sublime makes this fast with multi-cursor and column selection.

Quick Code Comments

Function Documentation in Any Language

Sublime Text handles every language, and so does voice input. Position cursor above a Python function and dictate the docstring content. Position above a Go function and dictate the comment paragraph. Position above a Ruby method and dictate the YARD doc. The workflow is identical regardless of language.

Speak as if explaining the function to someone who can read the code but not your mind. Cover what it does, why it exists, what the parameters mean, what it returns, and what breaks if someone passes bad input. This takes 15-20 seconds for most functions and replaces 90 seconds of typing.

Sublime's strength here is speed of movement. Use Goto Symbol (Cmd+R or Ctrl+R) to jump between functions, dictate a comment at each one, then move to the next. You can document an entire file of 10 functions in 5 minutes.

Inline Explanations

For tricky one-liners, regex patterns, or non-obvious conditionals, add an inline comment. Position cursor at the end of the line or the line above, press the hotkey, and say "this regex matches email addresses but intentionally excludes plus-addressing to prevent alias abuse." Short explanations like this take 5 seconds to speak and save the next developer 10 minutes of confusion.

Markdown Editing

Sublime Text is a popular markdown editor because of its speed and distraction-free mode (Shift+F11). Combined with AICHE, it becomes a fast drafting environment.

Open a markdown file, enter distraction-free mode if you prefer, then dictate section by section. Press the hotkey, speak one section's content, stop. Add the markdown header manually. Move to the next section. Repeat.

Enable Content Organization in AICHE settings, and your spoken content gets structured into paragraphs automatically. This is particularly useful for longer documents like README files, project proposals, or technical specifications where you want clear paragraph breaks without having to say "new paragraph" explicitly.

For developers who use Sublime Text as their primary writing tool (blog posts, documentation sites, personal notes), voice input roughly triples throughput compared to typing.

Config File Documentation

Explaining Configuration Choices

Configuration files (YAML, TOML, INI, JSON) accumulate settings over time, and without comments, nobody knows why a timeout is set to 30 seconds instead of 10, or why retry logic is disabled for a specific service. Open the config file, position cursor above a section, and dictate the reasoning.

Sublime handles config files without any setup - syntax highlighting works automatically based on file extension. Your dictated comments sit alongside the configuration, and the next person to edit the file gets the context immediately.

Dotfiles and Scripts

If you maintain dotfiles (.bashrc, .zshrc, .gitconfig, .tmux.conf), dictate the explanations for non-obvious settings. Say "this alias uses ripgrep with hidden files included and gitignore respected because the default grep misses config files in dot directories." Future you will appreciate the explanation.

Sublime Text-Specific Tips

• No plugin required. AICHE runs as a separate desktop app. Sublime's lightweight philosophy stays intact. No Package Control dependency, no build system interaction, no startup time increase.
• Multiple cursors after dictation. Select the lines of dictated text, press Cmd+Shift+L (Mac) or Ctrl+Shift+L (Windows/Linux) to place cursors on every line, then type your comment prefix once. It applies to all lines simultaneously.
• Command Palette. Sublime's Command Palette (Cmd+Shift+P) and AICHE's hotkey do not conflict. Both are keyboard-driven, instant, and stay out of your way.
• Vintage/NeoVintageous. If you use Vim keybindings in Sublime, AICHE still works. Press the hotkey from any Vim mode (normal, insert, visual), dictate, and text inserts at cursor position.

The pro-tip: Use Sublime's project-wide search (Cmd+Shift+F) to find functions without comments (search for def or function and manually scan for missing documentation), then dictate comments at each one. Batch documentation sessions are faster than interrupting coding flow.

Result: Function documentation that took 8 minutes to type now takes 90 seconds to dictate. Markdown drafts get written at speaking speed in distraction-free mode. Config files ship with explanations that prevent "why is this set to 30" questions.

Do this now: Open a file in Sublime Text with an undocumented function, position your cursor above it, press ⌃+⌥+R, and explain what the code does as if teaching a teammate who has never seen it.