How do you use AGENTS.md for brand?
AGENTS.md is an open format for giving AI agents standing instructions in a Markdown file at the root of a repository. Teams use it, alongside tool-specific files such as CLAUDE.md, GEMINI.md and Copilot instructions, to put brand rules in front of every agent that works in the repo.
Also called: CLAUDE.md for brand, brand rules for coding agents.
Why it matters.
Coding agents read instruction files before they start: AGENTS.md for agents such as OpenAI's Codex, CLAUDE.md for Claude Code, GEMINI.md for Gemini CLI and .github/copilot-instructions.md for GitHub Copilot. As of November 2026, GitHub Copilot's coding agent also reads AGENTS.md, CLAUDE.md and GEMINI.md.
Putting brand rules in these files means anything an agent builds, from a landing page to UI copy, starts from the brand. The catch is that each file is another copy to keep current, and teams with several tools and repositories end up with many.
Example.
How Brail handles it.
Brail keeps AGENTS.md, CLAUDE.md and your other instruction files in step with one versioned source of brand rules, tokens and voice for UI copy, across every repository. When the brand changes, each file is brought up to date, and one that falls behind is flagged.
Questions people ask.
- How do I keep CLAUDE.md and Copilot instructions in sync?
- Either maintain one file and point the others at it, where the tool allows, or keep the brand rules in one versioned source and update every file from it. See how to keep context and skills in sync across AI tools.
- What brand rules belong in AGENTS.md?
- The ones an agent needs while building: design tokens, component rules, voice for UI copy, words to avoid and where approved assets live. Keep long guidelines in linked files.
- Is AGENTS.md only for code?
- It's designed for coding agents working in a repository, but anything they build there, such as pages, emails or docs, benefits from brand rules in it.
Related terms.
- Sync brand across AI tools: You keep context and skills in sync across AI tools by keeping one versioned source, with the brand and its production context, examples of good work, playbooks delivered as skills, the brand kit and the design system, and connecting every tool to it instead of keeping a separate copy in each.
- Brand .md file: A brand .md file is a brand's guidelines written in Markdown so AI tools can read them, often named brand.md or kept in a project's knowledge files.
- SKILL.md: SKILL.md is the file at the heart of an Agent Skill: a Markdown file with a name, a description of when to use it and instructions, which an agent loads only when a task matches.
- Design system sync: Design system sync keeps a brand's design system (tokens, rules, fonts and components) consistent across the places it lives, such as Figma, Claude, Lovable, Canva and the code repository, from one versioned copy.
- Context sync: Context sync keeps the context every agent reads, such as positioning, audiences, messaging, proof points and pricing, on one current, versioned source across every tool and .md file, instead of separate copies pasted into each.