Agent Instruction Files for Builders
Agent instruction files turn project rules, design choices, brand voice, workflow steps and review checks into context an agent can use.
Why instruction files matter
Agents work better when the project explains itself. A clear instruction layer can tell the agent what the site is for, which files matter, how pages should read, how design should behave and which checks must run before work is considered complete.
Files worth creating
AGENTS.md
Use this for project rules, tool preferences, working boundaries, QA steps and instructions that should apply across a workspace.
design.md
Use this for colors, typography, layout rules, visual choices, components and mobile behavior.
Writing rules
Use this for banned phrases, tone, style, formatting and audience rules.
Workflow playbooks
Use these for repeatable tasks such as page creation, publishing QA, form checks, image handoff and local render testing.
What to include
- The audience and job of the project.
- The public brand name and terms to avoid.
- The files that own copy, design, pages, forms and publishing records.
- The checks that must pass before a page moves forward.
- The tools the agent may use.
- The actions that require user approval.
Review loop
Treat instruction files like working software. Review them after every major page, form, design or publishing change. Keep rules short enough to use during real work.
Start with one instruction file, one design file and one workflow checklist. Then connect them to the MCP and use-case pages so the system stays readable.