---
title: "Case studies"
url: /cases
description: "Six design systems, 2011 to 2026, each told as problem, what was built, what it taught and what is still open."
---

## §0 · cases

# Case studies

Six design systems that I built or helped to build, from 2011 to 2026. Each one taught me one part of the method.

Six systems, one template: problem, what was built, what it taught, what is still open. Cases 4 to 6 were arrived at separately. That is the best evidence that this is a method.

- [Governance for a team of two](/cases/governance-for-two.md): A B2B car-loan platform front end built by two people with no designer. Vendored shadcn/ui, one skin file, and numbered decisions that each name a lint or a test.
- [An agent-first design-system foundation](/cases/agent-first-foundation.md): Built for a banking software vendor. The agent never writes HTML; it fills a typed page spec, and scripts build and judge the page.
- [A design validator for a banking app](/cases/validator-for-a-banking-app.md): A deterministic validator that finds whether a UI bug comes from the implementation, an inconsistent design file or the analysis. It reports and routes; it never blocks.
- [Tokens as a product](/cases/tokens-as-a-product.md): At Notino, tokens moved between the design tool and code in both directions, automatically, and shipped as versioned packages for many internal teams.
- [Two brands from one code base](/cases/two-brands-one-code-base.md): After a merger, ČP Invest and Generali Investments needed two investment sites at once. Both came from one graphic framework, with brand as a parameter.
- [One ordering system in three countries](/cases/one-system-three-countries.md): M-Objednávka, a B2B ordering system for Makro Cash & Carry in Czechia and for METRO in Slovakia and Ukraine. One front-end code base, three build targets.
