agentleFS
WhaocaiiWhaocaii/ai-game-skills/AGENTS.md

ai-game-skills

AGENTS.md4 starsChanged 2 months agoMITView on GitHub

This is Whaocaii's AI game skill project. Work on the user's requested scope; do not expand a narrow edit into rebuilding all skills.

The file

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

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Very specific:

    Keep skill names, catalog.json, dependency links and README entries consistent.

    line 5
  2. Distinctive:

    Do not introduce AI short-drama modules unless the user explicitly requests them.

    line 6
  3. Distinctive:

    Write practical decision guidance, concrete examples and observable completion criteria.

    line 8
  4. Distinctive:

    Update CHANGELOG for behavior changes.

    line 10
  5. Very specific:

    Run python3 scripts/validate.py and relevant tests.

    line 11
  6. Distinctive:

    Do not publish or push unrelated changes without task authorization.

    line 12

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

Repository guidance

This is Whaocaii's AI game skill project. Work on the user's requested scope; do not expand a narrow edit into rebuilding all skills.

  • Keep skill names, catalog.json, dependency links and README entries consistent.
  • Do not introduce AI short-drama modules unless the user explicitly requests them.
  • Preserve user-authored changes. The installer must never silently overwrite an existing skill.
  • Write practical decision guidance, concrete examples and observable completion criteria.
  • Explain whether a feature is workflow guidance, a tested script or a tested engine integration.
  • Update CHANGELOG for behavior changes; preserve third-party attribution when introducing external material.
  • Run python3 scripts/validate.py and relevant tests. Actual gameplay or model quality needs separate evidence.
  • Do not publish or push unrelated changes without task authorization.

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.