--- title: "Design Systems" url: https://www.ohmni.tech/design-systems language: en updated: 2026-08-22T23:48:55Z --- # Design Systems > A design dictionary is every design decision made once, as working code you own. Your team publishes without a designer, and AI tools build inside the system instead of around it. ## Six versions of the same button. That is not a taste problem. It is what happens when every design decision stays open forever. A design dictionary closes them, once, so your team can publish without asking anyone. [Get a Free Site Audit](https://www.ohmni.tech/free-site-audit) ### Your website was not designed. It was accumulated. It starts innocently. A campaign needs a slightly different hero. A webinar page gets a tweaked button. The approved color list grows by one, then three, then ten. Every designer who passes through leaves their own version behind. Nothing is wrong on its own. Together they become a site where nothing quite matches and every new page is a fresh argument. **The cost is not ugliness. The cost is that shipping anything now requires a designer.** That is the real bottleneck. Not the code, not the CMS. The fact that no decision was ever final, so every page reopens all of them. ### Three signs you have design creep More than one of everything. Two card styles, three button treatments, a hero that exists in four slightly different heights. Every new page needs a mockup. If your team cannot publish without design review, the system is not doing its job. Nobody can say what the brand colors are. There is a list somewhere, it has grown, and no one is sure which entries are still approved. ### Four layers, each decided once A design dictionary is not one artifact. It is four layers, each built from the one below, so a change at the foundation reaches everything above it without anyone editing a page. **That is the difference between a design system and a style guide. One is enforced by the code. The other is a document people are asked to remember.** ### A design dictionary is every decision, made once. Typography and type scale. Color, as named roles instead of a growing list of hex codes. Spacing. Border radius. Then the components built on top of them, and the page sections built on top of those. Not a style guide PDF that goes stale in a quarter. Working code, in your repository, that the website physically cannot disagree with. **The point of locking the decisions is not control. It is that nobody has to have an opinion about the button ever again.** Your team stops thinking about design and starts thinking about content, which is the thing that actually moves a buyer. ### What you get All of it in your repository, under your ownership, from the first day. - **Tokens** Color, type scale, spacing, radius, and shadow as structured data. A rebrand becomes a change in one file, not a six-week audit. - **Components** The interface pieces built from those tokens, so anything assembled from them is coherent by default. - **Templates** Page sections your team composes without a developer. Build a layout once, use it fifty times. - **Guardrails** Accessibility, performance, and search structure built into the framework, so they happen whether or not anyone remembers. Plus a live documentation site where every token and every section is rendered from the real system, so onboarding a new hire or an agency takes an afternoon. ### This is what makes AI safe to point at your website Give an AI tool a blank canvas and it invents a new blue every time. You get design creep at machine speed. Give it a design dictionary and it has nowhere to drift. The colors it can reach are the only colors that exist. The spacing is already decided. The accessibility rules are in the framework, not in a reviewer's memory. **Our clients generate their own pages with Claude Code, inside their own system, and the results look like the brand because they cannot look like anything else.** It goes past web pages. PDFs, one-pagers, invoices, and email templates all come out of the same core, all recognisably yours. ### You own it, including the documentation. The tokens, the components, the templates, the repository, and the configuration files that let an AI assistant work inside the system. All of it yours from day one. That includes the operating manual: the written rules that tell any developer, or any AI tool, how to extend the system without breaking it. Most handovers give you code and no instructions. This one gives you both. **If we part ways, your team keeps shipping. That is the test of whether a system was ever really yours.** ### Will this make our site look generic? The dictionary decides the mechanics, not the brand. Type scale, spacing, and radius are settled so nobody argues about them. What your pages say, and how they are composed, is wide open. Constraint at the component level is what lets the content be distinctive. ### We already have brand guidelines. Is this the same thing? No. Brand guidelines are a document that describes intent. A design dictionary is working code the website is built from. Guidelines can be ignored and usually are. Code cannot be. ### What happens to our existing site? We audit what exists, find the real patterns hiding under the variations, and consolidate. Most sites have three or four genuine layouts wearing a dozen costumes. ### Do we need a designer after this? For campaigns and content, no. For a genuine rebrand or a new product identity, yes, and the dictionary makes that work faster because there is one place to change. ### Can our team really build pages without a developer? That is the whole point, and it is the thing to test before you buy. Ask us to show a page being composed live during the call. ### Curious how much of your site is variation, not design? Start with a free site audit. We will map what exists, count the versions, and show you what consolidating would actually free up. You get the list either way. [Get a Free Site Audit](https://www.ohmni.tech/free-site-audit)