Creating a Consistent Visual System
Transcript
Made automatically from the video's sound, so it may contain mistakes. Click a line to play from there.
Welcome to this explainer on visual design for the web. Today we are taking the digital chaos of random hex codes and magic numbers, and we're transforming it all into a bulletproof, lightweight visual system. Now, just for a super quick recap, having already engineered our canopy project to adapt fluidly across container widths, complete with a 320 pixel 400% reflow and strict WCAG 2.2 contrast and focus standards, it is time for our next big step.
We need to extract every scattered colour, type step, spacer unit, radius and shadow from our previous 11 sessions into a single reusable visual architecture. Alright, here is our agenda for today. One, the visual entropy trap.
Two, conducting an interface inventory, three, three-tier token architecture, four, amplifying brand personality, and five, the minimum viable system. Let's dive right in. Section one, the visual entropy trap, escaping the extremes.
This brilliantly illustrates the dilemma we face on the modern web. On one side, you've got ad hoc entropy, that organically grown, messy component math, where everyone just adds custom margins over time. But on the exact opposite side, untouched framework slop.
This is what happens when you ship generic defaults from tailwind or material design, or worse, when you let AI coding agents like Clawed Code or Cursor literally hallucinate fresh hex codes on every single prompt. Section two, conducting an interface inventory.
Visualizing the pain. You absolutely cannot systemize what you cannot see. Brad Frost teaches us that running an interface inventory cut-up audit rounds all your unique patterns.
Seeing those slightly different components side by side forces you to expose redundancies and actually deal with them. Imagine the sheer nightmare of running this audit on an organically grown five-page site, only to discover you've accidentally accumulated 14 slightly different button variants.
Throw in nine shades of grey, a chaotic mix of six, eight, twelve, and sixteen pixel radii, and magic numbers dictating your spacing. It's an absolute headache for designers, and it leaves vibecoders and AI agents completely lost in the weeds.
Section three, three-tier token architecture. Building the foundation. The ultimate antidote to that visual chaos is extracting those bespoke craft decisions into a rigid structure inspired by W3C, Material 3, and Polaris.
It's a three-tier design token architecture. Step one gives us tier 1 primitives, which are your raw values like OKLCH ramps and fluid space scales. Step 2 moves to tier 2 semantic roles, defining the purpose like background canvas or primary text.
Finally, step 3 brings us to tier 3, scoped component overrides for highly specific usage. So look at how this maps out in practice. A raw OKLCH primitive value connects upward to a semantic role alias, which then explicitly styles a button background component override.
The beauty here is that it all cascades perfectly. You update the primitive, and the entire system responds. This lightweight architecture then syncs seamlessly across the board. We're talking Figma variables and modes, live webflow style guides, CSS custom properties inside layer tokens, and Tailwind's app theme.
It bridges the gap perfectly, keeping designers, founders, and your AI agents entirely on the same page. Section 4. Amplifying brand Personality.
Polished without looking generic. Now, you might be wondering: does strict systemization make everything look incredibly generic? Alaka Hormatova's foundational rule proves the exact opposite.
A clean token system establishes perceptual patterns that actually empower teams and heavily amplify brand personality. Let me show you exactly what I mean. By flipping a single Figma variable mode, or simply swapping an HTML dash theme attribute on our canopy project, we can reskin the exact same semantic markup into a warm editorial archetype.
Instantly we get optical serif type, warm paper neutral backgrounds, subtle four pixel radii, and this lovely airy macro spacing rhythm. Or, boom, we instantly switch gears to a crisp Swiss technical utility vibe. Our token system swap in neo-grotesque and tabular mono fonts, sharp zero to two pixel radii, and a very precise one pixel keyline utility elevation.
And finally, we can toggle over to a tactile craft brand. This gives us warm tonal surfaces, 20 and 12 pixel concentric radii, and rich three-layer tinted shadows. We achieved all three distinct looks with zero component edits, whilst perfectly preserving 100% of our WCAG 2.2 contrast standards.
It's literally a game changer. Section 5. The Minimum Viable System. Guardrails for scale.
To actually implement this, you do not need hundreds of variables. That's overengineering. This is your minimum viable system checklist. You just need about 35 to 45 semantic tokens in total.
Eight surface and ink rolls, six or seven type steps, eight to nine fluid spacing tokens, three elevation tiers, and three concentric radius pairs. That is enough to build almost any interface. And to enforce this across your workflow, especially if you're using AI, you just drop an agents.md, or design.md file right into your repository.
This acts as a strict seven-rule visual rubric. It firmly bans your coding agents from using raw hexes or generic SASPurple, forcing them to stick exclusively to your curated tokens. So, with this bulletproof, lightweight visual architecture finally synchronized, what happens when we unleash it for a complete website redesign?
Can we take a legacy website and entirely rebuild it using these exact tokens? Well, that is exactly what we are going to tackle in our highly anticipated series finale. Thank you so much for joining me for this explainer, and I will see you in the next one.