Guidelines for agents
Plain-Markdown guidelines with an entry point (Guidelines.md), a component catalogue with decision trees, imperative Do / Forbidden rules, and a React API section on every component generated from the TypeScript source.
Atomus is built for humans and agents
Most design systems are written for people and then scraped by AI tools. Atomus is written for both. Every rule a designer or developer reads on this site is also published in a form agents can follow literally. The props, tokens and rules agents use are generated from the same sources as the Figma file and the React package, so they can’t drift.
The result: Claude Code, Cursor, Copilot, Figma Make and the Figma MCP server pick the right component, use only real props, style with semantic tokens and keep one primary action per view. You review the result instead of fixing it.
Available now
Section titled “Available now”Atomus skill
An Agent Skill with the workflow, references (components, tokens by intent, page patterns, Figma) and a validator that flags raw colours, primitive tokens and invented props. npx skills add StanVisionAgency/atomus.
AGENTS.md template
Paste-in rules for product repos that use Atomus, read by Claude Code, Cursor, Copilot and Codex.
llms.txt and Markdown pages
/llms.txt, /llms-full.txt, /llms-small.txt, topic subsets, and every page as Markdown at …/index.md.
Figma MCP rules
How an agent reads Atomus designs through the Figma MCP server: modes on the top frame, Code Connect first, variables to tokens, never paste hex.
Code Connect mappings
All 21 React components are mapped to their Figma component sets, ready to publish to Dev Mode.
Atomus MCP server
Components, props, tokens by intent, page patterns, Figma to code, validation, setup files and brand ramps as MCP tools. Set it up.
ESLint and Stylelint rules
The Atomus rules as lint rules for editors, CI and agent loops, with SARIF output. Lint rules.
shadcn registry
Every component, four app screens, an AI chat block and 30 website sections as source, for the shadcn CLI, the shadcn MCP server and v0. Registry.
Storybook
Stories for every React component with theme, brand and radius switches, a component manifest and an MCP server for agents.
Agent kit
12 components for AI products — prompt input, messages, streaming text, reasoning, tool calls, approvals, citations, suggestions, model selector, feedback, AI label and context meter — on the same tokens and modes. See the Conversation demo.
Coming next
Section titled “Coming next”| What | Status |
|---|---|
npm packages @stanvision/atomus-react and @stanvision/atomus-tokens |
Publishing soon. Until then, install from the repo. |
| Figma Make kit | After the npm packages publish. See Figma Make kit. |
| Evals results | The evals harness scores agent output against the rules (real imports and props, lint, axe, no raw hex). The first scorecard per agent is coming with the first run. |
Start here
Section titled “Start here”Claude Code, Cursor and CopilotInstall the skill, add the AGENTS.md template, validate the output.
Atomus MCP serverComponents, tokens, patterns and validation as tools, local or remote.
Figma MCP and Code ConnectTurn Atomus designs into Atomus code, not div soup.
llms.txtGive any LLM the whole documentation as Markdown.
shadcn registry, MCP and v0Install Atomus components, screens and sections as source with shadcn add.
Agent compatibility (evals)50 prompts and six deterministic scorers, with and without the skill and MCP server.
Rules for agentsThe core rules and the forbidden list every Atomus agent follows.