{"slug": "design-md-claude-md-agents-md-the-agent-context-file-family", "title": "DESIGN.md, CLAUDE.md, AGENTS.md: The Agent-Context File Family", "summary": "A developer introduces the Agent-Context File Family: CLAUDE.md, AGENTS.md, and DESIGN.md, which are plain-text, repo-resident files that provide persistent context for AI coding agents. CLAUDE.md and AGENTS.md cover code and project conventions, while DESIGN.md handles visual identity and design systems. The separation allows teams to adopt each file independently, starting with the one that addresses their biggest pain point.", "body_md": "**DESIGN.md, CLAUDE.md and AGENTS.md are plain-text, repo-resident files that give AI coding agents persistent context.** CLAUDE.md and AGENTS.md cover code and conventions; DESIGN.md covers the visual identity. Complementary layers an agent reads on every interaction.\n\n``` php\nCLAUDE.md / AGENTS.md  -> code & project context\n                          (stack, conventions, commands)\nSKILL.md               -> on-demand capabilities\nDESIGN.md              -> the design system\n                          (tokens + rationale)\n```\n\nEach handles a different concern, and they do not overlap.\n\nSeparation keeps each focused and lets you adopt them independently. A team might start with CLAUDE.md for code context, add DESIGN.md when agent-generated UI drifts off-brand, and layer in skills later. All plain text, so they version and review like code.\n\nThe cleanest setup wires them: a CLAUDE.md that tells the agent to read DESIGN.md for UI work links code context to design context. The agent gets one coherent picture - how to write the code and how to make it look right.\n\nStart with the file that solves your biggest pain:\n\nMost teams end up with more than one, added as the need appears.\n\n**One universal format?** AGENTS.md is closest to a cross-tool standard for code context; DESIGN.md is the emerging standard for design context.\n\n**Can I have all three?** Yes - code context, capabilities, and design context, each in its own file.\n\nThe pattern is the same across all of them: persistent, plain-text, repo-resident context an agent reads every time. DESIGN.md is the design member of the family.\n\n**Free starter:** The format, a complete annotated example, and the core idea are on a free cheat sheet: [DESIGN.md Quick-Start Cheat Sheet](https://promptmasterstore.gumroad.com/l/design-md-cheat-sheet)\n\n**Go deeper:** The full guide covers the entire format — the token schema, the CLI in depth, accessibility, Tailwind and DTCG export, agent integration, and a complete walkthrough: [DESIGN.md: The Complete Guide to Design Systems for AI Agents](https://promptmasterstore.gumroad.com/l/design-md-guide)\n\nHow many of these files are in your repos already - none, one, or the full set? Curious where everyone is on this.", "url": "https://wpnews.pro/news/design-md-claude-md-agents-md-the-agent-context-file-family", "canonical_source": "https://dev.to/promptmaster/designmd-claudemd-agentsmd-the-agent-context-file-family-3651", "published_at": "2026-06-27 08:16:26+00:00", "updated_at": "2026-06-27 08:34:02.947158+00:00", "lang": "en", "topics": ["developer-tools", "artificial-intelligence", "large-language-models", "ai-agents"], "entities": ["CLAUDE.md", "AGENTS.md", "DESIGN.md", "PromptMasterStore"], "alternates": {"html": "https://wpnews.pro/news/design-md-claude-md-agents-md-the-agent-context-file-family", "markdown": "https://wpnews.pro/news/design-md-claude-md-agents-md-the-agent-context-file-family.md", "text": "https://wpnews.pro/news/design-md-claude-md-agents-md-the-agent-context-file-family.txt", "jsonld": "https://wpnews.pro/news/design-md-claude-md-agents-md-the-agent-context-file-family.jsonld"}}