--- title: Your Design System Needs a Version for Everyone Else description: Non-technical teams like marketing, sales and ops now use AI coding agents to build decks, dashboards and internal tools, but they can't use a design system... canonical: https://daily.dev/posts/your-design-system-needs-a-version-for-everyone-else-gbljvhrlg twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Your Design System Needs a Version for Everyone Else | daily.dev og:description: Non-technical teams like marketing, sales and ops now use AI coding agents to build decks, dashboards and internal tools, but they can't use a design system... og:url: https://daily.dev/posts/your-design-system-needs-a-version-for-everyone-else-gbljvhrlg og:image: https://api.daily.dev/og/posts/GbljVHrlG.png og:image:alt: Your Design System Needs a Version for Everyone Else og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Your Design System Needs a Version for Everyone Else **[Headway](https://daily.dev/sources/headway)** · 8 min read · 1 upvotes · 2 comments ## Summary Non-technical teams like marketing, sales and ops now use AI coding agents to build decks, dashboards and internal tools, but they can't use a design system built for developers. The fix is a single DESIGN.md markdown file holding design tokens and visual rules that any agent can read, with no repo access or install required. Without it, agents guess at colors and spacing, producing drift that nobody catches because these teams skip code review. The post recommends tracking these users alongside adoption through engagement, and offers a design system MCP as a next step for teams building in the same stack as the component library. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What should I put in a DESIGN.md file for non-developers using AI coding agents? A DESIGN.md should hold your design tokens and visual rules in plain markdown that any agent can read, without requiring repository access or installs. Start with tokens like colors and spacing since they fix the recognition issues that break fastest, then add the rules someone would absorb working alongside the design team for a month. Keep it lean, since every added section is more for the agent to process and makes it worse for someone just building a slide deck. _Teams standardizing AI-generated work on brand guidelines can track this kind of practical write-up on daily.dev._ ### Why does AI-generated UI from a coding agent not match our company's design system? An agent asked for UI elements with no reference material will guess, producing raw hex codes instead of color tokens, pixel padding instead of a spacing scale, and border radius values pulled from nowhere. It looks close enough on screen, and the non-technical person reviewing it has no reason to check the code, so drift compounds quietly until a customer notices two inconsistent products from the same company. _Developers tracking how AI-assisted design drifts from a system's rules can follow more of this reasoning on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@nark3d** · 0 upvotes > A DESIGN.md for the deck-makers is cheap to write and I'd ship it, but what happens when the tokens in it and the component library disagree. The markdown has no build behind it, so it'll drift the moment a token changes and the drift won't show up outside the product team, which is the same silent failure you're describing in the agents. How would the file get regenerated from the source of truth? **@demovexa** · 0 upvotes > The same gap shows up in video. Marketing and sales now ask agents for launch clips, social videos and demo snippets too, and a DESIGN.md written for decks and pages usually says nothing about motion: how the logo comes in, how long a title card holds, the caption font and size, what the end card says. A short section of video rules in the same file keeps agent-made clips from drifting away from everything else the company ships. I'm building DemoVexa, which turns a product's code into demo videos, and we set those rules once per product as a brand kit:... ## Similar posts on daily.dev - [DESIGN.md vs. Design System MCP: Which Does What?](https://daily.dev/posts/design-md-vs-design-system-mcp-which-does-what--kgeeofyhy) · Headway · 108 upvotes · 8 comments - [Atlassian’s DESIGN.md is here: what we learned testing portable design context in practice](https://daily.dev/posts/atlassian-s-design-md-is-here-what-we-learned-testing-portable-design-context-in-practice-nnf3qta24) · Atlassian · 2 upvotes · 1 comments - [Design Systems for AI Agents: How to Make Yours Agent-Ready](https://daily.dev/posts/design-systems-for-ai-agents-how-to-make-yours-agent-ready-stcywhhbg) · Headway · 0 upvotes · 0 comments --- Tags: [#ui-design](https://daily.dev/tags/ui-design), [#mcp](https://daily.dev/tags/mcp), [#design-systems](https://daily.dev/tags/design-systems) [View this post on daily.dev](https://daily.dev/posts/your-design-system-needs-a-version-for-everyone-else-gbljvhrlg) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Your Design System Needs a Version for Everyone Else","url":"https://daily.dev/posts/your-design-system-needs-a-version-for-everyone-else-gbljvhrlg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/your-design-system-needs-a-version-for-everyone-else-gbljvhrlg"},"datePublished":"2026-10-26T22:03:01.122Z","dateModified":"2026-10-26T22:14:00.862Z","description":"Non-technical teams like marketing, sales and ops now use AI coding agents to build decks, dashboards and internal tools, but they can't use a design system...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8e9117514556f96dd5aeb04740d3c317?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8e9117514556f96dd5aeb04740d3c317?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Headway","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Headway","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/6db6367290f142ec95e820d83985679d","url":"https://daily.dev/sources/headway"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/your-design-system-needs-a-version-for-everyone-else-gbljvhrlg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"ui-design,mcp,design-systems","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Headway","item":"https://daily.dev/sources/headway"},{"@type":"ListItem","position":3,"name":"Your Design System Needs a Version for Everyone Else"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/your-design-system-needs-a-version-for-everyone-else-gbljvhrlg","comment":[{"@type":"Comment","text":"A DESIGN.md for the deck-makers is cheap to write and I’d ship it, but what happens when the tokens in it and the component library disagree. The markdown has no build behind it, so it’ll drift the moment a token changes and the drift won’t show up outside the product team, which is the same silent failure you’re describing in the agents. How would the file get regenerated from the source of truth?","datePublished":"2026-10-30T11:24:39.290Z","url":"https://daily.dev/posts/GbljVHrlG#c-Y4jSLtCHK","author":{"@type":"Person","name":"Adam","url":"https://daily.dev/nark3d","image":"https://avatars.githubusercontent.com/u/2162621?v=4"}},{"@type":"Comment","text":"The same gap shows up in video. Marketing and sales now ask agents for launch clips, social videos and demo snippets too, and a DESIGN.md written for decks and pages usually says nothing about motion: how the logo comes in, how long a title card holds, the caption font and size, what the end card says. A short section of video rules in the same file keeps agent-made clips from drifting away from everything else the company ships. I’m building DemoVexa, which turns a product’s code into demo videos, and we set those rules once per product as a brand kit: https://demovexa.com/blog/brand-kit-product-videos?utm_source=dailydev\u0026amp;utm_medium=community\u0026amp;utm_campaign=comments","datePublished":"2026-10-27T02:59:51.308Z","url":"https://daily.dev/posts/GbljVHrlG#c-2X8TlcaN2","author":{"@type":"Person","name":"DemoVexa","url":"https://daily.dev/demovexa","image":"https://media.daily.dev/image/upload/s--I0Ym8soj--/f_auto,pg_1/v1792077531/avatars/avatar_F6wD6jMSPjwEMcztjwnyE?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/your-design-system-needs-a-version-for-everyone-else-gbljvhrlg#faq","mainEntity":[{"@type":"Question","name":"What should I put in a DESIGN.md file for non-developers using AI coding agents?","acceptedAnswer":{"@type":"Answer","text":"A DESIGN.md should hold your design tokens and visual rules in plain markdown that any agent can read, without requiring repository access or installs. Start with tokens like colors and spacing since they fix the recognition issues that break fastest, then add the rules someone would absorb working alongside the design team for a month. Keep it lean, since every added section is more for the agent to process and makes it worse for someone just building a slide deck. Teams standardizing AI-generated work on brand guidelines can track this kind of practical write-up on daily.dev."}},{"@type":"Question","name":"Why does AI-generated UI from a coding agent not match our company's design system?","acceptedAnswer":{"@type":"Answer","text":"An agent asked for UI elements with no reference material will guess, producing raw hex codes instead of color tokens, pixel padding instead of a spacing scale, and border radius values pulled from nowhere. It looks close enough on screen, and the non-technical person reviewing it has no reason to check the code, so drift compounds quietly until a customer notices two inconsistent products from the same company. Developers tracking how AI-assisted design drifts from a system's rules can follow more of this reasoning on daily.dev."}}]} ```