Workshops: Agentic Engineering Practices
Design Systems & Storybook with AI Coding Agents: Workshop
Coding agents produce UI quickly, but left alone they invent new buttons, spacing values and colour shades in every feature. This workshop shows your team how to make the design system the agent's first point of reference: tokens as the source of truth, Storybook as living documentation, rules that keep agents on-system and visual regression tests that catch drift.
Who is this workshop for?
- Design system teams and frontend platform engineers
- Frontend developers working with React, Angular, Vue or Web Components
- Design engineers and UX designers who work close to code
- Tech leads worried about UI inconsistency as agent use grows
- Teams consolidating several component libraries into one
What you will take away
- Structure design tokens so agents use them consistently instead of hard-coded values.
- Write and maintain Storybook stories, controls and documentation with agent support.
- Give agents instructions and component inventories so they reuse existing components first.
- Turn design specifications into components with agents and review the result against the design.
- Set up visual regression and accessibility checks that catch unintended UI changes in pull requests.
Agenda
Module 1
Why agents drift off-system
- How agents choose components and styles without guidance
- Inventory: what your design system offers and where it has gaps
- Rules in CLAUDE.md, AGENTS.md or Cursor rules for UI work
Module 2
Tokens as the source of truth
- Colour, spacing, typography and theming tokens
- Transforming tokens for several platforms, e.g. with Style Dictionary
- Lint rules that flag hard-coded values introduced by the agent
Module 3
Storybook with agents
- Exercise: the agent writes stories, args and docs for existing components
- Interaction tests and documented states: loading, empty, error
- Storybook and component catalogues as context for coding agents
Module 4
From design to component
- Feeding design data to agents, e.g. from Figma via MCP where your setup supports it
- Building a new component with variants, tests and stories
- Design review: comparing the result with the specification
Module 5
Guarding consistency
- Visual regression with Playwright screenshots or Chromatic
- Accessibility checks with axe in stories and CI
- Deprecating and migrating old components with the agent
Design systems are context for agents
For human developers the design system is documentation they hopefully read. For an agent it can be much more: a machine-readable catalogue of components, props, tokens and usage rules it consults on every UI task. The better that catalogue is structured, the more the output looks as if your own team built it.
Agents such as Claude Code, Cursor, GitHub Copilot or OpenAI Codex can also take over the unloved maintenance work: missing stories, outdated docs and migrating usages of deprecated components across dozens of screens.
Typical problems we tackle
Participants bring their own system; common starting points are:
- Hard-coded colours and spacing scattered across feature code
- Several near-identical components because nobody found the original
- Storybook out of date or missing for half the components
- No automated check for visual or accessibility regressions
Designers and developers at one table
The workshop works best when design and development attend together, because many decisions sit at the boundary: naming, variants, states and what counts as a regression. We run it remotely or on-site, in English or German, with neooutput AI Code Engineers who build frontends with agents in client projects.
Frequently asked questions
Do we need Figma?
No. Figma is widespread and can be connected to agents, but the workshop works equally well with other design tools or with a design system that exists only in code.
Which frameworks do you support?
React, Angular, Vue, Svelte and Web Components, each with Storybook. The principles for tokens and consistency are framework-independent.
Can an agent build our design system from scratch?
It can scaffold components and stories quickly, but the design decisions behind a system – naming, scales, principles – need designers and developers. We use agents to speed up implementation and maintenance, not to replace that work.
Workshop
Get in touch
Should agents build UI that looks like your product rather than a generic template?
Tell us roughly how many people will join and pick dates that work – we will get back to you within 24 hours with a proposal for content, format and schedule.
Prefer to talk first?
15 minutes, free and without obligation – with our AI Trainers and AI Code Engineers.
Book a call for free (opens in new tab) +49 761 519 751 50 (24/7)Request a training / workshop
Workshop: Design Systems & Storybook with AI Coding Agents: Workshop · 1 day
More workshops
- Workshops: Agentic Engineering PracticesPair & Mob Programming with an AI Agent: Team Workshop
- Workshops: Agentic Engineering PracticesAgent-Ready User Stories: Scrum & Kanban with Coding Agents
- Workshops: Agentic Engineering PracticesObservability with Coding Agents: OpenTelemetry Workshop
- Workshops: Agentic Engineering Practicesi18n & Localization with Coding Agents: Half-Day Workshop
- Workshops: Agentic Engineering PracticesScripts, CLIs & Internal Tools with Coding Agents: Workshop
- AI Development ServicesIntegrating LLM Features into an Existing App: A Guide
