MAX-DESIGN
AGENTS.md4 starsChanged 23 days agoMITView on GitHub
These instructions apply when editing the MAX-DESIGN repository itself. Run npm test after changing skills or token examples. Review the diff for clarity, duplication, broken paths, and unintended scope expansion.
We split this AGENTS.md into the rules it gives an agent
6 rules. About 1 is common, 5 are distinctive, and 0 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Read the README and the skill being changed.
- Distinctive: line 16
Never instruct an agent to replace an established design system blindly.
- Distinctive: line 17
Prefer semantic HTML and native platform behavior when practical.
- Distinctive: line 19
Do not claim WCAG conformance, browser testing, or performance results without evidence.
- Common: line 20
Do not include secrets, private user information, or third-party skill content copied wholesale.
- Distinctive: line 24
Run npm test after changing skills or token examples.
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repository instructions for coding agents
These instructions apply when editing the MAX-DESIGN repository itself.
Before editing
- Read the README and the skill being changed.
- Preserve the skill package format: YAML-style front matter, a clear activation section, a workflow, and measurable quality gates.
- Inspect neighboring skills before introducing overlapping guidance.
- Make the smallest complete change that solves the request.
Content quality
- Be concrete, operational, and framework-aware without forcing a framework.
- Separate required behavior from optional techniques.
- Never instruct an agent to replace an established design system blindly.
- Prefer semantic HTML and native platform behavior when practical.
- Distinguish automated checks from manual visual or assistive-technology review.
- Do not claim WCAG conformance, browser testing, or performance results without evidence.
- Do not include secrets, private user information, or third-party skill content copied wholesale.
Verification
Run npm test after changing skills or token examples. Review the diff for clarity, duplication, broken paths, and unintended scope expansion.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository13 other files it gives its agents.
- max-designSkill
- accessibility-auditSkill
- data-visualizationSkill
- design-reviewSkill
- design-systemSkill
- forms-uxSkill
- frontend-designSkill
- information-architectureSkill
- interaction-motionSkill
- max-designSkill
- resilient-localizationSkill
- ui-testingSkill
- ux-writing-contentSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.