Verify that implementation looks like the design.
Compare rendered code with its design visual and see whether the implementation matches the design.
Use the rendered implementation as evidence
We compare the component as it actually renders, not just its source. Storybook stories supply the states.
- Review the rendered output.
- Use Storybook states when available.
- Tie each result to a code version.
Compare against the corresponding design visual
The mapped design component is the reference. Each code state is compared with its design state.
- The design is the reference.
- Compare matching variants and states.
- Keep the design version with the result.
Review visual differences in shared context
See visual results next to structural, styling, and token differences, and judge whether a difference is intended or drift.
- Review differences per component.
- Link what you see to other mismatches.
- Designers and developers see the same evidence.
See how the code holds up on phones and tablets
Each component is also drawn at your project's tablet and phone sizes, exactly as your code is, and we report what breaks there. No mobile design needed. In beta, and it never changes the score.
- Wider than the screen, overflowing or overlapping.
- Tap targets and text that get too small.
- Intended overflows, like carousels, stay quiet.
Keep reading on the Cosmic Ledger.
Verify the result, not just the implementation details.
Compare rendered code with the design and decide from shared evidence.

