Develop · Build
How it came together.
- 01
Make the output the product
The decision that shapes everything else is that the artifact is one markdown block, not a dashboard or a ticket queue. Markdown is the format a designer can read and an agent can consume without a second version existing. So there is no export step, no integration to configure, and no account: the review is text, and text goes wherever it is needed.
Product Strategy - 02
Read the components the framework actually renders
Comparable tools walk the client fiber tree. On a Next App Router page that finds SegmentViewNode and very little else, because a server component never gets a fiber at all, so the review ends up naming anonymous divs. This reads fiber._debugInfo as well, which is where the server-side component identity survives, and that is the difference between a note saying div.flex and one saying ChapterTeaserCard.tsx line 41.
Frontend Engineering - 03
Answer the two failures a screenshot cannot show
Contrast ratio and focus order are the accessibility problems that are invisible in an image and settled instantly by a pass over the live DOM. Every queued element reports its measured contrast against the AA threshold and its position in the tab order, so a review catches the things a visual check structurally cannot.
Web Design - 04
Boot every project at once, rather than one at a time
lightbox is the second half: a hub that starts each project's own dev server on demand, next dev or vite or astro or storybook, waits for it to answer, and proxies it with the same overlay injected. A server already listening is adopted rather than duplicated. Routes group into families by first path segment, so fifty pages that are one layout with different data can be skipped through a template at a time.
Backend Engineering - 05
Zero dependencies, because of what it is for
A tool whose job is booting other people's projects cannot arrive with a dependency tree that argues with theirs. Both run from a clone with nothing installed, and inspect-comment is one file you copy in. The constraint is not minimalism for its own sake; it is what makes the thing safe to drop into a codebase you did not write.
Product Strategy