Skip to content
CV
Browse documentation

Design System

Every visible property comes from a step, and every element exists exactly once. Everything the pages are built from lives here.

Each category loads its own examples. Source contracts sit beneath each preview; native hover and keyboard focus can be tested directly.

Story

The shared base for every case’s scroll story: start, line, stations, navigation and finale. Each case varies its stations, visuals and finale; the base stays the same.

Roles for story and case

--brand--brand-soft--brand-line--brand-chip-line--thread-line--panel-glass--glass-edge--mark-jira--ok--danger-line.case-path.dark
Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-roles">{roles.map(r=><span class="ds-role"><i style={`background:var(--${r})`}></i><code>--{r}</code></span>)}<span class="ds-role"><i class="ds-role__ink"></i><code>.case-path.dark</code></span></div>

Case head with a story: start and “Read the case” (↵), results on the status

Initiative case · AI enablement · Designing with AIzvoove · staffing software · 2025 – 2026

My working rules became the team’s AI infrastructure.

Role in the project
InitiatorOwn initiative, no brief
Setting
AI Steering (Value Builders)Founding member
Responsibility
Skills and foundationzvoove Brain, design and PM skills, knowledge base and design system connected, guardrails
Status
Live+2

As of September 2026

  • Live

    Since March 2026: 19 skills at launch, 34 across three departments in August 2026

  • In use

    Dark Factory with the developers since August 2026, the pipeline belongs to Engineering

  • Open

    Measured internally by tickets done

and 2 more states
Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/case/CaseHero.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="case-hero-stage ds-story--hero"><div class="case-frame"><CaseHero content={c} locale={locale} demo story/></div></div>

Start and “Start again” (pill with a light on its border, binary stream on hover)

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/story/StoryStart.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-story ds-story--light ds-story--row"><StoryStart locale={locale} demo/><StoryStart locale={locale} demo again/></div>

Dock: back · next | skip to the case

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/story/StoryDock.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-story case-path dark"><StoryDock skip={skip} demo/></div>

Shared platform

Each program keeps doing its job

StaffingTime trackingPayrollAbsencesExpert ModeInbox

One shared platform

MessagesWhat is happening

StaffingMon 06:00 · 2 shifts open

Expert ModeShift plan: Mon 06:00 unfilled

MailNorth: who covers Mon 06:00?

DetailsWhat Lena needs to know

AbsencesSick note J. B. · from Monday

TimeM. K.: 38 of 40 hours

PayrollPayroll waits for timesheets

Sign-in and accessWho can see and change what?

Switch between programsAll programs in one place

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/story/StoryScene.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-story case-path dark"><StoryScene name="lanes" locale={locale}/></div>

Messages become a signal

StaffingMon 06:00 · 2 shifts open

AbsencesSick note J. B. · from Monday

Expert ModeShift plan: Mon 06:00 unfilled

MailNorth: who covers Mon 06:00?

4 messages → 1 task

2 shifts on Mon 06:00 unfilled

detected 05:51 · before anyone asked

StaffingAbsencesExpert ModeMail
Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/story/StoryScene.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-story case-path dark"><StoryScene name="signal" locale={locale}/></div>

Building the Decision Object

Proposed by zAInDecision · Review staffing

Cover two open shifts

Monday, 06:00 · Logistics North · 8 hours per person

Not ready for approval

M. K. only has 2 hours available. The shift needs 8.

M. K.6 hours short

2 of 8 hours covered2 hours available

T. L.Fits the shift

8 of 8 hours covered9 hours available

Assessment: well supported

Based onShift planHours balanceQualification

The hours conflict is documented. A replacement for M. K. is still needed.

Find an alternative for M. K.

Keep T. L. Replace M. K. with someone for the full shift.

Resolve in chat
Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/story/StoryScene.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-story case-path dark"><StoryScene name="dobj" locale={locale}/></div>

zAIn conversation

⌂Notification Center›J. B.Monday, 19 October 2026

Tasks (9)

InboxDone

OVERDUE3

ShiftUnfilled shiftJ. B. — Logistik Nord◷ due Mon 05:30✦ Hand to zAIn
Time limitAssignment time limit exceededS. M. — BMW◷ 3 days overdue
SafetySafety briefingT. F. — Siemens◷ 5 days overdue

J. B. — Logistik Nord✓ Mark done

✦zAIn can propose a replacement for J. B. on Mon 06:00.Hand to zAIn

URGENCY

StatusOverdue

DueMo 05:30

TypeSHIFT

What happens herezAIn prepares, Lena approves
Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/story/StoryScene.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-story case-path dark"><StoryScene name="zain" locale={locale}/></div>

Decisions build the dashboard

⌂HomeMonday, 19 October 2026

Your morning at a glance

The early shifts are covered. Next up: the timesheets.

Prepared by zAInDecision · Needs your review

Match 12 timesheets

Week 42Time trackingStaffing

The matching proposals are ready. Check which assignment each timesheet belongs to.

Already prepared: timesheets and assignments brought together.
Review matching
Prepared matching · week 42
Scope
12 timesheets
Compared with
Assignments in the shift plan
Your review
Do person, assignment and hours match?

The proposal is open for review. Nothing has been approved or carried out.

Only your approval changes the assignment.

Done today

Mon 06:00 filled · T. L. + E. W.

Approved by you. Both shifts saved in the shift plan.

One shared state across programs

The updated shift plan is available to the other programs. No need to enter it again.

What happens hereOne case completed, the next still open
Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/story/StoryScene.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-story case-path dark"><StoryScene name="dash" locale={locale}/></div>

Station, reached

  1. 01

    Solve my own problem first

    write the way I work down instead of repeating it.

    Starting point

    • What slowed things down

      • Design was brought in too late
      • AI did not fit the system
      • Context got lost
    • The decision

      Instead of explaining the same things every day, I wrote down how I work. At first just for me. Then it turned out others could work with it just as well.

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/story/StoryStation.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-story case-path dark"><ol class="case-path__steps"><StoryStation i={story.steps[withCards]} n={withCards} art={arts[story.steps[withCards].id]} locale={locale} zoomLabel={t(locale,'case.zoom')} lit/></ol></div>

Station with a rebuilt interface

  1. 02

    Connect knowledge instead of copying it

    the knowledge base via MCP, improved together with its team.

    MCP

    Knowledge over MCPAgent · new sessionRebuilt · synthetic data
    1. Which fields does a timesheet export for customers need?
    2. knowledge-base · search3 results

      • 1Timesheet · data modelEntity, 14 fields
      • 2Export · CSV and PDFGuideline
      • 3Persona · dispatcherPersona

      A customer export needs 9 of the 14 fields: employee, assignment, date, start, end, breaks, hours, surcharges and approval. Internal cost centres stay out.

      1Timesheet · data model2Export · CSV and PDF3Persona · dispatcher

    Write a message …

    Rebuilt: an agent queries the Knowledge Base over MCP instead of someone pasting context into every session.

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/story/StoryStation.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-story case-path dark"><ol class="case-path__steps"><StoryStation i={story.steps[withMock]} n={withMock} art={arts[story.steps[withMock].id]} locale={locale} zoomLabel={t(locale,'case.zoom')} lit/></ol></div>

Learning band

Learning

A skill is only as good as the knowledge it is connected to. Improving the access was worth more than any additional prompt.

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/case/CaseHighlight.astro

States: default · keyboard focus where interactive · light / dark · reduced motion · ink (breaker before the first chapter, tone="ink" with lead)

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<CaseHighlight b={band}/>

Tooltip

01Solve my own problem firstwrite the way I work down instead of repeating it.19My working rules became the team’s AI infrastructure.
Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/case/CaseTip.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="ds-tips"><CaseTip k="01" t={story.steps[0].t} b={story.steps[0].b} locale={locale}/><CaseTip k="19" t={c.hero.h1} locale={locale}/></div>

More cases

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/case/CasePager.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<CasePager prev={link(others[0],'design-systems')} next={link(others[1],'product-systems')} locale={locale}/>

Case notes

Case notesHow to read this case.
Evidence
Repository snapshots from March and August 2026, Confluence documentation and my own account.
Images
Software screens rebuilt, with synthetic names and data. Diagrams rebuilt, skill contents paraphrased.
Team
AI Steering (Value Builders), engineering (Dark Factory), frontend lead (UnityUI), the knowledge base team, PM lead and tech lead (zAIn initiative).
Rights
zvoove and UnityUI are trademarks of the zvoove Group. This shows my work there; it is not official zvoove communication.
Last updated
As of September 2026
Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

src/components/case/CaseFooter.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<CaseFooter notes={c.notes} locale={locale}/>

Motion

Glides use a sine ease; their duration grows with the distance. A next step runs in two legs: the line to the number, a short pause, then on to the cards. Everything pauses out of view and is off under reduced motion.

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/StoryDemos.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<p class="max-w-text text-sm text-ink-muted">{t(locale,'ds.storyMotionNote')}</p>
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.