Every client used to get a short PDF: brand colours, a heading scale, maybe a logo usage note. It looked tidy and went stale within a month, because nothing forced the actual site to keep matching it.

Build it from the real CSS

A living style guide is just a page, built from the project's own stylesheet, that renders every button state, every heading level, every colour swatch directly from the classes in use:

<section class="guide-swatch">
  <div class="swatch swatch--brand"></div>
  <code>.swatch--brand { background: $brand-teal; }</code>
</section>

It catches drift automatically

If a developer adds a new button variant without documenting it, the style guide simply doesn't show it - which is a far more useful nudge than a PDF nobody re-opens after week one.

A static style guide goes stale the day it's published

A PDF or Sketch file documenting button states, spacing, and color usage is accurate exactly once - the moment it's exported. Every code change after that point can silently drift from the documented design with nothing forcing the two to stay in sync, which is precisely how most style guides end up ignored within a few months.

Generating docs from the actual components

A living style guide - built with something like Storybook - renders documentation directly from the real, running component code, so the guide can never show something the codebase doesn't actually produce. Any prop or state a component supports shows up automatically; anything removed from the component disappears from the docs without anyone needing to remember to update a separate file:

// The Button component IS the documentation source
export const Primary = { args: { variant: 'primary', children: 'Save changes' } };