Report · marked 26 Aug 2026
NervJS/taro
An agent will struggle here, mostly for fixable reasons.
TypeScript · 37,653 stars · 5,102 files · branch main
52
/100
C+
Instructions
2/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on agent instruction file and instruction quality.Setup
12/18Whether an agent can install the project and get it running without a human. Losing marks on environment config and pinned runtime version.Verification loop
22/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Full marks.Context economy
9/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability
5/10How quickly anything new can orient itself. Losing marks on written documentation and license.
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 2/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
2/3
README exists but never explains how to get the thing running.
Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.
Setup 12/18 B
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
pnpm-lock.yaml pins the dependency tree.
Found pnpm-lock.yaml
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
package.json scripts (preinstall, prepare, build, build:serial, build:binding:debug, build:binding:release…)
scripts/ directory
✗Environment config
0/4
Nothing documents the environment this needs. An agent will get a runtime error it can't diagnose.
Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.
✗Pinned runtime version
0/2
No pinned runtime version.
Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.
–Reproducible environment
n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 22/22 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
727 test files against 3725 source files.
e.g. crates/native_binding/__test__/index.spec.mjs, crates/swc_plugin_compile_mode/src/tests/alipay.rs, crates/swc_plugin_compile_mode/src/tests/attributes.rs
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
8 GitHub Actions workflows define what "passing" means.
✓Lint and format rules
3/3
.eslintrc.js encodes the house style.
–Static type checking
n/a
Not applicable — the Rust compiler type checks every build.
Context economy 9/20 C
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 47 patterns.
✗File sizes fit in context
0/6
5 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.
packages/taro-cli-convertor/report/static/js/bundle.js — 1967KB
packages/taro-plugin-react-devtools/src/backend/index.js — 510KB
packages/taro-components-rn/src/components/Picker/regionData.ts — 276KB
✗Repository weight
0/5
About 1596MB 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 开放式跨端跨框架解决方案，支持使用 React/Vue 等框架来开发微信/京东/百度/支付宝/字节跳动/ QQ 小程序/H5/React Native 等应用。 ## Setup ``` pnpm install ``` ## Commands ``` pnpm build # produce a build pnpm test # run the test suite, must pass before any commit pnpm lint # lint pnpm format # format pnpm preinstall pnpm prepare pnpm build:serial pnpm build:binding:debug ``` ## Layout - `packages/` 2876 source files - `examples/` 569 source files - `tests/` 157 source files - `crates/` 117 source files - `scripts/` 2 source files ## Conventions - Tests live alongside the code they cover, following `crates/native_binding/__test__/index.spec.mjs`. - CI defines what passing means. See `.github/workflows/auto-review.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `packages/taro-cli-convertor/report/static/js/bundle.js` is 1967KB. 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/NervJS/taro.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/NervJS/taro)Other TypeScript 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.