Day 1
The system first.
Tokens for colour, type and layout, then the shell. Nothing drawn twice.Tokens for colour, type and layout, then the shell: navigation, tables, charts. Nothing drawn twice.
Work — No. 01
Signal AI Ops.
A dashboard for teams running AI agents — runs, costs, evals, deploys.
Designed end to end in one week.
- Type
- Dashboard
- Platforms
- Web + mobileWeb 1440 + mobile 390
- Modes
- Dark + light
- Delivered
- Figma
The week, in numbers
36
screens
18 at 1440, 18 at 390
146
states
every overlay, empty and error
2
modes
dark and light, mirrored
24
auth frames
sign in to server error
193
variables
colour, type and layout
0
raw paints
every colour bound
The brief
one product.
every state.
A team shipping AI agents came to us with a list, not a design: runs, spend, quality and deploys, all in one place — on a desk and on a phone, at night and in daylight. They needed it ready for their developers the week after.
How the week went
seven days, four plates.
Day 2–4
Every screen, both sizes.
Eighteen screens at 1440, the same eighteen at 390.Eighteen screens at 1440, the same eighteen at 390 — each one built from the system, not copied.
Day 5
Then every state.
Tooltips, empty states, errors, dialogs, toasts: 146 of them.Tooltips, empty states, errors, confirm dialogs, toasts: 146 of them, each on its own frame.
Day 6–7
Light, auth, handoff.
The light mode mirrors the dark one. Every paint bound, every layer named.The light mode mirrors the dark one. Sign in, invite and error pages follow. Every paint bound, every layer named.
More plates
yours could be no. 05.
Pick your weekNext: No. 02 Infmar