agentleFS
Sign inStart free
striderZAstriderZA/OpenCodeGameStudios/docs/AGENTS.md

OpenCodeGameStudios

AGENTS.md93 starsChanged 3 months agoMITView on GitHub

When authoring or editing files in this directory, follow these standards. Use the ADR template: docs/framework/templates/architecture-decision-record.md Required sections: Title, Status, Context, Decision, Consequences, ADR Dependencies, Engine Compatibility, GDD Requirements Addressed Status lifecycle: Proposed → Accepted → Superseded - Never skip Accepted — stories referencing a Proposed ADR are auto-blocked - Use /architecture-decision to create ADRs through the guided flow TR Registry: docs/architecture/tr-registry.yaml - Stable requirement IDs (e.g. TR-MOV-001) that link GDD requirements to stories - Never renumber existing IDs —…

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When authoring or editing files in this directory, follow these standards.

    line 3
  2. Very specific:

    Use the ADR template: docs/framework/templates/architecture-decision-record.md

    line 7
  3. Very specific:

    Never skip Accepted — stories referencing a Proposed ADR are auto-blocked

    line 13
  4. Very specific:

    Use /architecture-decision to create ADRs through the guided flow

    line 14
  5. Distinctive:

    Never renumber existing IDs — only append new ones

    line 18
  6. Very specific:

    Validation: Run /architecture-review after completing a set of ADRs.

    line 26

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

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

Docs Directory

When authoring or editing files in this directory, follow these standards.

Architecture Decision Records (docs/architecture/)

Use the ADR template: docs/framework/templates/architecture-decision-record.md

Required sections: Title, Status, Context, Decision, Consequences, ADR Dependencies, Engine Compatibility, GDD Requirements Addressed

Status lifecycle: Proposed → Accepted → Superseded

  • Never skip Accepted — stories referencing a Proposed ADR are auto-blocked
  • Use /architecture-decision to create ADRs through the guided flow

TR Registry: docs/architecture/tr-registry.yaml

  • Stable requirement IDs (e.g. TR-MOV-001) that link GDD requirements to stories
  • Never renumber existing IDs — only append new ones
  • Updated by /architecture-review Phase 8

Control Manifest: docs/architecture/control-manifest.md

  • Flat programmer rules sheet: Required / Forbidden / Guardrails per layer
  • Date-stamped Manifest Version: in header
  • Stories embed this version; /story-done checks for staleness

Validation: Run /architecture-review after completing a set of ADRs.

Engine Reference (docs/engine-reference/)

Version-pinned engine API snapshots. Always check here before using any engine API — the LLM's training data predates the pinned engine version.

Pinned engines: see docs/engine-reference/<engine>/VERSION.md for each supported engine (godot, unity, unreal, sfml3, raylib, bevy) before suggesting any engine API.

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