---
id: compiled-context
kind: topic
title: "Compiled, not written, context"
atlas_url: https://designsystems.fly.dev/nodes/compiled-context.md
---

# Compiled, not written, context

Generating agent-facing files from the same sources as the human docs, on every release, so the two cannot drift.

## Edges

- <- about <- AI is accidentally making documentation more accessible, Agentic Design Systems Codebase Navigation, Beyond Design Tokens: Building an AI-Ready Figma Handoff, Component Examples as Data, Components as Data, Design System Doc Spec 0.20.0, Documentation foundations for humans and AI, How We Made Our Design System Bilingual, I’m making a spec for design system documentation, Making product documentation work for humans and AI, On progressive disclosure for AI context, On teaching AI how you work, State of AI in Design Systems — Insights, Storybook 10.3: Component-driven development for humans and agents, Storybook MCP for React, Storybook MCP sneak peek, The Bridge the Standard Cannot Build, The parts of your system you never wrote down, What are hypertokens? The layer between tokens and components, rebuilt for agents.
- <- focus <- Ali Asghar Aamir, Christine Vallaure, David Cai, Dei, Diana Wolosin, Dominic Nguyen, Gantushig Javkhlan, Geri Reid, Kaelig Deloumeau-Prigent, Karl Koch, Kyle Gach, Michael Shilman, Murphy Trueman, Nathan Curtis, PJ Onori, Robin Di Capua
- <- ships <- Astryx, Cloudscape, Design System Doc Spec (DSDS), HeroUI, Mantine, React Spectrum S2, Storybook, Supernova, Trinity (BILL)
- <- within <- Compile them. Hand-written agent docs rot; generated ones cannot drift., The agent-facing file is policy writing, and reads like a rulebook rather than documentation.

## Sources

- https://state-of-ai-in-design-systems.netlify.app/insights