Report · marked 25 Aug 2026

PanJiaChen/vue-element-admin

An agent can work here, but it will waste turns finding its footing.

Vue · 90,208 stars · 307 files · branch master

59 /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 8/18Whether an agent can install the project and get it running without a human. Losing marks on deterministic install and environment config.Verification loop 20/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on tests exist and static type checking.Context economy 20/20Whether the repo fits in a context window, or fights it. Full marks.Navigability 8/10How quickly anything new can orient itself. Losing marks on written documentation.

Higher is better. Accent marks what is costing you most.

Fix these first

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.

Instruction quality

Instructions earn their keep by naming exact commands. 'Run the tests with `pnpm test`' beats three paragraphs of philosophy.

Deterministic install

Commit the lockfile your package manager generates. Without it, an agent's install and your install are different builds, and 'works on my machine' becomes unfalsifiable.

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 8/18 C

Whether an agent can install the project and get it running without a human.

✗Deterministic install 0/6

No lockfile. An agent installing dependencies may not get what CI got.

Commit the lockfile your package manager generates. Without it, an agent's install and your install are different builds, and 'works on my machine' becomes unfalsifiable.

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

package.json scripts (dev, lint, build:prod, build:stage, preview, new…)

✗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 2/2

The language runtime version is pinned.

package.json engines.node >=8.9

–Reproducible environment n/a

Not applicable — a library doesn't need a container to be worked on.

Verification loop 20/25 A-

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✗Tests exist 4/8

7 test files against 219 source files.

Coverage is thin enough that an agent can break real behavior and still see green.

e.g. tests/unit/.eslintrc.js, tests/unit/components/Hamburger.spec.js, tests/unit/components/SvgIcon.spec.js

✓Test command is discoverable 7/7

An agent can find and run `npm run test:unit`.

✓Continuous integration 4/4

.travis.yml defines what "passing" means.

✓Lint and format rules 3/3

.eslintrc.js encodes the house style.

✗Static type checking 2/3

Type checking is configured, but not in strict mode.

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 20/20 A+

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 19 patterns.

✓File sizes fit in context 6/6

No source file is large enough to crowd out a context window.

✓Repository weight 5/5

About 15.4MB checked out, which is comfortable.

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 — drafted for PanJiaChen/vue-element-admin

# AGENTS.md

:tada: A magical vue admin                                                                https://panjiachen.github.io/vue-element-admin

## Setup

```
npm install
```

## Commands

```
npm run dev           # run locally
npm run lint          # lint
npm run build:prod
npm run build:stage
npm run preview
npm run new
npm run svgo
npm run test:unit
```

## Layout

- `src/`            193 source files
- `mock/`           8 source files
- `tests/`          7 source files
- `plop-templates/` 4 source files
- `build/`          1 source file

## Conventions

- Tests live alongside the code they cover, following `tests/unit/.eslintrc.js`.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- Generated output is committed (`build/`). Search will return the compiled copy, so edit the source, not that.
- No lockfile is committed, so an install here may not match what CI produced.

---

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/PanJiaChen/vue-element-admin.md

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

[![agent ready](https://agentreadme.com/badge/PanJiaChen/vue-element-admin.svg)](https://agentreadme.com/PanJiaChen/vue-element-admin)

Other Vue repositories, marked

ElemeFE/element 58 B- bailicangdu/vue2-elm 46 C CorentinTh/it-tools 68 B vbenjs/vue-vben-admin 63 B qier222/YesPlayMusic 53 C+

All Vue repositories

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.

Open an issue, already filled in