agentreadme

Report · marked 25 Aug 2026

twbs/bootstrap

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

MDX · 174,655 stars · 793 files · branch main

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
Environment config
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.

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

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 (start, bundlewatch, css, css-compile, css-rtl, css-lint…)
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.
Found .nvmrc
Reproducible environment 0/2
No container or devcontainer definition.
A Dockerfile or devcontainer removes an entire class of 'it won't install' failures.
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
59 test files against 225 source files.
e.g. js/tests/README.md, js/tests/browsers.js, js/tests/helpers/fixture.js
Test command is discoverable 7/7
An agent can find and run `npm run test`.
Continuous integration 4/4
16 GitHub Actions workflows 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 15/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 33 patterns.
File sizes fit in context 4/6
3 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/js/bootstrap.bundle.js — 203KB
dist/js/bootstrap.js — 142KB
dist/js/bootstrap.esm.js — 133KB
Repository weight 2/5
About 320MB 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 twbs/bootstrap
# AGENTS.md

The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.

## Setup

```
npm ci
```

## Commands

```
npm run start         # run the app
npm run test          # run the test suite, must pass before any commit
npm run lint          # lint
npm run bundlewatch
npm run css
npm run css-compile
npm run css-rtl
npm run css-lint
```

## Layout

- `site/`  146 source files
- `js/`    62 source files
- `build/` 9 source files
- `dist/`  3 source files
- `scss/`  3 source files

## Conventions

- Tests live alongside the code they cover, following `js/tests/README.md`.
- CI defines what passing means. See `.github/workflows/browserstack.yml`, and keep it green.
- 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.
- `dist/js/bootstrap.bundle.js` is 203KB. 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/twbs/bootstrap.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 61 out of 100

[![agent ready](https://agentreadme.com/badge/twbs/bootstrap.svg)](https://agentreadme.com/twbs/bootstrap)

Other MDX repositories, marked

dair-ai/Prompt-Engineering-Guide 61 B- thedaviddias/Front-End-Checklist 85 A inkonchain/docs 52 C+

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