---

$250^.00 $350^.00 Register for this workshop → 2 × 2h live sessions + Q&A. Dec 1–3.
With all video recordings & slides. Get a ticket.

Chances are, you’re not starting from a blank file. You’ve inherited a library that’s been growing for a few years — tokens nobody can trace back to a decision, components that half-bind their variables, that one frame still called “Frame 428,”, descriptions that are empty or simply wrong.

It works. Mostly. It just doesn’t scale, and every change comes with a real chance of breaking something downstream that nobody saw coming — a teammate, a consuming file, or an AI agent generating from it or checking it against code. This workshop is for that library: auditing what’s actually there, deciding what’s worth fixing, and fixing it.

What Will We Do?

• Learn what a design system audit is, and what kinds of issues it surfaces — for humans reading the library, and for the agents parsing it — auditing systematically across structure, tokens and documentation.
• Practice auditing a generic library and one you have more context on, then run a simple audit on your own library — or the example library we provide, if you don’t have one to bring.
• Establish what’s most critical to fix and why, and its impact on maintenance, on the people consuming the library, and on the agents parsing it.
• Understand severity results and turn them into a plan, and visualise the outcome — from a simple list to a full audit dashboard.
• Diagnose fast, then spend most of the time fixing: on day two, work through each main fix individually on your library (or the example one, if you don’t have your own) — catching breaking changes before you make them, leveraging component descriptions beyond the visual, and learning good design-system practice and the under-the-hood improvements as you go.
• Build in a manual pass and a way of recording decisions, so your system learns from itself.
• Use skills and AI as a supportive tool for the audit and fix work — not as an end in itself.

This works at any level of maturity: a young library, an inherited mess, or a mature system with drift. Don’t have a library of your own to bring? We’ll provide an example library so everyone has something real to work on.

Everyone leaves with a completed audit, fixes made, and a clear understanding of which things actually matter.

What Will Attendees Learn In This Workshop?

Working hands-on in your own library (or the base library, if you don’t have one to bring), by the end of the workshop you will know:

• How to tell whether a library is actually in good shape, rather than whether it looks good.
• What a design system audit actually surfaces, and how to read severity results and plan a way to fix them.
• How auditing a generic library differs from auditing one you have context on.
• Where the real maintenance costs hide: unbound values, broken token links, variants that don’t map to code, missing states.
• How to visualise an audit’s outcome, from a simple list to a full dashboard.
• How to rank problems by what they cost, so a cleanup has an order and an end.
• What counts as a breaking change, and how to tell before you make one.
• Why layer names, descriptions and properties are not housekeeping, but the part engineers and agents actually read — and how to leverage them beyond what’s visible on the canvas.
• Why the manual pass still matters: nothing is done until you’ve looked at it yourself.
• How to record decisions so your system learns from itself, and you don’t re-argue them later.
• You’ll leave with your own prioritised fix queue, ready to start next day.

---

About Javier Cuello

Javier is the founder of Fuller, a European agency specialising in design systems, building practical, accessible, and inclusive products that work better for everyone.

After years as a digital nomad, he is now based in The Hague, often wandering the city in search of good coffee and even better ideas.

Time & Schedule

This workshop is split over two days. The workshop sessions will run on the following days:

• Tue, December 1, 9:00 – 11:30 AM PT (18:00 – 20:30 CEST)
• Thu, December 3, 9:00 – 11:30 AM PT (18:00 – 20:30 CEST)

$250^.00 $350^.00 Register for this workshop → 2 × 2h live sessions + Q&A. Dec 1–3.
With all video recordings & slides. Get a ticket.

---

Course Breakdown

Day 1 — Auditing a Design System

8:45 AM PT
Virtual doors open, registration, chat and introductions.

9:00 AM – 11:00 AM

• What is a design system audit, and what kinds of issues it can surface — for humans, and for the AI agents that generate UI, check Figma-code parity, or write documentation from your library
• How to understand the severity results, and plan a way to fix them
• Auditing a generic library versus one that we have more context about
• Visualising the outcome, from simple lists to full audit dashboards
• Practicing a simple audit on your own library and sharing discoveries

11:00 AM – 11:30 AM
Q&A with Javier on the day’s material. Chat with each other.

Day 2 — Fixing What the Audit Found

8:45 AM PT
Virtual doors open, registration, chat and introductions.

9:00 AM – 11:00 AM

• What counts as a breaking change, and how to tell before you make one
• Working together to fix your library — or the example library, if you don’t have your own — with a real mix of problems
• Beyond visual, how to leverage component descriptions
• The manual pass, and why it still matters: nothing is done until you’ve looked at it yourself
• A system that learns from itself: recording decisions so you don’t re-argue them later

11:00 AM – 11:30 AM
Q&A with Javier on the day’s material. Chat with each other.