Lindi
MargheritaSan Marzano · basil$14.00ADDFor teams
Three roles. One file.
Designers change the product. Engineers review the change. Leads see the record. Nobody hands anything off, because there is nothing to hand.
Designers
Edit the product itself.
The button you restyle is the button. The spacing you fix is the spacing. Your file is never out of date, because your file is production.
- Your changes ship. Your redlines do not have to.
- Same components, same tokens — nothing to re-explain
- Ask the agent for the parts you would rather not draw
- Your teammates are on the same canvas, live
Tonight from the ovenPizzaPastaSalads
MargheritaSan Marzano · basil$14.00ADD
DiavolaNduja · chili honey$16.00ADD
Quattro FormaggiFour cheese blend$17.00ADDEngineers
Review a pull request, not a design link.
A design change arrives the way any change does: a branch, a diff, a description, a request for review. Nothing lands without you, and nothing needs rebuilding from a screenshot.
- Every design change is a PR on a branch
- Diffs, not screenshots. Components, not absolute positions.
- The whole codebase stays open beside the canvas in Code mode
- Your merge rules are the only rules
MergedRestyle dish cell on the Menu screen#412
- components/menu/DishCell.tsx+28 −9
- styles/menu.css+13 −3
<article className="dish-cell">- <Thumb className="size-10 rounded-md" />+ <Thumb className="size-14 rounded-2xl shadow-md" />- <Price className="text-sm" />+ <Price className="text-base font-bold text-brand" /> </article>
✓ dana reviewedmarco merged into main
Leads
See every change, dated and attributed.
One record for design and code, because there is one file. Who changed what, when, and why — and which review let it through.
- Roles: who edits, who reviews, who only looks
- Seats you can count, on a plan you can explain
- A design edit sits next to the merge that shipped it
- Whitelabel when it has to run on your terms
- 12 Aug · 14:02sofiadesignRestyled the dish cell — radius, price weight#412
- 12 Aug · 14:20bellabuildAsked for a tip step; the agent added TipSelector#413
- 12 Aug · 16:05danareviewReviewed #412 and #413 — two comments, both resolved—
- 13 Aug · 09:41marcocodeMerged both into main; the canvas shows ita41f2c
What changes
The handoff, row by row.
| Where | With a handoff | With Lindi |
|---|---|---|
| The spec | A doc, a link, and a meeting to explain both. | The change itself, on the screen, with the diff behind it. |
| The file | A design file and a codebase, kept in sync by people. | One file. The codebase is the design file. |
| The review | A screenshot in a thread, then a rebuild, then a second review. | A pull request. One review, the one your engineers already do. |
| The drift | Every release, the picture and the product move apart. | There is no picture to drift. |
| The record | Versions in one tool, commits in another, and no line between them. | One record: design edits and merges, in order, attributed. |
| The agent | A generator that draws something to be rebuilt. | An agent that edits the same file, and opens the PR. |
Put the whole team in one file.
Lindi is pre-release. Get in line — and bring the engineer who has to review it.