OpenCodeGameStudios / src
AGENTS.md93 starsChanged 3 months agoMITView on GitHub
When writing or editing game code in this directory, follow these standards. The LLM's training data predates the pinned engine version. Always check docs/engine-reference/ before using any engine API. Do not guess at post-cutoff API signatures — look them up first. Match the engine-specialist agent to the file type being written. See docs/framework/technical-preferences.md → Engine Specialists → File Extension Routing. When in doubt, use the primary engine specialist configured in docs/framework/technical-preferences.md. Tests live in tests/ — not in src/. Run…
We split this AGENTS.md into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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: line 3
When writing or editing game code in this directory, follow these standards.
- Distinctive: line 9
Do not guess at post-cutoff API signatures — look them up first.
- Distinctive: line 13
All public APIs require doc comments
- Distinctive: line 15
Prefer dependency injection over singletons for testability
- Very specific: line 16
Every new system needs a corresponding ADR in docs/architecture/
- Very specific: line 24
When in doubt, use the primary engine specialist configured in docs/framework/technical-preferences.md.
- Very specific: line 29
Run /test-setup to scaffold the test framework if it doesn't exist yet.
- Distinctive: line 30
Every gameplay system should have unit tests covering its formulas and edge cases.
- Distinctive: line 34
Write tests first when adding gameplay systems.
≈ “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
Source Directory
When writing or editing game code in this directory, follow these standards.
Engine Version Warning
The LLM's training data predates the pinned engine version.
Always check docs/engine-reference/ before using any engine API.
Do not guess at post-cutoff API signatures — look them up first.
Coding Standards
- All public APIs require doc comments
- Gameplay values must be data-driven (external config files), never hardcoded
- Prefer dependency injection over singletons for testability
- Every new system needs a corresponding ADR in
docs/architecture/ - Commits must reference the relevant story ID or design document
File Routing
Match the engine-specialist agent to the file type being written.
See docs/framework/technical-preferences.md → Engine Specialists → File Extension Routing.
When in doubt, use the primary engine specialist configured in docs/framework/technical-preferences.md.
Tests
Tests live in tests/ — not in src/.
Run /test-setup to scaffold the test framework if it doesn't exist yet.
Every gameplay system should have unit tests covering its formulas and edge cases.
Verification-Driven Development
Write tests first when adding gameplay systems. For UI changes, verify with screenshots. Compare expected output to actual output before marking work complete.
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 repository82 other files it gives its agents.
- AGENTS.mdAGENTS.md
- design/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- skill-testing-framework/AGENTS.mdAGENTS.md
- .cursor/rules/ocgs-framework.mdcCursor rule
- adoptSkill
- architecture-decisionSkill
- architecture-reviewSkill
- art-bibleSkill
- art-generateSkill
- asset-auditSkill
- asset-specSkill
- automated-smoke-testSkill
- balance-checkSkill
- bug-reportSkill
- bug-triageSkill
- changelogSkill
- code-reviewSkill
- concept-brainstormSkill
- consistency-checkSkill
- content-auditSkill
- create-architectureSkill
- create-control-manifestSkill
- create-epicsSkill
- create-storiesSkill
- day-one-patchSkill
- design-reviewSkill
- design-systemSkill
- dev-storySkill
- estimateSkill
- exploreSkill
- gate-checkSkill
- helpSkill
- hotfixSkill
- hybrid-prototypeSkill
- init-templateSkill
- launch-checklistSkill
- localizeSkill
- map-systemsSkill
- milestone-reviewSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- playtest-reportSkill
- project-stage-detectSkill
- propagate-design-changeSkill
- prototypeSkill
- qa-planSkill
- quick-designSkill
- regression-suiteSkill
- release-checklistSkill
- retrospectiveSkill
- reverse-documentSkill
- review-all-gddsSkill
- scope-checkSkill
- security-auditSkill
- setup-engineSkill
- skill-improveSkill
- skill-testSkill
- smoke-checkSkill
- The first 60 shown.
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.