Once UI Blog
Builder stories
Beiträge
Once UI
How Sentry keeps four apps honest
What we built with Claude for Open Source
Once UI joins the Neon Open Source Program
Design tokens your agent can follow
How coding agents read the Once UI component catalog
AGENTS.md for design systems
What is an agentic design system?
Once UI 2.6: it thinks in a cube
Once UI Stack chat: an AI chat with a face
Once UI 2.5: reactions that move
Once UI 2.4: ready for AI apps
Once UI 3.0 beta: one way to say it
Stack languages: your app in Hungarian, or in two
Stack store: your shop on your own site
Liquid Metal: chrome that never sets
Chirio, redesigned
Styled screenshots in Chirio
Once UI 2.3: made for real apps
Frametic is now a video and capture studio
Agents write about 40% less code from Stack
Magic Portfolio, now on Once UI 2
Frametic MCP: let your agent film your site
Once UI Stack: your site as a desktop app
Once UI Stack, redesigned
Stack: teams and billing
Prism Glow: soft prism light behind your sign-in screen
Once UI for React Native: the same props on a phone
Once UI 2.2: chat, forms and mobile
Dither: your own image or video as a dithered print
Once UI 2.1: The pieces apps kept asking for
Once UI 2.0: A system an AI can build with
Once UI 2.0 Alpha: Gemessen, nicht vermutet
Paarweise gestalten: background und onBackground
Colour arrives in pairs
Once UI 1.8: Feinschliff als Feature
Once UI 1.7: Form mit Absicht
Von Produkten zu Systemen: Ein neues Servicemodell
Magic Journal: Ein anderes Medium für Langform-Texte
Supa Social: Der nächste Meilenstein unserer Reise
Once UI ist Open Source. So wollen wir es beibehalten.
Gestaltung einer zeitlosen, KI-nativen Marke
Once UI 1.5: Neugier im Code
Once UI 1.4 Migrationsleitfaden: Das Breakpoint-Objekt
Launches im KI-nativen Zeitalter: Ein Leitfaden für Indie-Builder
Das erste Design-System für Indie-Builder
Builder Stories
Side und Once UI: Von der Café-Website zum Reservierungssystem
SatisPro und Once UI: Smarteres Bewertungsmanagement skalieren
IQON und Once UI: Skalieren mit einem Design-System
Dev: Verbindung von Wissenschaft und Code mit Once UI
JExcellence und Once UI: Experimente in Enterprise-Apps verwandeln
OsmyReal: Start einer Mobile-Gaming-Plattform mit minimalem Codeaufwand
TrademarkTrademark
Ctrl k
Search…
Registrieren
Once UI Blog
Builder stories
Beiträge
Once UI
How Sentry keeps four apps honest
What we built with Claude for Open Source
Once UI joins the Neon Open Source Program
Design tokens your agent can follow
How coding agents read the Once UI component catalog
AGENTS.md for design systems
What is an agentic design system?
Once UI 2.6: it thinks in a cube
Once UI Stack chat: an AI chat with a face
Once UI 2.5: reactions that move
Once UI 2.4: ready for AI apps
Once UI 3.0 beta: one way to say it
Stack languages: your app in Hungarian, or in two
Stack store: your shop on your own site
Liquid Metal: chrome that never sets
Chirio, redesigned
Styled screenshots in Chirio
Once UI 2.3: made for real apps
Frametic is now a video and capture studio
Agents write about 40% less code from Stack
Magic Portfolio, now on Once UI 2
Frametic MCP: let your agent film your site
Once UI Stack: your site as a desktop app
Once UI Stack, redesigned
Stack: teams and billing
Prism Glow: soft prism light behind your sign-in screen
Once UI for React Native: the same props on a phone
Once UI 2.2: chat, forms and mobile
Dither: your own image or video as a dithered print
Once UI 2.1: The pieces apps kept asking for
Once UI 2.0: A system an AI can build with
Once UI 2.0 Alpha: Gemessen, nicht vermutet
Paarweise gestalten: background und onBackground
Colour arrives in pairs
Once UI 1.8: Feinschliff als Feature
Once UI 1.7: Form mit Absicht
Von Produkten zu Systemen: Ein neues Servicemodell
Magic Journal: Ein anderes Medium für Langform-Texte
Supa Social: Der nächste Meilenstein unserer Reise
Once UI ist Open Source. So wollen wir es beibehalten.
Gestaltung einer zeitlosen, KI-nativen Marke
Once UI 1.5: Neugier im Code
Once UI 1.4 Migrationsleitfaden: Das Breakpoint-Objekt
Launches im KI-nativen Zeitalter: Ein Leitfaden für Indie-Builder
Das erste Design-System für Indie-Builder
Builder Stories
Side und Once UI: Von der Café-Website zum Reservierungssystem
SatisPro und Once UI: Smarteres Bewertungsmanagement skalieren
IQON und Once UI: Skalieren mit einem Design-System
Dev: Verbindung von Wissenschaft und Code mit Once UI
JExcellence und Once UI: Experimente in Enterprise-Apps verwandeln
OsmyReal: Start einer Mobile-Gaming-Plattform mit minimalem Codeaufwand
Guide
Once UI

AGENTS.md for design systems

AGENTS.md is where coding agents look for a project's rules. What a design system should put there, what to leave out, and what npx once-ui-init-agent writes for you.
Updated 19 days ago
How coding agents read the Once UI component catalog
What is an agentic design system?
TrademarkTrademark
Once UIDokumentationBlog
© Once UI. Alle Rechte vorbehalten.
Built with Aveiro
Most coding agents read a file at the root of your project before they touch it. Codex, Cursor, Copilot, Gemini CLI and Zed read AGENTS.md. Claude Code reads CLAUDE.md. Whatever is in that file is the first thing the agent knows about your project, every session. For a design system that is the most valuable spot in the repository. It is also easy to waste.

Why the file matters for UI

An agent without design rules writes UI the way the average of its training data writes UI: utility classes, a div with a border, a hex colour that looks close enough. Every screen is plausible and none of them match. The rules that prevent that are short. Use these components, not raw HTML. Use these spacing tokens, not pixel values. Pair a background with its matching foreground. Import the provider from here, not there. They fit on one screen, and an agent that has read them makes far fewer of the mistakes a reviewer would otherwise catch by hand.

What to put in it

A pointer, not the manual. Every file an agent reads is sent again on every later turn of the conversation, so a long AGENTS.md costs you on every message. Keep the section short and point at the detailed files the agent should open for the task at hand. The task routes. "Building a pricing page? Read this bundle." An agent that goes straight to the right reference reads less and guesses less. The two or three rules that break silently. In Once UI, the clearest one is that a Next.js app must import LayoutProvider from @once-ui-system/core/next. Nothing errors without it, but internal links reload the page. Rules like that belong in the file itself, because an agent will never find them by trial. How to check the work. The command that validates a file, so the agent runs it before it says it is done.

What to leave out

The full component reference, the props of every component, and anything the agent can read from the types. Those belong in files the agent opens when it needs them, not in the one it reads every time.

What once-ui-init-agent writes

npx once-ui-init-agent
It writes a Once UI section into AGENTS.md and CLAUDE.md and adds a Cursor rule. The section sits between markers, so the rest of your file stays as it is and a second run changes nothing. If your CLAUDE.md already imports AGENTS.md, it is left alone, so the rules don't load twice. The section tells the agent to pick the task bundle closest to what it is building and read it in one step, to start a signed-in app from the working starter that ships in the package instead of writing the shell from scratch, and to validate what it wrote: Everything it points to ships inside the package, so the rules always match the version you installed.

Start here

If you use a coding agent with Once UI, run the command once per project and commit the result. The docs for AI coding agents list every file the section points to, and what an agentic design system is explains why they exist.
Read the agent docs
npx once-ui-validate-ai-code path/to/file.tsx