Design is part of the shipping path now. This path covers the systems that keep a product visually coherent, the tools the work actually travels through, and the vocabulary that keeps designers, engineers, and managers talking about the same thing.
From first principles to production: the vocabulary and fidelity ladder, the systems and tokens underneath, type and layout, color and accessibility, the handoff to engineering, and the craft carried over from print - brand, vector, and CMYK.
Tokens, components, and patterns with the decisions baked in - the shared language that keeps a product consistent as the team grows.
Read it →The browser-based design tool most product teams standardized on - multiplayer files, components, and why it became the default.
Read it →Two terms used interchangeably that name different work - the experience someone has, and the interface they have it through.
Read it →Three fidelities of the same screen - structure, surface, then behavior - and which feedback each one can actually take.
Read it →Named values for color, spacing, and type, stored once and referenced everywhere - the atoms a design system is built from.
Read it →Contrast ratios, WCAG, dark mode, and never relying on color alone - making a palette legible to everyone.
Read it →Type scale, line height, measure, and hierarchy - the craft behind text that is effortless to read and scan.
Read it →The spacing scale and grid that make an interface feel calm instead of arranged - alignment, rhythm, and breathing room.
Read it →The moment a design becomes an engineer’s spec - what to include, where it breaks, and the tools that keep it lossless.
Read it →Math versus pixels - why Illustrator and Photoshop are different tools, and which format your logo and photos need.
Read it →RGB versus CMYK, PPI versus DPI, bleed and safe margins - the rules that keep a design vivid on paper and on a display.
Read it →A logo is not a brand - it is one part of a system of color, type, imagery, and voice, held together by guidelines.
Read it →An AI design partner is exactly as on-brand as the system you hand it - the system as an input the tool executes.
Read it →A gallery worth studying - four public systems at scale, and three downloadable system files: two teaching examples and Wise's real one as markdown.
Read it →The How-to: prepare your source material, upload it to your organization, review the system Claude generates, and publish it to your team.
Read it →