AboutProjects
Notes

Ready-to-Use Mac Keyboard Automation Starter Pack

productivitymacoskeyboard-automationtemplates

Theory helps, but a working config makes the system real.

Below is a starter Goku config, a shared setup checklist, and a list of Keyboard Maestro macro ideas. Take what fits, ignore what does not.

A practical order for getting started: wire up the config structure first, then define one or two modes, then add Keyboard Maestro actions once the remapping layer feels stable. Remove anything you have not used after a week -- the system should shrink to what you actually use.

Starter Goku config

This config defines three simlayers -- w for opening apps, t for templates, and s for screenshots.

{
  :profiles {:default {:default true}}
 
  :templates {
    :km "osascript -e 'tell application \"Keyboard Maestro Engine\" to do script \"%s\"'"
    :open "open \"%s\""
  }
 
  :simlayers {
    :w-mode {:key :w}
    :t-mode {:key :t}
    :s-mode {:key :s}
  }
 
  :main [
    {:des "w-mode: open apps"
     :rules [:w-mode
       [:c [:open "-a Google Chrome"]]
       [:v [:open "-a Visual Studio Code"]]
       [:o [:open "-a Obsidian"]]
       [:k [:open "-a Keyboard Maestro"]]
     ]}
 
    {:des "t-mode: templates and helper actions"
     :rules [:t-mode
       [:0 [:km "Open Templates"]]
     ]}
 
    {:des "s-mode: screenshot helpers"
     :rules [:s-mode
       [:c [:km "Take Screenshot"]]
       [:o [:km "OCR Selected Text"]]
     ]}
  ]
}

Swap in your own app names and Keyboard Maestro macro names. The structure stays the same.

Shared setup checklist

Use this if you want multiple macOS user accounts to share the same keyboard automation source files.

Shared folder

Per user account

Keyboard Maestro

Maintenance

Keyboard Maestro macro ideas

App and workspace setup

Search and navigation

Repeated text and generation

Capture and utility actions

A few design rules worth keeping in mind

Keep it small at first

Resist the temptation to configure everything at once.

Wire up one mode, use it for a week, remove what you skip. The configs that last are the ones that grew from actual habits — not the ones that tried to predict them.

Further reading