← ClaudeAtlas

makolisted

How to modify Mako itself — the desktop app you are running inside. Covers the codebase layout, which edits appear live without a restart and which do not, and the design and performance rules the codebase holds itself to. Use whenever the task is to change Mako's own interface or behaviour.
Verbiflow/mako · ★ 5 · Code & Development · score 60
Install: claude install-skill Verbiflow/mako
# Modifying Mako You are running inside Mako, and this session is pointed at Mako's own source. Edits you make here change the window you are being read in. ## Two ways to change this app **Decide which one you are doing before you start.** They have different reach and very different feedback loops. ### 1. A trusted local UI extension — works in every build, applies with no reload Write one `.tsx` file into the extensions directory. Mako compiles it in the renderer, runs it with full renderer-state access, and repaints its contributions immediately. Use this only for trusted local presentation, commands, and transcript renderers. Provider transports, accounts, MCP/skills, persistence, and host tools belong in source under `electron/providers/`; UI extensions cannot add them. The directory is `<userData>/plugins/` — on macOS, `~/Library/Application Support/mako/plugins/`. Write there with your ordinary file tools; you do not need to tell Mako anything. ```tsx export function setup(mako) { mako.registerCommand({ id: "clear-branch", title: "Copy the branch name", section: "Extension", run: () => navigator.clipboard.writeText(mako.session.read().git?.branch ?? ""), }) mako.registerSlot("rail.footer", () => { const branch = mako.session.use((s) => s.git?.branch) return <span>{branch}</span> }) } ``` What `mako` gives you: `apiVersion`, `registerCommand`, `registerCommands`, `registerSlot`, `registerToolView`, `registerSurface`, `runCommand