
For designers and engineers building shared infrastructure
A design system is not a collection of components. It is a decision made once so it does not need to be made again.
But the decisions that matter — the ones that give a system coherence rather than just consistency — cannot be made by System 2 alone. Rules and logic get you a library. They do not get you a language.
System 3 is what makes a design system feel right. The token that carries meaning. The spacing that has rhythm. The naming convention a team reaches for without thinking. These are not accidents. They are the residue of imaginative thinking done early and structured well.
This workshop connects design systems to the thinking that makes them work. Naming methodology. Token architecture. The machine-readable brief. These are structures built to hold System 3 outputs — creative decisions given a form precise enough that tools, teams and AI can all read them.
Neurodiverse designers often feel the rightness of a system before they can explain it. This workshop closes that gap — and gives the people around you a language for what you already know how to build.
What makes a design system coherent rather than just consistent
When to build, when to borrow, and when to hold
Token architecture: primitives, semantics, components
Naming conventions: how to build a shared language teams reach for naturally, without thinking
The machine-readable brief — structuring design decisions so tools, teams and AI can all read them without translation
Figma variables and how they map to a token infrastructure
Managing a library that scales without fracturing
Audit framework: what to look for and how to prioritise fixes
How design system decisions compound across a product over time
These tailored sessions help you quickly build your skills by practicing live, asking real-time questions, and going at the pace that fits how you learn best.
Tell me where the friction is. We'll work out the right starting point for you or your team.
hamish@hux.works
+44 (0)7832 839 543