Setup for Developers
This setup targets development workflows that switch between editor, terminal, browser, and chat. Mouse+ comes first: most of your day is spent navigating and scrolling, so a stable pointer and a few high-value button mappings pay off before any language rules.
Step 1: Mouse+ foundation
Configure the mouse before anything else.
- Enable smooth scrolling so code and long documents scroll predictably.
- Set a comfortable pointer speed and disable acceleration if you prefer 1:1 tracking.
- Map side buttons to your most repeated developer actions, for example:
- open or focus the terminal
- switch Space (left/right desktop)
- back/forward in the browser or editor history
On mice with a tilting wheel, the wheel-tilt slots (WL/WR) can also be mapped — for example to Space switching.
Step 2: Editor / terminal input source
After the mouse feels right, add input-source rules for the apps you live in.
- Editor/IDE -> coding input source (usually plain ASCII).
- Terminal -> coding input source.
This keeps typing predictable the moment those apps gain focus.
Step 3: Browser domain rules
Refine the browser by domain for docs and tools.
Start with domains you visit many times per day:
- documentation sites
- internal tools
- AI assistants
- issue tracking or review systems
Step 4: Chat app input source
Map your chat app to your communication language input source.
Validation loop
- Confirm mouse behavior feels stable in IDE, terminal, and browser.
- Trigger your mapped side-button actions and confirm they fire.
- Switch the browser between two mapped domains.
- Switch between browser and chat app and confirm input is correct.
Maintenance guidance
- avoid duplicate overlapping rules
- keep domain rules explicit
- clean stale rules regularly