Report · marked 25 Aug 2026
phaserjs/phaser
An agent can work here, but it will waste turns finding its footing.
JavaScript · 40,207 stars · 3,609 files · branch master
63
/100
B
Instructions
3/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on agent instruction file and instruction quality.Setup
14/14Whether an agent can install the project and get it running without a human. Full marks.Verification loop
22/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on static type checking.Context economy
11/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability
10/10How quickly anything new can orient itself. Full marks.
Higher is better. Accent marks what is costing you most.
Fix these first
01
Agent instruction file
Add an AGENTS.md at the root: what the project is, how to install, how to run, how to test, and the two or three conventions a newcomer always gets wrong.
02
Instruction quality
Instructions earn their keep by naming exact commands. 'Run the tests with `pnpm test`' beats three paragraphs of philosophy.
03
File sizes fit in context
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
The full marking
Every deduction below names the file or setting it came from.
Instructions 3/27 F
Whether the repo tells an agent how to behave before it starts guessing.
✗Agent instruction file
0/12
None found. Every agent that opens this repo starts from zero.
Add an AGENTS.md at the root: what the project is, how to install, how to run, how to test, and the two or three conventions a newcomer always gets wrong.
Looked for AGENTS.md, CLAUDE.md, .github/copilot-instructions.md, .cursorrules
✗Instruction quality
0/12
Nothing to judge, since there are no instructions.
Instructions earn their keep by naming exact commands. 'Run the tests with `pnpm test`' beats three paragraphs of philosophy.
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 14/14 A+
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
package-lock.json pins the dependency tree.
Found package-lock.json
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
package.json scripts (beta, help, build, watch, watchns, dist…)
scripts/ directory
–Environment config
n/a
Not applicable — this reads as a library, with no environment to configure.
✓Pinned runtime version
2/2
The language runtime version is pinned.
Found .nvmrc
–Reproducible environment
n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 22/25 A
Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.
✓Tests exist
8/8
1106 test files against 3305 source files.
e.g. scripts/tsgen/test/bin/game.js, scripts/tsgen/test/bin/game.js.map, scripts/tsgen/test/output.txt
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
1 GitHub Actions workflow define what "passing" means.
✓Lint and format rules
3/3
.eslintrc.json encodes the house style.
✗Static type checking
0/3
No static type checking.
A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.
Context economy 11/20 B-
Whether the repo fits in a context window, or fights it.
✓No committed build output
6/6
No generated directories committed.
✓.gitignore hygiene
3/3
.gitignore covers 17 patterns.
✗File sizes fit in context
0/6
8 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
dist/phaser.esm.js — 8345KB
dist/phaser.js — 8338KB
dist/phaser-arcade-physics.js — 7746KB
✗Repository weight
2/5
About 479MB checked out. Large enough that cloning and searching are both slow.
Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.
Here is your AGENTS.md
Drafted from what is actually in this repository: the install
command from your lockfile, the commands you already declare, your real directory layout. Anything
marked TODO needs a person. Save it at the root as AGENTS.md.
# AGENTS.md Phaser is a fun, free and fast 2D game framework for making HTML5 games for desktop and mobile web browsers, supporting Canvas and WebGL rendering. ## Setup ``` npm ci ``` ## Commands ``` npm run build # produce a build npm run test # run the test suite, must pass before any commit npm run lint # lint npm run beta npm run help npm run watch npm run watchns npm run dist ``` ## Layout - `src/` 2182 source files - `tests/` 1099 source files - `scripts/` 13 source files - `config/` 3 source files - `dist/` 3 source files - `types/` 3 source files ## Conventions - Tests live alongside the code they cover, following `scripts/tsgen/test/bin/game.js`. - CI defines what passing means. See `.github/workflows/lock-comments.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - Generated output is committed (`dist/`). Search will return the compiled copy, so edit the source, not that. - `dist/phaser.esm.js` is 8345KB. It will not fit comfortably in context, so read it in parts. --- Drafted by agentreadme.com from what is in this repository. Everything marked TODO needs a human. Check it in as AGENTS.md at the root.
Open the raw markdown
or
curl -o AGENTS.md agentreadme.com/draft/phaserjs/phaser.md
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/phaserjs/phaser)Other JavaScript repositories, marked
Think this mark is wrong?
Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.