hammerspoon

Window management in Hammerspoon uses grid-based layouts defined in Lua configuration files. Create a grid.lua module to map hotkeys to window positions, then load it in init.lua. Hammerspoon adapts layouts dynamically to screen type—normal, ultrawide, or vertical—so you define positions once and they adjust automatically across displays.

Yes. Hammerspoon lets you define hyper and super modifier keys through a hyper-key.lua module, then bind them to actions like app launching or window switching. Use hs.hotkey.bind() to map key combinations to Lua functions, and enable config reloading with hotkeys to test changes instantly.

Create a unified switcher using Hammerspoon's window-switcher and app-launcher modules with fuzzy matching. Bind a hotkey to trigger the switcher, which filters open apps and windows by keystroke, letting you jump between apps without clicking. Store launcher and switcher logic in separate Lua modules for modularity.

Use a modular structure with separate Lua files for distinct tasks: hyper-key.lua for modifier definitions, grid.lua for window layouts, config-watch.lua for auto-reloading, and app-launcher.lua for quick-switch logic. Load all modules from init.lua and enable file watching so changes reload automatically without restarting.

Yes. Hammerspoon includes hs.ipc.cliInstall() which sets up a CLI so you can trigger Hammerspoon functions from the terminal. This lets you integrate Hammerspoon automation into shell scripts and external workflows without manual hotkey presses.

Use config-watch.lua to monitor your ~/.config/hammerspoon directory for file changes and auto-reload when you save. Alternatively, bind a hotkey to hs.reload() to manually trigger reloads. Both approaches let you test keybindings and window layouts instantly without restarting the application.