aseprite-automation
AGENTS.md25 starsChanged 20 days agoMITView on GitHub
Read @RULES.md if exists, to align communication style, collaboration specification, as well as other matters. Read @CONTEXT.md for the project scope and shared domain language. Use @ARCHITECTURE.md for the current system view and the relevant records in docs/adr/ for architecture decisions and their rationale. Read docs/test-standards.md before you write or change a test. README.md is user-facing onboarding (installation, usage, and contributing). Read the sections relevant to the task; read the full file when the task requires it. Read @STATE.md and…
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 31,700 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.
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Read @RULES.md if exists, to align communication style, collaboration specification, as well as other matters.
- Very specific: line 5
Read @CONTEXT.md for the project scope and shared domain language.
- Very specific: line 9
Read docs/test-standards.md before you write or change a test.
- Distinctive: line 12
Read the sections relevant to the task.
- Distinctive: line 16
Read @STATE.md and @PITFALLS.md if they exist.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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
Primary
Read @RULES.md if exists, to align communication style, collaboration specification, as well as other matters.
Read @CONTEXT.md for the project scope and shared domain language. Use
@ARCHITECTURE.md for the current system view and the relevant records in docs/adr/
for architecture decisions and their rationale.
Read docs/test-standards.md before you write or change a test.
README.md is user-facing onboarding (installation, usage, and contributing).
Read the sections relevant to the task; read the full file when the task requires it.
State and pitfalls
Read @STATE.md and @PITFALLS.md if they exist.
Environment variable names
Name every environment variable defined by SPA with the SPA_ prefix. Preserve
the names of variables defined by Aseprite, the operating system, or external tools
when integrating with them; for example, ASEPRITE_USER_FOLDER and PATH.
Agent skills
Issue tracker
Issues and PRDs are tracked in GitHub Issues. See docs/agents/issue-tracker.md.
Triage labels
Triage uses the five canonical role labels. See docs/agents/triage-labels.md.
Domain docs
This repository uses a single-context layout. See docs/agents/domain.md.
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.