What you are getting
A dummy company's kit, built with the same engine as yours, so you can click through everything described here. Yours has your logo, colours, type and visuals in the same places.
Self-contained
One folder: index.html, brand.json and assets/. No installer, no account, no server, nothing that phones home. Double-click index.html and the whole kit opens in any browser, from disk, offline. Zip it and it is a backup; copy it and it is a second one.
An interface for people
The kit is a page, not a spec sheet. The logo in every variant, the palette with each colour's role, the type specimens, the visuals in their themes, the do-and-don't rules, and every file downloadable one at a time or all at once. It is the page you send to a designer, an agency or a new hire.
A composer, built in
The generators make finished assets from templates, deterministically, in the browser: the logo in any variant, colourway and background at any size; social banners and cards with your visuals behind the logo; an email signature; the favicon set. Same input, same output, every time. No model, no tokens, no API cost, and nothing to check for drift.
Local or on the web
The same folder works from a laptop, a shared drive or a static host. Put it on Cloudflare Pages and it is a private address you can send to anyone; the publishing guide covers it in half an hour.
A definition a machine can read
brand.json states your colours with their roles, the type scale, the logo variants and where each may be used, the minimum sizes, the motifs. That is what makes the next step possible: an agent that reads it derives your identity rather than guessing at it.
Two editions
The master archive with every source and print-size file, to store and never work out of; and the web edition, the same kit without the heavy masters, to send and to publish.
The easy way
- Pick an agentic coding tool and a current frontier model. Claude Code, OpenAI Codex, Gemini CLI, Cursor and Cline all read a folder directly, which is the point. Any of them works; a stronger model is materially better, and the gap is widest exactly where it matters — layout judgement and restraint.
- Open your brand kit folder in it. The one we delivered as the master archive, not a copy of a copy.
- Give it the one instruction that makes this work:
Read
brand.jsonin this folder before you make anything. Take every colour, font, spacing and logo path from that file — never type a value in by hand. Then make me [what you need], as a single HTML file that opens from disk, using only assets from this kit.
Then look at the result and correct it. Expect to; that is the workflow, not a failure of it.
The full guide
1. Choosing a tool and a subscription
None of this is tied to a vendor. The agentic tools — Claude Code, Codex, Gemini CLI, Cursor, Cline — differ in interface more than in result; take the one your team already has, or the one whose subscription fits. Anthropic, OpenAI and Google are the obvious model providers; Chinese frontier models such as Kimi and GLM are capable and considerably cheaper. OpenRouter gives one account and one key across most of them, which is the cheap way to compare before you commit. For installation matched to your operating system, ask ChatGPT or Gemini; that is faster and more current than any page.
2. The first session
Open the kit folder in the tool. Give the instruction above. Ask for something small first — an email signature, one social card — and look at it in a browser before asking for more. Correct it in plain words: "the logo is too small", "use the dark-ground variant here", "less decoration". The agent keeps the context, so each correction improves the next piece.
3. What to ask for, and how
Say what the piece is for and where it goes, not how it should look: "an investor update page, read on a phone, four short sections", "a LinkedIn card for a hiring announcement, 1200 by 627". Ask for a single self-contained HTML file that opens from disk — the same form we deliver in — and for a PDF or PNG produced from it if you need one. Good uses: internal decks, investor updates, social cards, email signatures, simple microsites, one-off event material — anything repetitive, fast-moving and low-stakes.
4. Checking the result against the kit
Four things to look at every time: the logo is a variant from the kit, on a ground it is allowed on, above its minimum size; every colour is one of yours; the fonts are the kit's fonts and not a look-alike; and nothing is decorated for the sake of it. If any of those is wrong, say so — and add "do not invent a colour or a logo variant" to your instruction next time.
5. Keeping what you make
Save finished pieces back into the kit folder, in a folder of their own, so the next session finds them and reuses them instead of starting again. Keep brand.json and assets/ untouched: they are the source, and if the agent proposes changing them, say no unless you mean to change your identity.
6. Where to be careful
Your core identity, your main pitch deck and your primary site carry real consequence, and an agent working alone will not match a designer on them. Use it to draft and explore, and keep a human decision at the end. If a piece is going in front of investors, treat the output as a starting point rather than a deliverable. A $100 subscription does not replace a $15,000 service; it gives you adequate, on-brand output for everyday needs — which is usually what you actually need, and which you would otherwise not have at all.