Documentation
Plugins are plain JavaScript that run against a small, documented API — no build step, no framework. These four guides cover the whole surface: what the API can do, how to write a plugin by hand, how to have an AI write one for you, and how to publish your own list of plugins for other people to add.
Plugin API reference
Every method a plugin can call: reading and moving the map, drawing markers and overlays, storage, logging, and remote requests.
Creating a plugin
Write one by hand in the built-in editor: match patterns, settings, code, and how to test it on a real page.
Writing a plugin with AI
Hand an AI assistant the API reference and a description of what you want, and review its output against a short checklist.
Creating a registry
Publish your own list of plugins at a URL so other people can add it — the JSON shape, the rules it must follow, and what keeps users safe.
New here? Start with the API reference
The other three guides all assume you know what plugin.mapHook and a
settings schema (a form your plugin can expose for the user to configure) are.
The API reference explains both, plus everything else a plugin
can do — that's the natural first stop even if you plan to have an AI write the code for you.