NewenergyEricNewenergyEric/art-director-skill/AGENTS.md

art-director-skill

AGENTS.md5 starsChanged 34 days agoMITView on GitHub

This repository packages art-director at the repository root and the optional skills/game-art-production companion. They share project packs; do not duplicate aesthetic rules. It also contains deterministic tools for building project-specific art-direction skills.

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,774 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 repository2 other files it gives its agents.
- art-directorSkill
- game-art-productionSkill

The file

We split this AGENTS.md into the rules it gives an agent

12 rules. About 1 is common, 8 are distinctive, and 3 are very specific to this project.

≈1
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Keep the frontmatter description concrete about when the skill should be used.
line 8
Very specific:
Put long methods in references/, reusable records in templates/, and deterministic operations in scripts/.
line 9
Distinctive:
Do not make the entrypoint depend on an absolute path or on the original development checkout.
line 10
Distinctive:
Keep project style, entity identity, task variation, and technical facts separate.
line 15
Very specific:
Do not upgrade proposed, unknown, or unchecked material to approved status without an actual decision record.
line 16
Distinctive:
Keep the core CLI compatible with Python 3.10+ and the standard library.
line 22
Distinctive:
Default to refusing destructive overwrites of builds, archives, and existing project packs.
line 23
Distinctive:
Update tests when a change affects the pack contract, validation rules, command output, or relocatability.
line 24
Very specific:
Run python -m unittest discover -s tests -v.
line 25
Distinctive:
Use repository-relative paths in documentation and fixtures.
line 29
Common:
Do not commit customer names, customer assets, private project decisions, credentials, or local machine paths.
line 30
Distinctive:
Keep Chinese and English README claims aligned.
line 31

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

AGENTS.md

Guidance for agents working in this repository

This repository packages art-director at the repository root and the optional skills/game-art-production companion. They share project packs; do not duplicate aesthetic rules. It also contains deterministic tools for building project-specific art-direction skills.

Keep the skill discoverable

SKILL.md is the entrypoint. Its frontmatter name must remain art-director.
Keep the frontmatter description concrete about when the skill should be used.
Put long methods in references/, reusable records in templates/, and deterministic operations in scripts/.
Do not make the entrypoint depend on an absolute path or on the original development checkout.

Preserve the evidence model

style-pack.json is the source of truth for a project pack. STYLE.md and the project SKILL.md are derived outputs.
Keep project style, entity identity, task variation, and technical facts separate.
Do not upgrade proposed, unknown, or unchecked material to approved status without an actual decision record.
A successful schema or file check is not visual approval.
Examples are fictional fixtures. Do not turn their visual choices into universal art direction.

Changing code or templates

Keep the core CLI compatible with Python 3.10+ and the standard library. Pillow may remain optional for pixel checks.
Default to refusing destructive overwrites of builds, archives, and existing project packs.
Update tests when a change affects the pack contract, validation rules, command output, or relocatability.
Run python -m unittest discover -s tests -v; validate both examples/harbor-studio-draft and examples/campaign-studio-draft; then build the mother Skill archive before release.

Public repository hygiene

Use repository-relative paths in documentation and fixtures.
Do not commit customer names, customer assets, private project decisions, credentials, or local machine paths.
Keep Chinese and English README claims aligned.
Regenerate README motion assets from motion/src/ with the scripts in package.json when their copy or visual system changes.

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free