The ABC of Coded Style Guides
summary
Argues that a living component directory (a coded style guide) increases reuse and stabilizes UI by shipping a concrete setup: Storybook hosted in-repo, automated snapshot tests wired into CI, design tokens and Sketch libraries synced with components. Shows developers adding isolated components, running tests that catch regressions, and exposing runnable examples in the browser so new contributors can play with and integrate components. Claims reduced friction for maintenance and clearer ownership across teams.
AI-written summary · about
chapters (10)
- 0:00Coded style guides intro
- 4:50Style guides simplify integration
- 8:25Centralizing branding
- 12:30Testing components
- 16:48Style guide benefits
- 23:40Design tokens and colors
- 25:46Component integration workflows
- 28:47CI with style guides
- 31:19Designer-dev collaboration
- 34:19Q&A
related talks
30mThe ABC of Coded Style Guides
42mThe Dream of Styleguide Driven Development
01h 05mStyleguide-Driven Development
38mStyleguide-Driven Development
34mThe Dream of Styleguide Driven Development
24mFrom Sketch to Code Designing a Component Kit
28mFrom Sketch to Code Designing a Component Kit
30mLiving Style Guide Driven Development
