Build your own button — config, not code
A Magik Button is a single declarative file: questions plus steps. New workflows are added as configuration, validated and dry-run before they go live — no custom software, ever.
Most workflow tools make you the engineer. LocalMagik goes the other way: the engine is generic, and every button is just data — a single button.json describing the questions to ask and the steps to run.
That one design decision is where the leverage comes from:
- New buttons ship fast. Defining a workflow is writing configuration, not building software. A button tailored to your business is a conversation, not a project.
- Every button is safe by construction. Definitions are validated before they go live — references must resolve, steps can't loop, and anything that sends must sit behind an approval gate.
- Builders can test without risk. The authoring CLI dry-runs any button offline with a stub AI — no database, no API keys, no accidental sends — before publishing it to a real workspace.
You click the button. The button is just a file. The engine does the rest — and that's why your next workflow is days away, not quarters.
Questions, answered
How is a new button created?
A button is one JSON definition: the questions to ask and the ordered steps to run. The authoring CLI scaffolds it, validates it (schema, references, no cycles), dry-runs it offline with a stub AI, and publishes it to a workspace — no app deploy required.
Do I have to be technical to get a custom button?
No — that's the point of config-not-code. Tell us the workflow you repeat every week and a tailored button can be defined for your workspace quickly, because nobody is writing custom software to do it.
Can a builder or agency make buttons for clients?
Yes. The CLI is built for exactly that: scaffold, validate, dry-run offline, then publish into a client's workspace. The format is a single readable JSON file that AI coding tools handle well.
Why does 'config, not code' matter to me as an owner?
Speed and safety. Config is fast to create and cheap to change, and every definition passes the same validation — including the rule that nothing sends without an approval gate.
See it in a button
The fastest way to understand LocalMagik is to run one Magik Button end to end.