Marketing Design OS
Ship site changes as fast as you can describe them.
Write the change in plain language. The agent composes it from your real design system, proves it against schema and taste rules, and leaves it as a draft for you to approve.
See the guardrailsWhat you get
Speed for marketers. Guardrails for everyone else.
One workflow that answers to three different sets of worries.
No ticket, no sprint
Describe the section you want. It lands as a real page, not a mockup waiting on someone else's backlog.
Composed, not invented
The agent can only build from your existing blocks — so new pages inherit the system instead of drifting from it.
Schema-validated writes
Every patch is checked field by field against the live design system before anything is stored.
A stylistic linter
Taste rules the agent must satisfy: hero placement, section rhythm, no stray hex values in copy.
Draft-first by default
Writes land as drafts on dev. Nothing reaches the public site until someone says so.
Every change is legible
Each edit is a reviewable patch against a named page — readable before it ships, traceable after.
How it works
Open Claude and say what you want changed. The agent reads your live design system first — blocks, tokens, page treatments — then composes a layout patch in that vocabulary.
Two validators run before a single byte is written. One checks the patch against the schema. The other checks it against the design principles.
What that means in practice
The agent cannot invent a component to solve a layout problem. If nothing in the system fits, it says so and files the gap instead of faking it.
- Describe the change
- Validators run — schema, then principles
- The patch lands as a draft on dev
- You preview it and publish when you are happy