Skip to content
CV
Workmax.system, max.zeichen and max.lab10 min read01 · Overview

Product design case study · Design systems · Own systemOwn system · max.systems · October 2026

A design system you can't work around

For my portfolio I didn't take a template, I built a system: four token layers, 131 custom marks, a contract for every component and guards that reject any hard-coded colour. Humans and AI agents work under the same rules, and max.lab makes my earlier systems explorable, live.

Read the caseRJump to results
Role in the project
End to endDesign, architecture, code and documentation
Tools
Astro, React, Tailwind 4Radix Colors and shadcn; built with Claude Code, Codex and Orca
Scope
Three partsmax.system, max.zeichen and max.lab
Status
Live+2

As of September 2026

  • Live

    Has carried this website since October 2026

  • Checked

    Guards and around 300 tests on every build

  • Open

    Effect not measured

and 2 more states
As of September 2026
Live+2

As of September 2026

  • Live

    Has carried this website since October 2026

  • Checked

    Guards and around 300 tests on every build

  • Open

    Effect not measured

I didn’t write rules for my portfolio. I built a system no change can get around, whether it comes from me or from an agent.

max.system, max.zeichen and max.lab

At a glance

  • 88 roles

    in four token layers; fixed values fail the build

  • 131

    glyphs from one source, foreign icon imports blocked

  • 300+

    component files with a contract

    300+component files with a contractManifest with source hashes
  1. Problem

    One path per value

    Four token layers. No colour and no spacing lives outside them.

  2. Intervention

    The system says no

    Guards fail the build when something bypasses the system.

  3. Outcome

    For human and agent

    The same files and tests apply to me and to every AI tool. max.lab makes earlier systems explorable.

Role in the project
End to endDesign, architecture, code and documentation
Tools
Astro, React, Tailwind 4Radix Colors and shadcn; built with Claude Code, Codex and Orca
Scope
Three partsmax.system, max.zeichen and max.lab
02 · Why a system of my own

A portfolio about design systems has to be one

I build my portfolio with AI agents. They're fast, but they like to improvise: a hex value here, a foreign icon there, a spacing that exists nowhere else. After a few weeks the site would have looked like the codebases I've cleaned up in every job I've had.

The system has four jobs to do, depending on who is building, changing or checking:

  • Me, buildingJob story

    When
    I build a new page or case,
    I want
    to draw only on the system’s tokens, marks and components,
    so
    the site stays coherent after hundreds of changes.
  • Me, changingJob story

    When
    I change a component,
    I want
    to see first which pages and parts use it,
    so
    nothing breaks unnoticed somewhere else.
  • An AI agentJob story

    When
    I get a task in the repository,
    I want
    to read rules, components and limits from files instead of guessing,
    so
    my change passes the guards.
  • Whoever reviews my workJob story

    When
    I assess a design system that can’t be published,
    I want
    to touch it live and trace it back to the token,
    so
    I see more than a screenshot.
Written from the requirements I set for the system.
03 · Four token layers

Every colour has exactly one path

The values come from five Radix scales, light and dark. Above them sit 88 semantic roles such as surface, text, line, brand, success and warning. A thin bridge translates them for shadcn, and only the top layer makes them usable in Tailwind. I removed Tailwind's default palettes: whatever isn't in the system doesn't exist.

Four layers
  1. Primitives

    Radix scales, spacing, radii, type, motion. Only token files may touch them.

  2. Semantics

    88 roles; dark mode only swaps the scales.

  3. shadcn bridge

    18 names that point only to semantics.

  4. Tailwind

    Our own colours, radii, shadows and type, nothing else.

From utility to colour valueLive on this site

max.does.systemsmax.systemLiveoriginaloriginalRuns on the real system of this site: the same tokens, components and rules.Docs
Pick a role and follow the chain, light and dark side by side.
04 · max.zeichen

Marks of my own instead of an icon library

Third-party icon sets bring their own stroke weight and attitude. So I drew max.zeichen: 64 UI marks in outline and filled, each in six true sizes on a 32-unit grid, plus illustrations, hero motifs and 48 flow motifs in seven palettes. The geometry lives as source code; a build turns it into SVGs, sprites, React components and custom elements.

131 marks, searchableLive on this site

max.does.systemsmax.systemLiveoriginaloriginalRuns on the real system of this site: the same tokens, components and rules.Docs
Search, filter, change size: every size is drawn, not scaled.

The website only receives released files, with checksums and a locked version. Edits happen in the source only. An import from lucide-react fails the build.

05 · Contracts and workbench

Knowledge belongs in contracts, not in heads

Every component has a contract: its job, entry point, limits and how it is reused, directly, through a parent or as a reference only. A generated manifest holds source hashes, and a usage scan shows where a component is really used. A command line answers the same questions for humans and agents.

A contract, liveLive on this site

max.does.systemsmax.systemLiveoriginaloriginalRuns on the real system of this site: the same tokens, components and rules.Docs
Pick a component: job, reuse, limits, real usages and the component itself.

What the system knows is in the manifest: over a hundred curated contracts, more than 300 component files, over 500 scanned source files. It also states what the system doesn't know: an import doesn't prove that something actually renders.

06 · Guards

The system says no

So every build runs guards that raise hard errors.

What gets rejected
  1. Hard-coded values

    Hex, rgb, oklch, px and rem literals outside the token files.

  2. Foreign palettes

    Tailwind colours, off-scale values, primitives inside components.

  3. Foreign marks

    Icon imports that don't come from max.zeichen.

  4. Drift

    A stale manifest, demos without a component, files without a contract.

Around 300 tests and a browser matrix across German and English, three widths and both themes hold it together. In the lab, a dedicated guard makes sure original code from former employers can never be published.

Accessibility

Every change has to meet the same bar: keyboard, visible focus, contrast, reduced motion and no horizontal scrolling at 320 pixels. Checks run in both themes at 1440, 390 and 320 pixels, and colour is never the only information. Browser scripts measure WCAG contrast, at least 4.5:1 for text and 3:1 for icons, on selected pages. This does not yet run automatically in every build; a checker like axe is still missing.

Learning

Rules nobody checks are suggestions. A system only holds once the build can say no.

07 · Human and agent

The same rules for human and agent

Whether it's Claude, Codex or ChatGPT, they all read the same files. An agent contract describes tokens, components and limits; skills of my own guide case copy, stories and variant labs. No server, no key, just the repository.

This site has patterns too, and the most important one is the decision: every chapter names one, with its cost. Its rules live in the repository’s case playbook, the same one the agents read. Here is the pattern, shown on this chapter’s own decision.

Pattern: a chapter’s decisionfrom this case

Sample

  1. MarkerGlyph and kind of note, so the decision stands out from the running text
  2. TitleNames the decision as a statement
  3. Reason and costWhy it was decided this way, and what it cost

Rules

  • Do:One decision per chapter, with its cost.
  • Do:Headings as statements.
  • Do:Only what portfolio.os can back up.
  • Don’t:Claiming impact that wasn’t measured.
How an agent reads itpatterns/decision.md
---
pattern: decision
source: docs/case-playbook.md
---

## Anatomy
1. Marker [mark] — Glyph and kind of note, so the decision stands out from the running text
2. Title [title] — Names the decision as a statement
3. Reason and cost [body] — Why it was decided this way, and what it cost

## Rules
- DO: One decision per chapter, with its cost.
- DO: Headings as statements.
- DO: Only what portfolio.os can back up.
- DON’T: Claiming impact that wasn’t measured.

The rules are shortened from the case playbook.

One route for human and agent
  1. Own branch

    Every change starts away from the live site

  2. Contract

    New components need a registry entry, or the check fails

  3. Guards and tests

    Run on every build and fail hard

  4. Preview

    Every state can be checked as a preview before it goes live

  5. Release

    Only I release, as one merge

Clean-up has a route too. A usage report reads the source code and classifies every component: in early November 2026, 202 of 321 were reachable from a public page, 107 only from docs or previews. Nothing is deleted automatically; every candidate is reviewed one by one.

08 · max.lab

Systems you can touch

My earlier systems belong to my former employers. To show them anyway, I built max.lab: a documentation platform where Compass and Camelot run as rebuilds, measured from the rendered original and written from scratch. An inspector traces every spacing and colour back to the token that produces it.

Compass button with inspectorLive in the lab

max.labCompassLiverebuiltrebuiltRewritten for this site, not the original code. Where a detail is approximated, the docs say so.Docs
Switch on “Measure” and the inspector shows every value with its token.

The lab is a system in its own right: one shared component contract for both systems, an embed protocol for height and theme, and a public build that only contains rebuilds.

09 · Outcome

What came of it

  1. One path per value

    Four layers, 88 roles; hard-coded values fail the build

    No colour and no spacing outside the tokens

  2. One hand

    131 marks from one source, foreign icon imports blocked

    Own marks instead of third-party icon sets

  3. Knowledge in the system

    Over 300 component files with a contract, a manifest with source hashes

    Every component explains itself

  4. Human and agent

    Agent contract and skills in the repository, no server or key

    The same rules in every tool

  5. Show earlier systems

    max.lab with an inspector, embedded in the cases

    Compass and Camelot live, not as screenshots

  6. What is still openopen

    not measured

    Measure speed and quality

10 · Looking back

What I learned and would do differently today

Caveats

max.system carries one website, built by one person with agents; how it scales across several teams is untested. What is documented is scope, contracts and checks, not how much faster I build with it; the lab shows Compass and Camelot as rebuilds. As of 1 November 2026.

Learnings

  1. Coverage isn't a goal

    I don't delete a variant study just to make a metric look better. An open list is a to-do list, not a list of failures.

  2. Same values, different roles

    I don't merge two tokens with the same value if they do different jobs. Otherwise the first change breaks both.

  3. Name the debt

    A type token still carries the name of a former typeface but has long pointed to another. That sits openly in the code until it's renamed properly.

What I would do differently today

  1. The guards first

    I would write the checks before the first components. Every rule that came later brought clean-up work with it.

  2. Names by job, from the start

    A type token still carries the name of a former typeface. Had I named every role by its job from the start, that debt wouldn’t exist.

  3. Record a baseline

    I should have noted how long a new page took before the system. As it is, the gain in speed stays an estimate.

A design system doesn’t prove itself in its documentation but in what it rejects.

Maximilian Dahl

fin (for now)

CV · Maximilian Dahl
In plain words

What do you actually do, Max?

My parents and family have nothing to do with tech or my profession. They told me they did not understand my website. This is for them. And for anyone who would like an explanation without the jargon.

I make software easier to work with.

When someone spends ages searching for a button or has to enter the same information three times, I want to know why. I watch how people work, talk to them and design a better way through the task. Then we try it together.

My title is Principal Designer. That means I also make decisions about how whole products fit together and help the team build on them. I still design and write code myself.

Here is a simple example.

At zvoove, I designed an assistant called zAIn. This simplified example shows the idea:

  1. Someone asks

    “How much holiday do I have left?”

  2. The assistant looks it up

    It finds the information and explains the answer.

  3. The person decides

    If they want to book time off, they review the details before anything is sent.

My job is to work out what people need to see, how the answer should be explained and when the program needs their approval.

A design system is a bit like LEGO.

Imagine every team inventing its own bricks. Nothing fits. With a shared kit, the pieces connect, even when people build different things.

Shared pieces. Different things you can build.
Book time offReview an invoice

In software, those pieces are things like buttons, input fields and messages, plus rules for how they work together. I built this kind of kit at Container xChange. It is called Compass.

What has come out of my work?

One starting point
At zvoove, I designed the shared starting point for several programs and tried it out in code. It became Launchpad, which has been live since August 2026.
Built, too
I built the visible part of the notification centre myself. A backend engineer built the part behind it, and we shipped it together.
A team that can build on the work
At Container xChange, I grew the design team from 4 to 14 together with Niclas. Compass gave designers and developers a shared kit to work with.

What am I particularly good at?

I look beyond the screen in front of me. When several teams run into the same problem, I look for a solution they can share. That is how Compass came about.

And I like making an idea tangible early. I can build a working version myself, put it in front of someone and find out where it falls short. I would rather learn that from using it than from a long discussion about a picture.

What would I like to do next?

I want to help decide what a product should become, support a team and keep building myself. I am looking for a role as a Principal Designer, Team Lead or AI Product Builder, in a team that builds with artificial intelligence.

In plain words: I want to take responsibility for the whole thing, without giving up the part I enjoy most — trying things out and making them work.