Citations
Every source cited across the wiki, grouped by page, in reading order. Inline citations within each page link the same sources at the point they’re used — this page exists so the reading list can be scanned or followed up on without the surrounding prose.
Each entry ends with its publication year. “Living doc” marks documentation sites and
repositories that are updated continuously rather than published once, and “n.d.” marks
a source with no findable date. A Dated tag marks a source that is old for its area
and describes tools or examples that have since changed. Older sources used only for principles aren’t flagged.
Foundations, token architecture, design-to-code contract
Section titled “Foundations, token architecture, design-to-code contract”- Murphy Trueman,
design-system-ops—knowledge-notes/*.md, the primary source for Part 1 and most of Part 2’s governance mechanics. Living doc. - Nathan Curtis, “Component Contracts and Schemas”, 2026:
READY_FOR_DEVhandoff, keeping contracts current, and ADRs - Design Tokens Community Group, “Design Tokens Specification Reaches First Stable Version”, W3C, 2025: the 2025.10 stable release and the tools that read it
- Figma, “Control opacity at scale”, release notes, 2026: opacity on color variables without detaching
- Tokens Studio, “Modified Colors”, living doc: alpha and mix modifiers, Pro only, resolved to hex on export to Figma
- Design Tokens Community Group, “Design Tokens Format Module 2025.10”, 2025: curly-brace aliases target whole tokens only
- Design Tokens Community Group, “Design Tokens Color Module 2025.10”, 2025: color value structure with optional alpha
- Stuart Robson, “How Colour Works with the DTCG Design Tokens Color Module”, Always Twisted, 2026
- GitButler, design-core PR #47, “write colors aliased with their own opacity as color-mix”, 2026
- figma/plugin-typings issue #381, “opacity on a translucent color source is … silently ignored”, 2026
- Alla Kholmatova, Design Systems: A Practical Guide to Creating Design Languages for Digital Products (O’Reilly, 2017)
- Jina Anne, “Design Systems are for People”, AIGA, n.d.
Token naming
Section titled “Token naming”- Nathan Curtis, “Naming Tokens in Design Systems”, 2020
Dated— predates Figma variables and DTCG resolver files, and treats mode as a naming level; cited for the taxonomy levels, completeness, local-to-global promotion, and polyhierarchy - Nathan Curtis, “Reimagining a Token Taxonomy”, 2022: the Badge and Alert mismatch, the overbroad interactive token, and FigJam dot voting
- Murphy Trueman, “Why design system naming feels impossible”, 2025: trust and friction, abbreviations, and the decision log
- Murphy Trueman,
design-system-ops—knowledge-notes/token-architecture.md, living doc: thecategory.role.variant.statepath - Murphy Trueman,
design-system-ops—skills/token-audit/SKILL.md, living doc: convention consistency, ambiguity flags, platform suffixes, and orphan tokens - Romina Kavcic, “50 design token files, one problem: your agents can’t read the meaning”, 2026: eight names for one role, agents blending conventions, the brand-crimson test, and semantic token counts
- Romina Kavcic, “Name and get your tokens in 5 seconds”, 2025: the generator’s default segment order
Accessible Colors
Section titled “Accessible Colors”- Nathan Curtis, “Color in Design Systems”, 2016
Dated— written against WCAG 2.0 and HSL-lightness naming, before perceptual color spaces like OKLCH were usable in CSS; cited for the principles (tested pairs, reversed pairings, few options) - Nathan Curtis, “Light & Dark Color Modes in Design Systems”, 2017: the Contrast Grid
- Murphy Trueman,
design-system-ops—skills/theme-audit/SKILL.md, living doc: the WCAG 2.2 AA baseline, contrast on resolved values, wide-gamut and alpha handling, dark-mode elevation, and the brand-versus-feedback check - Murphy Trueman,
design-system-ops—skills/token-audit/SKILL.md, living doc: color tokens a shipped theme doesn’t redefine - Romina Kavcic, “50 design token files, one problem: your agents can’t read the meaning”, 2026: color token counts, the brand-crimson test, and Primer’s LLM extension
- Radix Colors, “Understanding the scale”, living doc: the 12 steps and the APCA guarantee
- Radix Colors, issue #41, “Inaccessible color combinations in light theme”, 2024: 283 pairs failing WCAG AA, and Vlad Moroz’s reply on APCA and WCAG-safe hues
- Radix Colors, issue #25, “Is there a preferred disabled color on the scale?”, 2022: no disabled step for solid fills
- Radix Colors, issue #51, “Missing contrast, surface, indicator and track color values”, 2025: Radix Themes values outside the 12 steps
- Carbon Design System, “Color: Overview”, living doc: tokens, roles, and values, and the layering model
- Atlassian Design System, “Color”, living doc: choosing a token instead of a shade, and WCAG AA contrast targets
- Radix Colors, “Create a custom palette”, living doc: introduced with Radix Themes 3.0 in 2024
- Maximilian Blazek, “Generating Accessible Colors for design systems … inspired by APCA!”, Canonical, 2025: WCAG’s false positives and negatives, perceptual color spaces, spacing steps by contrast, and Canonical choosing WCAG
- Vanilla framework, “Color settings”, living doc: Canonical’s WCAG 2.2 AA target
- W3C, “Web Content Accessibility Guidelines (WCAG) 2.2”, 2023: color not the only signal
Accessibility
Section titled “Accessibility”- Murphy Trueman,
design-system-ops—skills/accessibility-per-component/SKILL.md, living doc: the five audit dimensions, the evidence rule, and the extended protocol for complex components - Murphy Trueman,
design-system-ops—sample-outputs/fixture-accessibility-per-component.md, living doc: the Tooltip sample audit - Murphy Trueman,
design-system-ops—skills/cicd-integration/SKILL.md, living doc: automated accessibility scans in CI and what they can’t cover - GOV.UK Design System, “Accessibility strategy”, updated 2024: what the system can’t guarantee, testing with assistive technology, the GDS 30% automated-testing figure, and research with disabled people
- GOV.UK Design System, “Accessibility statement”, updated 2024: published known issues
- Nathan Curtis, “‘Accessible’ Design Systems Don’t Guarantee Accessible Products”, 2018: configure, compose, and customize as the adopter’s three jobs, with Adam Rowe (Morningstar Design System) quoted on screen-reader testing
- W3C, “Web Content Accessibility Guidelines (WCAG) 2.2”, 2023
- European Union, Directive (EU) 2019/882 (European Accessibility Act), 2019 — applies from 28 June 2025
- ETSI, EN 301 549 V3.2.1, 2021 — the EAA’s harmonised standard, referencing WCAG 2.1 AA
- Nathan Curtis, Directed Edges
specs, “ADR 067: Element Behavior Roles viaanatomy.role”, 2026: roles as an authored fact, the three look-alike pills, and thediv-plus-ARIA output without them - Nathan Curtis, Directed Edges
specs, “ADR 068: Form Control and Field Plumbing Role Concepts”, 2026: control and part roles such aslabelanderrormessage - Nathan Curtis, Directed Edges
specs, “ADR 087: Behavior Actions viaanatomy.action”, 2026: role versus action, and the alert’s dismiss button - Directed Edges
specs,Anatomy.ts, living doc: the anatomy element shape, and role lists on composed instances
Layout accessibility
Section titled “Layout accessibility”- Nathan Curtis, “Typography in Design Systems”, 2019: separating heading level from H tag
- W3C, ARIA Authoring Practices Guide, “Landmark Regions”, living doc: keeping all content in landmarks, and labelling landmarks that repeat
- W3C, “Understanding Success Criterion 1.3.2: Meaningful Sequence”, living doc: matching code order to visual order, and CSS positioning as a failure
- GOV.UK Design System, “Page template”, living doc: the skip link, header, main, and footer frame
- Carbon Design System, “UI shell header: Accessibility”, living doc: the built-in header region and skip link, and the one-time annotation per product
- Carbon Design System, “Keyboard accessibility”, living doc: the default navigation order and landmarks
- Cloudscape Design System, “Building accessible experiences”, living doc: heading hierarchy, code order, and the app layout component
- Cloudscape Design System, “Static dashboard”, living doc: ordering dashboard content by importance, and its accessibility guidelines
- Cloudscape Design System, “Configurable dashboard”, living doc: letting users rearrange dashboard items
- Murphy Trueman,
design-system-ops—skills/accessibility-per-component/SKILL.md, living doc: the landmark-regions check for components that fill a page region
Code Composition
Section titled “Code Composition”- Nathan Curtis, “Subcomponents”, 2022
- Nathan Curtis, “Slots in Design Systems”, 2025
- Nathan Curtis, “Configuration Collapse”, 2026
- Brad Frost, Atomic Design, Chapter 2, 2016 — atoms, molecules, organisms
- Radix Primitives, “Composition”, living doc — parts and the
asChildpattern - Radix Primitives, “Dialog”, living doc: the Dialog anatomy example
- Workday Canvas Design System, “Compound Components”, living doc: the compound Tabs example
- MUI, “Button API”, living doc: the
startIconslot prop - Radix Primitives,
create-context.tsx, living doc: the error a part throws outside its parent - Kent C. Dodds, “How to use React Context effectively”, 2021: throwing when a context hook is used outside its provider
- Braid Design System, “Layout”, living doc: layout components own all spacing between elements
- React Spectrum, “Dialog”, living doc: Spectrum 2 Dialog slots, and
CustomDialogfor custom layouts
Figma Composition
Section titled “Figma Composition”- Nathan Curtis, “Architecting Subcomponents”, Schema by Figma, 2022
- Figma, “Taking cues from code”, 2022
- story.to.design, “Subcomponents: How to make your design system more flexible”, 2022
- fourzerothree.in, “Crafting Components with Subcomponents and Nested Instances”, 2025
- Nathan Curtis, “Component Contracts and Schemas”, 2026: the 96-variant disabled example
- Figma Learn, “Use slots to build flexible components in Figma”, living doc: native slots, preferred instances, and what an instance can’t change
- Figma Learn, “The difference between slots, instance swaps, and variants”, living doc: when to use each
- Nathan Curtis, “Slots in Design Systems”, 2025: preferred or permitted children
- Murphy Trueman, “Slots and the control paradox”, 2025: slots replacing the instance-swap workaround
- Nathan Curtis, “The Sorry State of States”, 2024: disabled as its own variant property
Specifications
Section titled “Specifications”- Nathan Curtis, “Component Specifications”, 2023: specs for teams who never meet
- Nathan Curtis, “Components as Data”, 2025: Figma as an output, and the raw color caught in data
- Nathan Curtis, “Component Contracts and Schemas”, 2026: the
sizeenum,READY_FOR_DEV, and contract versus description - Nathan Curtis, “The EightShapes Specs Figma Plugin”, 2023
- Nathan Curtis, “What Specifications Leave Behind”, 2026: the hex-for-token loss and what specs can’t carry yet
- Nathan Curtis, Directed Edges
specs, “ADR 067: Element Behavior Roles viaanatomy.role”, 2026: roles as an authored fact - Shane P Williams, “The Job Nobody Is Hiring For Yet”, 2026: Figma, Storybook, and production each authoritative for a different question
- Romina Kavcic, “Gamechanger: Automatically sync design tokens from GitHub to Airtable”, 2025: the repo as source, docs as a view
- Murphy Trueman, “Your design system is fragmenting into agent files”, 2026: the Storybook Component Manifest
Platform divergence
Section titled “Platform divergence”- Nathan Curtis, “Finding Platform Balance in a Design System”, 2015
- Nathan Curtis, “Component Contracts and Schemas”, 2026
- Nathan Curtis, “Reimagining a Token Taxonomy”, 2022
UI audit
Section titled “UI audit”- Brad Frost, “Conducting an Interface Inventory”, 2015
- 18F Methods, “Interface audit”, living doc
- Obvious University, “How to audit a design system”, updated 2024
- Nielsen Norman Group, “How to Conduct a Heuristic Evaluation”, 2023
- Clearly Design, “Audit before you scaffold: meeting projects where they are”, 2026
Pilot strategy & launch prioritization
Section titled “Pilot strategy & launch prioritization”- Dan Mall, living doc — Superfriendly; primary site for the pilots-and-scorecards methodology cited below via secondary write-ups
- Dan Mall, via UXPin, “On Design Systems: Dan Mall of Superfriendly”, 2017
- Dan Mall, scorecard reproduced by Obvious University, “How to run a design system pilot”, updated 2024
- Big Medium, “Design Systems: Pilots & Scorecards”, 2017 — summarizing Dan Mall’s original pilots-and-scorecards article
- Dan Mall, via NTT Data, “Design that scales: Unlocking design system success with Dan Mall”, 2025
- Dan Mall, “Dan Mall: creating a sustainable design system practice,” Content Strategy Interviews, 2023
Team models, decision governance, component lifecycle & contribution models
Section titled “Team models, decision governance, component lifecycle & contribution models”- Murphy Trueman, “The bidirectional design system: When code talks back to design”, 2025
- Murphy Trueman,
design-system-ops—knowledge-notes/design-to-code-contract.mdandexecutive-communication.md, living doc: service levels for the core team - Nathan Curtis, “Team Models for Scaling a Design System”, 2015
- Nathan Curtis, “The Fallacy of Federated Design Systems”, 2024
- Nathan Curtis, “Defining Design System Contributions”, 2020
- Jina Anne, “The Salesforce Team Model for Scaling a Design System”, 2015 — Salesforce UX
- Jina Anne, “Design Systems and Hybrids”, 24ways, 2017
- Jina Anne, “There Is No Design System”, 24ways, 2019
- zeroheight, Design Systems Report 2026 (147 practitioners) — report.zeroheight.com
- IBM Carbon — deprecation and migration-guide practice, cited as the standard reference for sunsetting. Living doc.
- Martin Fowler, Refactoring: Improving the Design of Existing Code (1999) — the rule of three, credited there to Don Roberts
- Chris Ballantine-Thomas, GOV.UK Design System, “Iterating the GOV.UK Design System contribution model”, 2023
- Brad Frost, Atomic Design (2016), Chapter 5 — Inayaili de León Persson’s Canonical Vanilla Framework (modification/addition/removal decision tree); Alex Schleifer and Jina Bolton quotes; Nathan Curtis’s “living, funded product” line
- Cathy Dutton, “The Problem with Patterns,” A List Apart, 2018
- Ness Grixti, “Rethinking Contribution: Lessons from the Messy Middle of Design Systems”, 2025
- Design System Tactics, “RACI”, 2025
- DesignX, “Design System Governance: An Enterprise Guide”, n.d.
Onboarding adopters
Section titled “Onboarding adopters”- Murphy Trueman,
design-system-ops—skills/onboarding/SKILL.md, living doc: the shared core and role sections, the first two weeks, and marking team policies to confirm - Ness Grixti, “Wise Design System Onboarding”, n.d. — the self-serve Figma course
System Maturity
Section titled “System Maturity”- Huei-Hsin Wang, “Design-System Maturity: A 6-Dimension Framework,” Nielsen Norman Group, 2026
Fostering contribution
Section titled “Fostering contribution”- Amy Hupe, “5 Lessons on Enabling Design System Contribution”, 2019
- Inayaili de León, “Design Systems: How to Foster Participation,” Design Systems London, 2018
- Ness Grixti, “Rethinking Contribution: Lessons from the Messy Middle of Design Systems”, 2025
- zeroheight, Design Systems Report 2026
API Design
Section titled “API Design”- Nathan Curtis, “Configuration Collapse”, 2026
- Supernova, “Building Durable Component APIs for Design Systems”, 2023
- MUI, “API design approach”, living doc
- Wealthfront Engineering, “Building Wealthfront’s multi-platform design system”, 2022
- Murphy Trueman,
design-system-ops,skills/metadata-schema-generator/SKILL.md, living doc: prohibited prop combinations - Murphy Trueman, “Slots and the control paradox”, 2025: deciding what stays locked
- W3C, ARIA Authoring Practices Guide, “Button Pattern”, living doc: toggle buttons and
aria-pressed - W3C, ARIA Authoring Practices Guide, “Tabs Pattern”, living doc:
aria-selectedon the active tab - W3C, ARIA Authoring Practices Guide, “Radio Group Pattern”, living doc:
aria-checkedon each radio, one checked per group - Radix Primitives, “Toggle”, living doc:
pressedandonPressedChange - Radix Primitives, “Toggle Group”, living doc:
valueandonValueChangeon the group - React Aria, “ToggleButton”, living doc: the
isSelectedboolean - React Aria, “TagGroup”, living doc:
selectedKeyson the group - MUI, “ToggleButton API”, living doc: the
selectedprop - Nathan Curtis, Directed Edges
specs, “ADR 067: Element Behavior Roles viaanatomy.role”, 2026: a checkbox’s selected state emitted asaria-selected - Nathan Curtis, “The Sorry State of States”, 2024: error with disabled as a design question
Property Naming
Section titled “Property Naming”- Nathan Curtis, “Crafting Component API, Together”, 2021
Dated— predates Figma’s boolean, text, and instance-swap properties (2022) and slots; cited for the principles, with tool details from Curtis’s 2026 posts - Nathan Curtis, “Code Only” Props in Figma, 2026
- Nathan Curtis, “Component Contracts and Schemas”, 2026:
READY_FOR_DEVin place of a handoff meeting - Supernova, “Building Durable Component APIs for Design Systems”, 2023: consistent names and the
src/imageexception - MUI, “API design approach”, living doc: boolean naming and defaults, boolean vs. enum
- Figma, “Taking cues from code”, 2022
- Figma Learn, “Apply changes to instances”, living doc: which overrides carry across variants and instance swaps
- Figma Learn, “Swap components and instances”, living doc: swapping from the Assets panel keeps only text overrides
- Figma Learn, “Use slots to build flexible components in Figma”, living doc: one slot property across variants
- Nathan Curtis, Directed Edges
specs, “ADR 066: Lossless key formatting”, 2026: what converting layer names to keys loses, and the safe character set - Nathan Curtis, Directed Edges
specs, “ADR 058: Collapsing Wrapped Primitives”, 2026: unstyled wrapper frames dropped from the spec - Murphy Trueman, “What your components look like as data”, 2026: descriptive layer names and enum properties
- Nathan Curtis, “The Sorry State of States”, 2024: ten Figma kits vs. their code, splitting prop-driven states from interaction states
- Nathan Curtis, “Analysis of Variants”, 2025: invalid configurations read from a Figma asset
Usability
Section titled “Usability”- Murphy Trueman, “Why your components break in production (and how to fix it)”, 2025: the five states, data contracts, and containing errors
- Murphy Trueman, “Every component in your design system is a promise”, 2026: the untyped
variantprop and its typed alternative - Carbon Design System, “Overflow content”, living doc: where not to truncate, and “Show more” over fades
- Alice Packard, “12 ways to make your Figma components more delightful to use”, 2022: the star-rating example, top-layer edits, overrides on swap, and auto layout guardrails
- MUI, “API design approach”, living doc: spreading props to the root, forwarding
ref, and controlled components - Nathan Curtis, “The Figma Component Review”, 2022: the review order and the palette-style example
- Nathan Curtis, “Component Examples as Data”, 2026: the empty Card and ready-made examples
- Nathan Curtis, “Configuration Collapse”, 2026
System inventory
Section titled “System inventory”- Murphy Trueman,
design-system-ops—knowledge-notes/component-governance.md, living doc: token-to-component coupling, composition mapping, cross-system dependencies, and the eight lifecycle stages - Murphy Trueman,
design-system-ops—skills/codebase-index/SKILL.md, living doc: the generated inventory with token bindings, the uses/usedBy graph, and the Tooltip example - Romina Kavcic, “Gamechanger: Automatically sync design tokens from GitHub to Airtable”, 2025
- Romina Kavcic, “Building an Agentic Flows Inventory in Airtable”, 2025
- Nathan Curtis, “Reimagining a Token Taxonomy”, 2022: the component audit sheet, the proposed-tokens sheet, and the Airtable preference
- Nathan Curtis, “The Figma Component Review”, 2022: the status and version check
- Nathan Curtis, “Planning a Design System Generation”, 2024: the dependency chain and the generation’s doneness matrix
- Nathan Curtis, “Doneness Matrices”, 2010: the definition and when not to use one
Release management: versioning, changelogs & migration guides
Section titled “Release management: versioning, changelogs & migration guides”- Nathan Curtis, “Versioning Design Systems”, 2018
- Supernova, “8 Examples of Versioning in Leading Design Systems”, 2024
- Design Tokens Substack, “How to Manage Breaking Changes in Design Tokens”, 2026
- zeroheight, “Handling breaking changes in a design system without causing chaos”, 2026 — Shaun Bent
- zeroheight, “Deprecating in design systems: When it’s time to say goodbye”, n.d.
- Carbon Design System, migration guide, archived v10 docs, n.d.
Dated— Carbon v11 replaced v10 in 2022 - Keep a Changelog, living doc
- UXPin, “How to Create a Design System Changelog”, 2025
Dependency observability
Section titled “Dependency observability”- Murphy Trueman, “We know how to build design systems, but we don’t know how to operate them”, 2026
- Spotify Encore — daily version-usage statistics and slot/prop-override analytics, referenced via Murphy Trueman (2026) and Figma, “How Spotify’s design system goes beyond platforms” (2023)
- Dependency-Track documentation, living doc — SBOM-based component analysis, the supply-chain-security analogue of this practice
Case Studies
Section titled “Case Studies”- Ness Grixti, “Wise Multi-Brand Design System — Case Study”, n.d.
- zeroheight, Design Systems Report 2026
- Figma / Design Executive Council — Grammarly champions-network anecdote, via “The new business case for design systems” (2026)
- Chris Ballantine-Thomas, “Iterating the GOV.UK Design System contribution model”, 2023
Long-term Scale
Section titled “Long-term Scale”- Kathrin Schalber, “UXT to Siemens Industrial Experience Migration”, Siemens iX blog, October 2025
- Siemens iX documentation and Siemens iX on GitHub, living docs — open-source, multi-framework (React, Angular, Vue, Blazor) design system
- David Sward, “Solving the Design System Problem When Products Live for Decades,” UXDX EMEA 2026 — cited from the published session description; no public transcript or recording was available at time of writing, so claims drawn from it are flagged inline as his framing rather than independently verified
System Takeover
Section titled “System Takeover”- Murphy Trueman, “Design system archaeology”, April 2026
- Nathan Curtis, “Adopting Design System Generations”, 2024
- Amy Hupe, “Renovating a design system: Why modernization should feel like turning dials, not flipping switches,” zeroheight blog, June 2026 — cited from title/framing only; the post’s body text was not retrievable at time of writing
Communication
Section titled “Communication”- Nathan Curtis, “Design System Communications”, 2019
- Nathan Curtis, “Design System Release Cadence”, 2018
- Nathan Curtis, “Stewarding Design System Contributions”, 2020
- Twilio Paste, GitHub Discussions: Office Hours, living doc
- GOV.UK Design System, “A guide to the design system monthly chat”, living doc
- Acorn Design System (Mozilla), “Office hours”, living doc
- Brad Frost, Atomic Design (2016), Chapter 5 — office hours, state-of-the-union meetings, the Shyp/Micah Sivitz PR-notification example
- Figma / Design Executive Council, “The Future of Design Systems is Marketing”, 2024 — Spotify, News UK examples
- Catriona Shedd, “Design Systems Ambassador at Salesforce”, n.d.
- Omlet, “Scaling adoption and advocacy for an enterprise-wide design system with Guy Segal”, 2024 — Thomson Reuters ambassador pods
- zeroheight, Design Systems Report 2026 — staffing data
Adoption Metrics
Section titled “Adoption Metrics”- Murphy Trueman, “The component adoption gap: understanding the psychology behind design system success”, 2025
- zeroheight, Design Systems Report 2026
- David Vera / zeroheight help centre, “How to measure the dev side of a design system,” n.d. — Pinterest FigStats, Atlassian’s adoption scanner
- Productboard, “How we measure adoption of a design system at Productboard”, 2021
- Mews Developers, “Building a design system adoption metric from production data”, 2025
- Ness Grixti, “The Hidden Work Behind Design System Adoption”, 2025
Documentation coverage
Section titled “Documentation coverage”- zeroheight, Design Systems Report 2026
- Ness Grixti, “The Hidden Work Behind Design System Adoption”, 2025
- Ness Grixti, “Wise Design System Onboarding”, n.d.
Communicating value, estimating ROI & business alignment
Section titled “Communicating value, estimating ROI & business alignment”- zeroheight, Design Systems Report 2026
- Figma / Design Executive Council, “The new business case for design systems”, 2026 — Freshworks, SAP, Hyundai Motor Group, Grammarly, Linear, Notion examples
- Supernova, “Getting Executive Buy-In and Proving ROI of Design Systems”, 2024 — interviews with Lauren LoPrete (Cash App) and PJ Onori (Instacart)
- Supernova, “How to Build a Business Case for Your Design System”, 2024
- Mike Fortuna, “How I Calculated the Business Case for a Design System”, 2024: the per-component cost formula and button example
- Adobe XD, “20 levers for communicating the value/ROI of design”, 2020
- Murphy Trueman,
design-system-ops—knowledge-notes/executive-communication.md, living doc: labelled figures, one loaded rate, and payback from running totals; growth, risk, and cost framing, phased asks, and following a proposal to a decision - Nathan Curtis, quoted in Brad Frost, Atomic Design (2016), Chapter 5 — “a living, funded product with a roadmap & backlog”
Brand alignment
Section titled “Brand alignment”- userQ, “Design Systems vs. Brand Guidelines”, 2025
- Ness Grixti, “Wise Multi-Brand Design System — Case Study”, n.d. — also cited in Case Studies
- DHL Brand Hub, living doc; MetaDesign — DHL, 2019 — brand-management platform, cited as a boundary example rather than a design-system case study
Stakeholder alignment & planning horizons
Section titled “Stakeholder alignment & planning horizons”- Marianne Ashton-Booth, “From Silos to Systems” — UXDX Berlin 2026 talk; ITVX Mosaic design system case study, stakeholder influence/frequency quadrant, Now/Next/Future planning horizons, LeanDS framework
- Marianne Ashton-Booth, “LeanDS Framework”, 2024 —
marianneab.substack.com - Stafford Beer, Diagnosing the System for Organisations (1985) — the Viable System Model, applied to design systems by Ashton-Booth
- Simon Sinek’s Golden Circle (Why/How/What), from Start With Why (2009), applied to stakeholder levels by Ashton-Booth
- zeroheight, Design Systems Report 2026
AI readiness, governance under AI consumption, Agentic Workflows, AI output discipline, scaling AI effort
Section titled “AI readiness, governance under AI consumption, Agentic Workflows, AI output discipline, scaling AI effort”- Romina Kavcic, “Design tokens that AI can actually read”, 2025
- Romina Kavcic, “Should you build an agent for your design system”, 2026
- Murphy Trueman, “Your next design system user is an agent”, 2025
- Murphy Trueman, “Your design system is fragmenting into agent files”, 2026: the Storybook Component Manifest and its MCP add-on
- Murphy Trueman,
design-system-ops—knowledge-notes/ai-readiness.md,agent-orchestration-guide.md,output-discipline.md,mcp-setup-guide.md. Living doc. In September 2026 the MCP guide’s middle layer changed from a system MCP server to repo files with anAGENTS.mdentry point. - Romina Kavcic, “5 MCP Connections Every Design System Team Needs Right Now”, 2025
- Shane P Williams, “Legibility Is the New Governance”, 2026 — Design Systems Collective
- Shane P Williams, “The Informal Contract Is Over”, 2026 — Design Systems Collective
- Shane P Williams, “Drift Doesn’t Announce Itself”, 2026 — Design Systems Collective
- Shane P Williams, “The Job Nobody Is Hiring For Yet”, 2026 — Design Systems Collective
Agent CI Pipelines
Section titled “Agent CI Pipelines”- GitHub, “Safe Outputs”, living doc — GitHub Agentic Workflows documentation
- Sil Bormüller, “Your Design System Is Not Ready for AI Agents”, 2026 — conference write-up carrying Romina Kavcic’s CI trust-tier framework, Jan Six’s GitHub Primer safe-outputs example, and Diana Wolosin’s Indeed pipeline figures, from the AI Design Systems Conference 2026
- Murphy Trueman,
design-system-ops—knowledge-notes/ai-readiness.md. Living doc.
Context engineering, documentation for agents, agentic UI patterns, generative loops
Section titled “Context engineering, documentation for agents, agentic UI patterns, generative loops”- Diana Wolosin, “Design Systems for AI: Introducing the Context Engine”, n.d.
- Murphy Trueman,
design-system-ops,skills/metadata-schema-generator/SKILL.md, living doc: per-valuesemanticguidance in component metadata - Romina Kavcic, “Design tokens that AI can actually read”, 2025: the token
metaexample - Diana Wolosin — benchmark of 8 MCP configurations against 1,056 prompts at Indeed, referenced via Into Design Systems conference, 2026
- Jan Six, Into Design Systems conference, “Build design systems with agents”, 2026
- Carbon Design System, “Carbon for AI”, living doc
- AWS Cloudscape, “User-authorized actions”, living doc
- AWS Cloudscape, “Response regeneration”, living doc
- GitLab Pajamas, “AI-human interaction”, living doc — patterns explicitly flagged by GitLab as still in development
- Atlassian, “Atlassian Design System: building the context engine for the AI era”, 2026
- Microsoft Learn, “Human-centered design for agents”, living doc — flagged on the source page as AI-generated content on an official Microsoft doc, not an individually authored piece
Figma Agent Access
Section titled “Figma Agent Access”- Nathan Curtis, “Figma Specifications on Command”, 2026: MCP vs. mechanical extraction, the button and action list compression figures, AI downstream of specs
- Directed Edges,
specs, living doc:specs-clisetup, personal access token, and licensing - Sil Bormüller,
figma-cliREADME, living doc: connection modes, the self-measured token comparison with API-based MCP, thesnapshot/checkcommands, and reuse handles withinstantiate - Sil Bormüller,
figma-cliroundtrip.js, living doc: the “renders white” failure and the token-layer comparison behindcheck --roundtrip - Nathan Curtis, “What Specifications Leave Behind”, 2026: rendering specs back into Figma, the hex-for-token loss, and what specs can’t carry yet
- Sil Bormüller,
figma-cliSECURITY.md, living doc: what each connection mode touches
Tooling
Section titled “Tooling”Vendor docs and pricing pages, used only for plan, seat, and license details.
- Figma Learn, “Code Connect”, living doc: Organization and Enterprise plans, Full or Dev seat
- Figma Learn, “Guide to the Figma MCP server”, living doc: remote vs. desktop server availability
- Figma Learn, “Claude Code and Figma: Set up the MCP server”, living doc: the Figma plugin for Claude Code
- Figma Learn, “Figma skills for MCP”, living doc: the skill list, and the Organization or Enterprise requirement for
figma-code-connect - Figma Developer Docs, “Write to canvas”, living doc: Full seat to write, Dev seat read-only
- Figma, “Agents, Meet the Figma Canvas”, 2026: free during beta, usage-based later
- Figma Developer Docs, “Rate limits & access” (MCP server), living doc
- Figma Developer Docs, “Rate limits” (REST API), living doc: Starter plan file-read limits
- Figma Developer Docs, “Variables”, living doc: Enterprise only
- Figma Developer Docs, “Library Analytics”, living doc: Enterprise only
- Figma Learn, “View and explore library analytics”, living doc: Organization and Enterprise plans
- Tokens Studio documentation, living doc: Pro-only features
- Specs plugin documentation, living doc: Pro features
- Style Dictionary, living doc
- Terrazzo, living doc: MIT license
- Storybook, “Manifests”, living doc: AI features in preview
- GitHub Agentic Workflows, living doc: supported engines and billing
- Claude Code, “Advanced setup”, living doc: required plans
- Chromatic pricing, living doc: free plan snapshot allowance, paid plan prices
- Changesets, living doc: MIT license
- Airtable pricing, living doc
- PostHog pricing, living doc
A note on sourcing discipline
Section titled “A note on sourcing discipline”Every claim on this site is attributed to a specific person, post, report, or named company outcome — not to “the industry” or an unnamed consensus. Where two sources agree independently, that’s noted as two people reaching the same conclusion separately, not merged into one voice. Where they disagree, both positions are left standing. If a page needed a claim none of its sources actually support, it says so as an open question rather than inventing an answer. See Start here for the full framing.