Report · marked 9 Oct 2026

pbakaus/impeccable

Ready for an agent to work in without hand-holding.

JavaScript · 78,994 stars · 3,900 files · branch main

87 /100 A

Instructions 27/27Whether the repo tells an agent how to behave before it starts guessing. Full marks.Setup 14/14Whether an agent can install the project and get it running without a human. Full marks.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 9/10How quickly anything new can orient itself. Losing marks on repository description.

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

Fix these first

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.

Repository weight

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

Repository description

Set the description and a few topics. It's the first context anything gets, and it takes ten seconds.

The full marking

Every deduction below names the file or setting it came from.

Instructions 27/27 A+

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12

AGENTS.md is present, which is the format the most tools read.

Also found: CLAUDE.md

✓Instruction quality 12/12

Specific enough that an agent can act on it.

14,430 characters, a workable length

names the actual commands to run

uses headings, so an agent can skim it

includes copyable code blocks

✓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

bun.lock pins the dependency tree.

Found bun.lock

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

package.json scripts (build:skills, build:skills:release, build, build:release, build:extension, package:vscode…)

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 rust-toolchain.toml

–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

2169 test files against 869 source files.

e.g. crates/browser/tests/advisory_contexts.rs, crates/browser/tests/brand_and_vendors.rs, crates/browser/tests/card_heuristics.rs

✓Test command is discoverable 7/7

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

✓Continuous integration 4/4

4 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

biome.json 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 63 patterns.

✗File sizes fit in context 0/6

38 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.

crates/live/assets/detect-antipatterns-browser.js — 2722KB

.agent/skills/impeccable/scripts/live-browser.js — 536KB

.agents/skills/impeccable/scripts/live-browser.js — 536KB

✗Repository weight 0/5

About 649MB 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 — drafted for pbakaus/impeccable

# AGENTS.md

The design language that makes your AI harness better at design.

## Setup

```
bun install
```

## Commands

```
bun build                  # produce a build
bun test                   # run the test suite, must pass before any commit
bun build:skills
bun build:skills:release
bun build:release
bun build:extension
bun package:vscode
bun fetch:engine
```

## Layout

- `crates/`         399 source files
- `tests/`          298 source files
- `scripts/`        36 source files
- `ui/`             16 source files
- `browser-bundle/` 8 source files
- `extension/`      6 source files

## Conventions

- Tests live alongside the code they cover, following `crates/browser/tests/advisory_contexts.rs`.
- CI defines what passing means. See `.github/workflows/ci.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `crates/live/assets/detect-antipatterns-browser.js` is 2722KB. 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/pbakaus/impeccable.md

A draft gets the commands right and stops at the things only a maintainer knows. What a good JavaScript AGENTS.md looks like covers what to add by hand, and what AGENTS.md is explains the format itself.

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/pbakaus/impeccable.svg)](https://agentreadme.com/pbakaus/impeccable)

Other JavaScript repositories, marked

affaan-m/ECC 89 A react/react 71 B+ trekhleb/javascript-algorithms 69 B DietrichGebert/ponytail 74 B+ Snailclimb/JavaGuide 53 C+ airbnb/javascript 54 C+

All JavaScript 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