Design review for what dev actually shipped

This page is for designers reviewing dev's implementation against the spec. The same pattern works across the use cases for visual product feedback hub, but design reviews are where the gap between "the design" and "the build" is widest and most worth closing.

The problem

Figma is where the design lives. The built UI lives in the browser. Reviewing what shipped against the spec means flipping between the two, and the feedback usually lands as inline comments on the Figma file, which the dev then has to translate to the actual code. Or, if the team is closer-knit, the feedback goes in Slack with two screenshots side by side: "look how dev did this vs the design." Either way, the comparison is buried in a thread, and the dev's coding agent gets none of it.

The cleaner pattern is a design review captured on the built UI, screenshots of what was actually shipped, annotated with what should have happened. The Figma file is the reference, not the artifact the review lives in.

The CobaltCapture workflow

Open the build in the browser. Capture screen at cobaltcapture.com, pick the window, drag a box around the implementation detail that drifted, the off-spec spacing, the wrong typography weight, the icon that doesn't match. Hit Dictate and talk through what should have happened: "The button radius should be 8px not 12px, this is the secondary style, the primary is 12px and we use 8px everywhere else. Also the hover state is missing the cobalt shift, that should ease in over 150ms."

Repeat for each finding. Publish. The link is the design review.

What the output looks like

The output is markdown with embedded screenshots. Each section is one finding, cropped screenshot of what shipped, source URL of the page, and your dictated rationale as a paragraph:

# Settings page, design review

Source: https://staging.example.com/settings

![Avatar upload button](https://cobaltcapture.com/r/des99821/img/1.png)

The avatar upload uses the primary cobalt button style. This is a
secondary action, should use the ghost button per the design system.
Primary on this page is "Save changes" only.

![Section spacing](https://cobaltcapture.com/r/des99821/img/2.png)

Vertical spacing between sections is 32px in the build, 56px in the
design. Affects the rhythm of the whole page. Worth fixing before the
notifications work goes in.

The dev opens the URL, reads each finding next to the actual page it refers to, and gets the rationale in your words, not summarized into a Figma comment, not condensed for Slack.

Why this beats Figma comments

Figma comments are the right tool for reviewing the design. They are the wrong tool for reviewing the implementation, because the implementation is not in Figma. Asking the dev to translate Figma comments into code changes is a step that loses information every time.

Figma comments also do not survive the agent handoff. If the dev is steering Cursor or Claude Code through the fixes, the agent cannot read Figma comments, they live behind an auth wall the agent does not have. CobaltCapture markdown lives at a public URL that any agent can curl and ingest. That makes the design review part of the Loom alternative category, a portable artifact, not a tool-locked thread.

Who this is for

Designers reviewing dev implementation against the design spec. Design leads doing a final pass before launch. Anyone whose feedback is "the build doesn't match the design" and whose feedback then has to inform a fix, usually by a dev who is increasingly working through a coding agent. If your design reviews are currently dying in Figma comment threads or Slack screenshot pairs, this is the workflow that ships them.