Chapter 01 of 04
The brief
Design review usually ends in a screenshot with an arrow on it, and whoever picks it up has to guess which element was meant.
This is a dev-only overlay that ends it in a markdown block instead: click an element, say what should change, queue it, and copy one review that names every element precisely enough for a designer or a coding agent to act on without guessing. 0 dependencies, 1 file to copy in, no account, no backend, no build step.
The failure is ordinary and everywhere. Somebody walks a page, spots twelve things, and sends a screenshot per thing. Whoever picks them up has to re-find each element, work out which of four nested divs was meant, and infer the intent from an arrow. Half the notes are about spacing nobody can measure from an image.
The other half of the problem arrived with coding agents. An agent can act on a review directly, but only if the review names things precisely: a component, a source line, a selector, the actual computed values. A screenshot carries none of that, so a human has to translate every note before any of it can be worked on.
[ element-review-inspector on GitHub ][ lightbox on GitHub ]
Chapter 02 of 04
The problem
End a design review in something the next person can act on, rather than a screenshot with an arrow on it and a guess about which element was meant.
Chapter 03 of 04
The build
- Frontend Engineering
- Reads React Server Components, which is the part comparable tools get wrong: they walk the client fiber, and on a Next App Router page that finds SegmentViewNode and nothing else, because a server component never gets a fiber. This reads fiber._debugInfo as well, so the review names a real component and source line.
- Product Strategy
- Chose the output format as the product. The artefact is one markdown block sized for whoever acts next, so the same review works for a human designer and for a coding agent with no second version of it.
- Web Design
- Designed an overlay that sits on top of any site without inheriting its styles or fighting its z-index, and that reports box, typography and contrast in the terms a reviewer already thinks in.
- Backend Engineering
- Wrote the MCP bridge that hands the review to Claude Code or Cursor, and lightbox's on-demand proxy, which adopts a dev server that is already listening rather than starting a second one.
Build notes. How it came together.
Chapter 04 of 04
What it did
Open source and in daily use on this site.
It answers the 2 accessibility failures a screenshot cannot show, contrast ratio against AA and position in the focus order, by reading the live DOM rather than a design file. Its companion, lightbox, boots every front end you have built at once, one review port each, and injects the same overlay into every page so the notes land in a folder tagged with the repository they came from.
Both are in daily use on this site, and the review overlay was used while auditing the pages it now documents. Both are MIT on public repos, so a reader can open the source and judge it for themselves rather than take it on trust.
- 0
- Dependencies1 file, no backend, no build step
- 2
- A11y checks answeredcontrast against AA, and focus order
- MIT
- Licencepublic repo, readable source


