explain-interface

Inspect the layer stack rather than a single element. Web gradients are usually several layers: an oversized element, a multi-stop gradient at low alpha, and a large blur filter. This Skill searches computed styles by property signature, including pseudo-elements, and reports each layer in paint order.

Check for fingerprints in the HTML and runtime: __NEXT_DATA__ or /_next/static for Next.js, __NUXT__ for Nuxt, utility classes like bg-linear-to for Tailwind v4, and data-radix attributes for Radix primitives. Each fingerprint should be reported with its evidence, since a fingerprint is not a fact.

Yes, but the result is a reconstruction, not a reading. Only colors and contrast ratios are exact from pixels; sizes are ratios because capture scale is unknown. Tokens, frameworks, breakpoints, and motion cannot be determined from an image, so a live URL is preferred when available.

Effects often live on ::before and ::after pseudo-elements, which getComputedStyle ignores unless the pseudo is passed as the second argument. Animation libraries also leave idle values like filter: blur(0px) on many elements, which must be filtered out to find real effects.

Fetched HTML and CSS cannot tell you which rule won the cascade, what was injected at runtime, actual paint order, live animation state, or computed pixel values. It does expose all responsive variants and every :root token, which a single-viewport browser session misses.