Project library

The seven projects

Same contract as the seven build steps: structure in lib/, words in the dictionary, both keyed by the same id. How long a build takes and which parts it needs are the same in every language; what it is called is not. Only Smart Parking Barrier is ready — the other six are honestly labelled preview, which is a product fact rather than a placeholder.

The component vocabulary

Sensor is generic on purpose: distance, soil moisture, motion and temperature share one word and one mark, which keeps seven builds inside one small set instead of growing an icon per part. Push button is the one addition to the nine the inventory names — the reaction game is a person pressing a button when a light comes on, and calling that a sensor would be the kind of small lie that makes a legend untrustworthy.

What the builds teach

Labels rather than sentences, because they sit in chips on a card and in a list on a detail page and both want the same words. A card shows the first three; the detail page shows all of them.

The set

Seen from above, like the canvas: the product has one point of view of a workbench and this is it. The colours are not a new palette — they are lifted verbatim from canvas/parts/, so the servo mark is the blue of the servo on the board and the resistor mark is the beige of the resistor beside it. A mark that used a different green from the board on the canvas would be a second opinion about the same object.

At every size it is used

24px inside a chip, 32 in a component strip, 40 in a checklist row, 48 on a detail page. The stroke is written in box units rather than pixels, so it stays a hairline at all four rather than thinning out at the bottom of the range.

On both grounds

A mark appears on white in a card and on sunken ground in a checklist row. Neither may swallow it — which is why the silhouettes carry a slightly heavier contour than the details inside them.

Why not the canvas parts

canvas/parts/ cannot be reused here and the reverse is also true. Those are scene parts on a real measuring system — a breadboard pitch is 2.54 mm, which is 10 scene units — and a drawing scaled down from there is unreadable at 44px. These are marks: fewer details, thicker relative strokes, no pin-level accuracy. Same hand, different distance.

All seven, side by side

This is why they are reviewed as a set and never one at a time. Approving them individually is how seven drawings become seven styles: each one looks fine on its own, and only the row shows the drift.

Bespoke scenes were chosen over composing each one out of the component marks, so the risk that they end up as seven separate styles is real and had to be closed by hand. Three decisions do it, all taken before any of them was drawn. One ground: every scene is parts laid out on the workbench's own cutting mat, the same mat the canvas draws. One point of view: from above, always, so a pot is a circle and a bottle is a rounded rectangle with a cap. One level of detail: two to four recognisable parts and at most one mark for what the build does — an arc, a pool of light, a drop.

The hero is the same drawing

P-09 is not an eighth illustration. The detail page shows the barrier scene larger, so there is no second drawing that could one day disagree with the card about what this build looks like.

A · The full inventory

All nine fields the brief asks for: the scene, the name, duration, level, step count, the component strip, the concepts it teaches, the status and the action. It answers what is in the box — you can tell at a glance whether a build needs a servo you do not own.

B · The calm grid

The same frame with the components and the concepts taken out, and one sentence put in. It answers what the build does. The bet is that seven of these read as one library while seven of the other read as seven dashboards.

Search and five filters

Try it: narrow by a component you do not own, or ask for something under 30 minutes. The count in the toolbar is the answer to the toolbar, so it sits inside it.

It filters for real. The narrowing lives in lib/projects/filter.ts as pure functions with no React in them, because an agent asked to find a build that uses a servo I already own calls the same code this toolbar calls. Nothing here is a new control either: the field is A-09, the popovers M-05, the checkboxes A-11's compact sibling, the ready toggle A-14. A filter button turns secondary once it is holding something back — the count alone would be one signal, and rule 7 asks for two.

The build already under way

The project card turned on its side, because this one answers a different question: not what is this but where was I. The progress indicator is A-15's compact variant, unchanged — a dashboard that invented a second way of saying 3/7 would have two of them to keep in step the first time the step count moved.

Getting a kit ready

The checklist is A-11 fed, and the direction it uses — CB3 · Inventory row — was settled in Batch 1 for exactly this: a list you run down once before starting, counting stock rather than agreeing to terms. Nothing blocks. The line underneath reports and never warns, even at zero, because an unticked list still starts the build. The steps come from steps.ts — the same seven the workbench rail renders, so a preview cannot promise a build the workbench does not deliver.

Preview project

A sentence, not a box. This is the trap You can continue in guided demo mode set in Batch 2: the message's job is to set expectations calmly, and a warning-shaped container undoes that whatever the words say. Info rather than warning, too — a preview project is not a problem with the build, it is a fact about this release.

How it works

Three numbered discs and a sentence each. No cards: this is the product talking about itself, and rule 4 gives surfaces to the user's input and to countable objects, never to output.