A prototype and research repository for product teams. Real, clickable prototypes and the design system they are built from, on one site with login, comments and live boards on top. Underneath it is all git and static HTML.
Building the prototypes is the easy part. An agent can produce a convincing screen in a minute, and most teams already have more of them than they can find. What is missing is everything around them: where the last version went, who changed it, which of the four things called "the dashboard" is the one being reviewed, and where the feedback landed. That is what this is. Prototypes live in one place with the design system they are made from, comments stick to the pixels they are about, boards let you run the real screens side by side, and every version is a commit you can walk back to.
It runs on your own box, or on somebody else's. There is no editor to be locked out of and no export to negotiate: a prototype is a folder of static HTML in a git repository you already own.
See it running: demo.augur.works, sign in with
visita@fulla.demo / regadora. It resets every night, so scribble away.
The demo runs Fulla, an invented community garden product. That repo doubles as the starter space, so everything below works against it.
There is no editor. A prototype is briefed, not drawn. You describe the screen the way you would brief a designer, and an agent builds it as a page in the space, using the design system like anyone else on the team.
The brief that made Seed swap:
Seed swap — a noticeboard where members offer saved seeds and claim each
other's. One screen. A board of offer cards: who, what, roughly how many,
which plot they came from — "Fava beans, saved from plot 12, ~40 seeds".
Claiming an offer keeps the card on the board but settles it down visually;
the swap happens at the shed, not in the app. The empty state suggests the
first action instead of apologizing. Warm and hand-made like the rest of
Fulla — use the fulla design system, don't invent new vocabulary. Add the
one-line meta description. No routing, no backend; seed the board with a
handful of believable offers.
That is Claude Code in the capture; any coding agent that can read the contracts in agents/ does the same job. Screens in the demo space carry the session that made them: open the repo and read one. The follow-ups read like design direction, because that is what they are.
Drop a live prototype next to the stickies and drive it. Everyone on the board sees the same screen state. Agents join as pixel mascots and work next to you. Up close: the specimen spins inside its tile, a teammate's cursor works the area, and Menta the agent strolls over to watch.
Shift+C on any prototype opens review mode. A pin sticks to the element it talks about, the thread keeps everyone's face on it, and the design system shows through as a layer.
The same space that holds your prototypes holds your design system. Tokens, base, components, patterns and pages each get a tier, every entry is a plain HTML page you write, and the site renders it with a live preview and the class names it documents. A small registry gives the review overlay the same vocabulary, so a pin on a prototype knows which component it landed on.
Up close, at the tokens depth: paddings shade in place like devtools, and the panel lists the tokens a component drinks with their live values. Token usage is tracked to the pixel across every prototype that links the system.
Under ten seconds from an empty folder to a page in your browser, and that is
a measured number rather than a hopeful one: three runs on a laptop with a fast
connection came in at 7.3s, 9.0s and 9.2s, stopwatch from git clone to a 200
on http://localhost:8788/ serving the real gallery. Most of that is the two
clones, so a slower connection moves the number and nothing else does — the
engine itself is about two seconds from cold to serving.
git clone https://github.com/andratwiro/augur.git
git clone https://github.com/andratwiro/augur-space-fulla.git
cd augur-space-fulla
node ../augur/scripts/dev.mjsThere is no install step and no build step in that list, and that is not an
omission: the engine has no runtime dependencies, so plain node is enough.
What you get is the full shell — the gallery, the library, review mode, boards —
with about a second of hot reload on every save. No login prompt, because a bare
clone has no user list to gate against; add one and the gate turns on.
Prototypes are self-contained static HTML, so index.html also opens straight
from disk. That is fine for your own glance and never a way to show anyone
anything: no chrome, no comments, no boards, and the link works on exactly one
machine.
- A space is a git repo. Your design system and your prototypes, nothing
else. Only the contents of
prototypes/folders and the gallery tiers ever publish. The research notes sitting next to them stay private by construction. - The engine is this repo. It composes spaces into one static site and runs the overlay worker on Cloudflare. It carries no secrets and no content.
- A private deploy shell holds your instance. The engine pin, the user list, every secret. Engine fixes reach your instance by pin bump, never by forking.
- Publishing is
augur publish. Seconds, atomic, straight from your clone. A git push saves and shares work without deploying anything.
INSTALL.md is the recipe, written to be executed top to bottom by a person or an agent. About an hour, most of it waiting on DNS and CI.
- CLAUDE.md, the engine conventions
- agents/, the contracts for agents working in a space
- CANVAS.md, the board engine and how agents co-work on it
- CONTRIBUTING.md, fork to PR, never fork to deploy
MIT for the code. See LICENSE.
The name, the marks in brand/ and the typefaces bundled with them are not part of
that grant — TRADEMARKS.md says what you can do without asking
(fork it, rename it, say what it is) and what needs a word first.