Skip to main content

Tutorial series

Build a minimal design system

Audit a clinic booking app, then define its tokens, colour, type and spacing scales and ten core components, and document and maintain them as a style guide.

  1. Audit your screens before you build a design system

    You will have an audit page in Figma that lists every colour, text setting, spacing value, corner radius and component your screens use, with each near-duplicate marked keep, merge or drop.

    Intermediate · 18 min

  2. Name design tokens from primitives to roles

    You will have the Larkfield Clinic values split into a primitives collection and a semantic collection in Figma variables, every semantic token aliasing a primitive, and a one-paragraph naming rule your team can apply to any new token.

    Intermediate · 16 min

  3. Build a colour palette with tonal ramps

    You will have four ten-step colour ramps built in OKLCH on a Figma palette page, each step labelled with its contrast on white and on the darkest grey, and the Larkfield semantic colour tokens pointing at ramp steps.

    Intermediate · 19 min

  4. Set a type scale for an app

    You will have a type scale for the Larkfield Clinic app worked out from a base size and a ratio, stored as Figma variables and six text styles named by role, shown on a specimen frame with real copy and checked at 200% text size.

    Intermediate · 17 min

  5. Define a spacing scale and corner radius tokens

    You will have a seven-step spacing scale on a 4 px base, three corner radius tokens and two border widths in Figma variables, a reference frame with the rules for choosing a step, and a Larkfield Pick a time screen whose every gap, padding, radius and stroke is a token.

    Intermediate · 18 min

  6. Specify ten core components and their states

    You will have a short written spec for each of the ten components the Larkfield Clinic app needs, listing anatomy, variants, required states, tokens and minimum touch size, placed beside the rebuilt components in Figma.

    Intermediate · 22 min

  7. Document a design system as a one-page style guide

    You will have a one-page Larkfield style guide in Figma, with principles, colour, type, spacing, ten components and error-message rules, tested by someone who built the Booked screen from it without asking you a question.

    Intermediate · 19 min

  8. Keep a design system in sync with code

    You will have a versioned Larkfield design system with a change log, its tokens exported from Figma into the code repository, an approval rule for new tokens and components, one real change shipped through all of it, and a monthly drift checklist.

    Advanced · 18 min