Download PDF

Free resource · Design systems

Figma Design-System Starter Kit

A starter structure for tokens, components, variants and handoff. Stand up a system that scales — without a forty-page manual nobody reads.

Mariana Ordonez Agentic Product & AI UX Designer
How to use it — Recreate this structure in a fresh Figma file, then swap the sample values for your brand. Start with foundations, add only the components you actually ship, and document as you build. A living system beats a perfect one — bias toward tokens, variants and clear names over volume.
01 · File & page structure where things live

Recommended Figma pages

📄  Cover            name · version · owner
📐  Foundations      colour · type · space · grid · icons
🧩  Components        buttons · inputs · cards · nav · feedback
🧱  Patterns          forms · empty states · tables · modals
🖼  Templates         PDP · landing · checkout · account
🗂  Archive           deprecated / WIP
📝  Changelog         what shipped, when, by whom
02 · Naming conventions findable = usable
  • Tokens: category/role/variantcolor/text/muted
  • Components: Category / NameButton / Primary
  • Use slashes to group in the Assets panel & instance menus
  • Layers named by intent, never "Rectangle 42"
  • Variants via properties (Type, Size, State), not duplicated frames
  • Icons: icon/name, 24px frame, single stroke weight
03 · Foundations — tokens the source of truth

Colour roles

TokenRole
color/bg/basePage background
color/bg/subtleCards, panels
color/text/strongHeadings, key text
color/text/mutedSecondary text
color/borderDividers, inputs
color/brandPrimary actions
color/brand/hoverHover / pressed
color/feedback/*success · warning · danger

Spacing & radius (4px base)

TokenpxTokenpx
space/14space/624
space/28space/832
space/312space/1248
space/416radius/md10
radius/sm6radius/pill999

Type scale

TokenSize / lineWeight
text/display40 / 44600
text/h130 / 36600
text/h222 / 28600
text/h317 / 24600
text/body15 / 24400
text/caption12 / 16500

Breakpoints & elevation

BreakpointpxShadowUse
sm480e1Cards
md768e2Dropdowns
lg1024e3Modals
xl1280
04 · Component checklist done means done

Every component ships with

  • Variant properties: Type, Size where relevant
  • States: default · hover · focus · active · disabled · loading · error
  • Tokens only — no hard-coded hex, px or type
  • Auto layout + resizing rules that survive content changes
  • Responsive behaviour defined (min/max, wrap, truncation)
  • Accessible name + focus order + AA contrast
  • Content rules: max length, empty/overflow, placeholder
  • Dev notes / code link in the description field
05 · Handoff documentation per component

One-screen spec

  • Purpose — what it's for, when not to use it
  • Anatomy — labelled parts
  • Props / variants — table of options & defaults
  • States & behaviour — including motion
  • Tokens — colour, space, type used
  • Do / Don't — two or three of each
  • Accessibility — roles, labels, keyboard
06 · Governance keep it alive

Contribution & versioning

  • One published library = single source of truth
  • Versioned releases with a written changelog
  • Deprecation policy: mark → migrate → remove
  • Lightweight request flow for new components
  • Review by an owner before anything publishes