Report · marked 25 Aug 2026

swc-project/swc

Solid foundations, held back in a few specific places.

Rust · 34,192 stars · 42,719 files · branch main

72 /100 B+

Instructions 24/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality and readme as an entry point.Setup 8/14Whether an agent can install the project and get it running without a human. Losing marks on discoverable commands.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 5/20Whether the repo fits in a context window, or fights it. Losing marks on no committed build output and file sizes fit in context.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

Discoverable commands

Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.

No committed build output

Add these to .gitignore and `git rm -r --cached` them. Generated files pollute search results, so an agent grepping for a function finds the compiled copy and edits the wrong file.

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 24/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 10/12

Specific enough that an agent can act on it.

Worth fixing: has no code blocks.

3,977 characters, a workable length

names the actual commands to run

uses headings, so an agent can skim it

✗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 8/14 B-

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

✓Deterministic install 6/6

cargo.lock pins the dependency tree.

Found cargo.lock

✗Discoverable commands 0/6

No declared commands. An agent has to infer how to build and run this from the file tree.

Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.

–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 .node-version

–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

41733 test files against 33524 source files.

e.g. .github/swc-ecosystem-ci/tests/concurrently.ts, .github/swc-ecosystem-ci/tests/node-fs-extra.ts, .github/swc-ecosystem-ci/tests/peerjs-server.ts

✓Test command is discoverable 7/7

An agent can find and run `cargo test`.

✓Continuous integration 4/4

16 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

clippy.toml encodes the house style.

–Static type checking n/a

Not applicable — the Rust compiler type checks every build.

Context economy 5/20 F

Whether the repo fits in a context window, or fights it.

✗No committed build output 0/6

Generated output is committed: node_modules/, coverage/.

Add these to .gitignore and `git rm -r --cached` them. Generated files pollute search results, so an agent grepping for a function finds the compiled copy and edits the wrong file.

✓.gitignore hygiene 3/3

.gitignore covers 44 patterns.

✗File sizes fit in context 0/6

126 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/swc/benches/assets/vue-id.ts — 13772KB

crates/swc_ecma_minifier/benches/full/typescript.js — 10696KB

crates/swc_ecma_minifier/benches/full/antd.js — 6529KB

✗Repository weight 2/5

About 465MB 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.

File tree exceeded GitHub's limit, so 53,073 entries were sampled

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 swc-project/swc

# AGENTS.md

Rust-based platform for the Web

## Setup

```
cargo build
```

## Commands

```
cargo test   # run the test suite
```

## Layout

- `crates/`   33393 source files
- `bindings/` 69 source files

## Conventions

- Tests live alongside the code they cover, following `.github/swc-ecosystem-ci/tests/concurrently.ts`.
- 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/swc/benches/assets/vue-id.ts` is 13772KB. 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/swc-project/swc.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/swc-project/swc.svg)](https://agentreadme.com/swc-project/swc)

Other Rust repositories, marked

ultraworkers/claw-code 69 B farion1231/cc-switch 64 B rustdesk/rustdesk 68 B openai/codex 82 A- rust-lang/rust 65 B tauri-apps/tauri 62 B

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

This repository is large enough that GitHub truncated the file listing, so the file-level checks ran on a sample.