v0.15.0 · 4 tools, 60+ rules, 13 scores

A repository structure for your code.

Detect, classify, ship. usebrick.dev turns an LLM-augmented codebase into one that knows its frameworks, patterns, smells, and the rules that catch them.

MIT 13.4 kB no telemetry Node ≥ 20
the platform

Four tools. One platform. Zero slop.

Every tool reads the same JSON Schemas and writes the same shape. Click a brick to crack it.

pickbrick

Pick the right patterns from a curated catalog of frontend, backend, and full-stack recipes. Calibrated against 100+ production codebases.

click to crack

mendbrick

Migrate legacy code to modern patterns. The repair tool that scores its own confidence on every change it proposes.

click to crack

slopbrick

The CLI. Detect, classify, score, and report. 60+ rules, 13 scores, JSON Schemas, MCP server. The moat itself.

click to crack

core

The shared spec. inventory, constitution, structure, and health JSON Schemas that every tool reads and writes.

click to crack
try it

Run it. Right here.

The full CLI runs in your terminal. So does this one. Click in, type a command, press Enter.

~ /your-repo
the difference

Static analysis, but it structures.

Linters check syntax. We check architecture. usebrick.dev reads your repo once, writes a structure file, and never re-discovers what it already knows about you.

usebrick
Calibrated against 100+ production codebases
4 JSON Schemas, one contract: Inventory, Constitution, Structure, Health.
MCP server. Your editor, our structure.
Confidence-scored every change it proposes
Cross-language JSON Schemas, not just TypeScript types
everything else
Re-scans the same file 47 times per session
Rules with FP rates you have to memorize
Vendor lock-in to a single editor
"100% coverage" with the floor(0.5) rounding bug
TypeScript types that lie about the JSON
calibrated, not guessed

The numbers that earn the name usebrick.

0
aiQuality
good
0
engineeringHygiene
strong
0
security
solid
0
repositoryHealth
ready to ship
/your-repo/.usebrick/structure.json 
  "version": "3",  "generatedAt": "2026-06-29T04:42:14.730Z",  "workspace": "/your-repo",  "aiQuality": 87,  "engineeringHygiene": 92,  "security": 95,  "repositoryHealth": 91,  "issueCounts":     "high": 3,    "medium": 12,    "low": 47
Every rule ships with a recall/FP ratio. A rule that fires more noise than signal goes back to defaultOff until it earns its way on. the usebrick calibration contract
ship it

Stop guessing your codebase.
Start structuring it.

13.4 kB on npm. One command to install, one to scan, one JSON to ship. MIT, no telemetry.

github