Start here
Overview
BricoWerx keeps the code your team has already proven as versioned bricks, so people and assistants reuse it instead of rebuilding it.
Most teams have solved the same problems many times: authentication, a waitlist, a notification inbox, a discount engine. Each time the solution is rebuilt from memory, or copied by hand and then left to drift. BricoWerx changes the first question from “how do we build this?” to “do we already have a brick for this?”. If you don’t, you build the brick once, capture it, and every later project reuses it.
A brick is a self-contained module with a manifest that says what it is, what it needs and where it goes. Bricks live in a Vault, which is a plain git directory of versioned snapshots. BricoWerx is not a code generator, a helper library or a boilerplate. It turns finished engineering work into assets you can find, version and install.
The ecosystem at a glance
There are three ways to make a brick, one place where bricks live, and one way to install them. Every tool below feeds the Vault or reads from it.
brico extract and brico capture lift a module out of a project you already have.index.json · shared with brico publish / brico pullbrico.json.Lets AI assistants search the Vault before they write new code.
The tools
brico ui: a full-screen view of the Vault with details, doctor and extract built in.AvailableThe VaultImmutable versioned snapshots in git. Local first, shareable through any git remote.PreviewBuilderA spec-driven, AI-assisted author for new bricks. Every line must pass type checks and tests.PreviewScanner extensionA Chrome extension that maps the routes, API calls and features of a running web app.PreviewWorkerBuilds Scanner captures into type-checked bricks and publishes them to the Vault.PlannedMCP serverVault search for Claude, Cursor and any assistant that speaks the Model Context Protocol.ReferenceBrick rulesR1–R12: what makes a brick portable, and the gates that check it.What the status labels mean
| Label | Meaning |
|---|---|
| Available | Shipped in the current release and covered by tests. Safe to rely on, within the limits on the Security page. |
| Preview | Works end to end and you can use it today, but its interface and deployment may still change. |
| Planned | Designed and on the roadmap, not built yet. The page describes the intended behaviour. |
Where to start
- You have a project with a module worth reusing. Follow Getting started, which installs the CLI and walks through capture and add.
- You want a new brick that doesn’t exist yet. Open the Builder.
- You want to understand the model first. Read Core concepts, then the brick rules.
- You are evaluating BricoWerx for a team. Read the security model and status and roadmap. They state plainly what is and isn’t built yet.