Why your agent needs measurements, not a screenshot
Words plagio team
A screenshot shows what a page looks like. A spec says how it's built. Agents rebuild from the second far more faithfully.
What a screenshot loses. Pasting a screenshot into Claude or Cursor and asking for "this" works for the outline. The details come back invented: a font that looks close, a grey that's off, spacing in round numbers, no hover states.
| Measured in a browser | From a screenshot | |
|---|---|---|
| Type | Exact font, size and tracking | Some serif, about 5rem |
| Colour | Weighted by how much it's used | Picked by eye |
| Structure | The real markup and CSS | Invented from the pixels |
| Hover states | Measured | Not in the picture |
| Motion | Keyframes and timings | Frozen |
What a spec holds
When plagio captures a component, it reads what the browser rendered: the HTML and computed CSS, the design tokens with colours weighted by use, the type scale, spacing, radii and shadows, hover and focus states, animations with their timing, and a screenshot as a reference. The agent follows that instead of guessing.
When a screenshot is fine
For a rough layout idea or a moodboard, a picture is enough. For anything you'll ship, where the type and spacing are what make it feel designed, give the agent the measurements.
Start from a page you like in Discover, or point plagio at any public URL.
Sources, checked 5 November 2026
Names and products belong to their owners. Prices and features change: if something here is out of date, write to support@plagio.dev and we'll fix it.
Give your agent a real reference.
Start the free week