Report · marked 8 Oct 2026

garrytan/gstack

Solid foundations, held back in a few specific places.

TypeScript · 135,630 stars · 3,392 files · branch main

83 /100 A-

Instructions 25/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup 16/20Whether an agent can install the project and get it running without a human. Losing marks on pinned runtime version and reproducible environment.Verification loop 22/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on lint and format rules.Context economy 13/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.

Lint and format rules

A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

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.

The full marking

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

Instructions 25/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: it's 22k characters, which burns context on every single turn.

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 16/20 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, build:cso, format:cso, format:cso:check, typecheck, typecheck:test…)

scripts/ directory

✓Environment config 4/4

.env.example documents what the app needs to 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 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

2303 test files against 1974 source files.

e.g. browse/test/activity.test.ts, browse/test/adversarial-security.test.ts, browse/test/batch.test.ts

✓Test command is discoverable 7/7

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

✓Continuous integration 4/4

26 GitHub Actions workflows define what "passing" means.

✗Lint and format rules 0/3

No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.

A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

✓Static type checking 3/3

Strict type checking is on, which catches a whole class of agent mistakes before they run.

Context economy 13/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 59 patterns.

✗File sizes fit in context 2/6

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

test/helpers/touchfiles-data.ts — 272KB

test/gen-skill-docs.test.ts — 252KB

test/plan-skill-questions.test.ts — 188KB

✗Repository weight 2/5

About 171MB 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 garrytan/gstack

# AGENTS.md

Use Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA

## Setup

```
bun install
```

## Commands

```
bun dev                # run locally
bun start              # run the app
bun build              # produce a build
bun test               # run the test suite, must pass before any commit
bun typecheck          # type check without emitting
bun build:cso
bun format:cso
bun format:cso:check
```

## Layout

- `test/`     1274 source files
- `browse/`   276 source files
- `scripts/`  142 source files
- `lib/`      101 source files
- `design/`   47 source files
- `make-pdf/` 33 source files

## Conventions

- Tests live alongside the code they cover, following `browse/test/activity.test.ts`.
- TypeScript runs in strict mode. Type errors are the fastest feedback available, so do not weaken it.
- CI defines what passing means. See `.github/workflows/actionlint.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `test/helpers/touchfiles-data.ts` is 272KB. It will not fit comfortably in context, so read it in parts.
- Copy `.env.example` before running anything that needs configuration.

---

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/garrytan/gstack.md

A draft gets the commands right and stops at the things only a maintainer knows. What a good TypeScript 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/garrytan/gstack.svg)](https://agentreadme.com/garrytan/gstack)

Other TypeScript repositories, marked

freeCodeCamp/freeCodeCamp 69 B openclaw/openclaw 73 B+ nilbuild/developer-roadmap 45 C deepseek-ai/deepseek-harness 82 A- vuejs/vue 67 B anomalyco/opencode 78 A-

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