Design systems
Tokens, components, usage guidelines and design documentation.
Download all 46
Start here 1
The general, start-from-zero entry for a need in this category: it works from a blank start, asks for what it needs and hands off to the specific entries. Example: Plan a trip.
- Set up a first design system
Sets up a first design system in gated steps - UI audit, tokens, the first ten components, usage docs, a pilot with one product team and a governance plan.
Specific 33
One situation, audience, tool or format inside the category. Example: Plan a road trip with children.
- Define an icon system
Defines an icon system with grid and keylines, stroke and corner rules, sizes, naming, metaphors, accessibility and contribution rules. Use when a design system creates or tidies up its icons.
- Write accessibility annotations
Annotates a screen design for engineering handoff with accessibility notes - headings, landmarks, focus order, accessible names, states, keyboard behaviour and announcements - mapped to WCAG.
- Audit design consistency across screens
Inventories spacing, type, colour, radii and component variants across screens, finds near-duplicates and plans their consolidation. Use before building or cleaning up a design system.
- Write a design-system component spec
Writes a design-system component spec covering anatomy, variants, states, behaviour, tokens, content rules, dos and don'ts, and accessibility. Use when adding or documenting a component.
- Define motion tokens
Defines a design system's motion tokens for duration and easing, with usage rules per interaction type and reduced-motion behaviour across components.
- Write a design system onboarding guide
Writes a getting-started guide for designers and engineers who are new to your design system, with setup, core concepts, a first real task, where to find things and common mistakes.
- Audit design-to-code component parity
Compares a design library's components with their coded counterparts, finding mismatched names, variants, props, states and tokens and missing components, and plans how to realign them.
- Define product illustration guidelines
Defines a product's illustration system with style rules, palette, people depiction, use cases and sizes, dark mode, alt text, and what to avoid, so every illustrator matches.
- Measure design system adoption
Defines how to measure design system adoption with code and design-file coverage, detached instances, contribution rates and team satisfaction, plus a quarterly report format.
- Plan a component deprecation
Plans the deprecation of one design-system component with a usage inventory, replacement mapping, warnings in code and design files, migration support and a removal date.
- Design layout primitives
Designs a design system's layout primitives such as Stack, Inline, Grid, Box and Sidebar, with props, spacing rules, semantics, examples and the misuse each prevents.
- Audit hard-coded styles against tokens
Scans a codebase for hard-coded colours, spacing, radii and type sizes, maps each to the nearest design token, and proposes or applies replacements, listing values with no token.
- Define elevation and layering rules
Defines a design system's elevation levels, shadow and surface tokens per theme, and a named layering scale for overlays, with stacking rules for dialogs, menus, toasts and sticky elements.
- Define a layout grid and breakpoints
Defines a design system's layout grid with breakpoints, columns, gutters, margins, max widths and container rules, plus tokens, design-file grid styles and responsive rules.
- Define a spacing and sizing scale
Defines a spacing and sizing scale with a base unit, steps, token names, control and icon sizes, and rules for padding, gaps and layout spacing.
- Define a type scale as tokens
Defines a UI typography scale as tokens with role names, sizes, line heights, weights, letter spacing and responsive steps, plus code and design-file styles.
- Plan a design system documentation site
Plans the information architecture and page templates for a design system documentation site serving designers and engineers, with search, live examples, versioning and ownership.
- Plan a design system roadmap
Turns a design system backlog of requests, bugs and debt into a prioritised quarterly roadmap scored on adoption impact, reach and effort, with what is deliberately not being done.
- Triage a design-system component request
Decides whether a requested component belongs in the core system, as a variant of an existing one, as a documented pattern, or stays local, and drafts the reply to the requester.
- Write a component release checklist
Writes the definition of done a design-system component must meet before release, covering design, code, accessibility, content, docs, tests and design-code parity, with evidence and owners.
- Write design system release notes
Writes release notes for a design system version, grouped by component, for both designers and developers, flagging breaking and visual changes with migration steps.
- Write a token usage guide
Writes usage documentation for a design system's semantic tokens, explaining what each is for, when not to use it, approved pairings, common misuse and how to choose between similar tokens.
- Write a UI content style guide
Writes the content section of a design system, covering capitalisation, button verbs, error and confirmation patterns, numbers, dates, terminology and accessibility for UI text.
- Write a UX pattern guideline
Documents a reusable UX pattern for a design system, such as bulk actions or filtering, covering the problem, when to use it, components involved, variations, behaviour, content and accessibility.
- Set up Figma variables and modes
Plans Figma variables for colour, spacing, radius and type, with collections, modes for themes, aliasing, scoping, code syntax and naming that matches the code tokens.
- Structure a Figma component library
Plans how a Figma design-system library is organised, covering files and pages, properties versus variants, variables and modes, naming, publishing and consumer habits.
- Audit duplicate UI components in code
Finds near-duplicate UI components and one-off variants in a codebase, groups them by role, and proposes a consolidation plan with migration effort, without changing any code.
- Map design tokens to a Tailwind theme
Maps a design system's tokens into the project's Tailwind theme with semantic colour utilities, spacing, type, radius and dark mode, matching the installed Tailwind version.
- Theme a UI kit to your brand
Maps brand colours, type, radius and shadows onto a UI kit such as MUI, shadcn/ui, Chakra or Mantine, producing the theme file, component overrides and a contrast check.
- Build a business case for a design system
Builds a business case to fund or grow a design system team, with the problem in evidence, costs, conservative benefit estimates, risks, options and a clear ask for leadership.
- Design density modes for a design system
Designs compact, default and comfortable density modes for a design system, with spacing and size tokens per mode, component rules, target-size limits and how users switch.
- Design focus indicators for a design system
Designs consistent keyboard focus indicators across a design system's components and themes, with focus tokens, WCAG contrast and size checks, and tricky cases like inputs and cards.
- Write design system instructions for AI coding agents
Writes an instructions file that teaches AI coding agents to build UI with your design system, covering which components and tokens to use, import paths, forbidden patterns and checks.
Advanced 12
Expert or deep work that assumes the user can judge expert output. Example: Plan croissant lamination.
- Design systems lead
Acts as a design systems lead who runs the system as a product, balances consistency with team autonomy, writes down decisions and judges success by adoption rather than component count.
- Design a dark theme
Designs a dark theme from an existing light palette, covering surface elevation, semantic colour mapping, contrast checks, images, charts and token changes. Use when a design system adds dark mode.
- Plan multi-brand theming
Designs a theming architecture so one component library serves several brands or white-label clients, defining what brands may change, token layers, delivery and testing.
- Generate platform token files
Generates web, iOS and Android token files from a source token file, with naming transforms, theme variants and a check that every alias resolves and every token appears per platform.
- Plan design system governance
Plans how a design system is run, covering ownership, the contribution model, versioning, deprecation, adoption tracking and support. Use when setting up or fixing how a design system is run.
- Define a design token architecture
Designs a three-tier design token architecture (primitive, semantic, component) with naming conventions, theming rules and a sample token file. Use when starting or restructuring a design system.
- Design a component's props API
Designs the public API of a design-system component, covering props, slots or composition, controlled and uncontrolled state, events, naming and escape hatches.
- Plan merging two design systems
Plans consolidating two or more design systems after a merger, reorg or acquisition, comparing them area by area, choosing a target for each and phasing the migration.
- Plan a migration to semantic tokens
Plans moving a codebase from primitive colour tokens to a semantic token layer by reading actual usages, mapping each to a role, isolating ambiguous cases and phasing codemods.
- Plan how to drive design system adoption
Plans how to raise design system adoption across product teams, diagnosing barriers per team and choosing champions, migration help, tooling, incentives and per-team targets.
- Plan a visual refresh rollout through the design system
Plans how a brand or visual refresh reaches every product through tokens and components, with a change inventory, a switchable theme, sequencing, visual QA and rollback.
- Choose a foundation for a component library
Compares building components from scratch, on a headless behaviour library, or on a styled UI kit, scores each against your constraints and recommends one with its exit costs.