explain-interface

Provide the URL and the Skill searches the page by CSS property signature, checking elements and their ::before/::after pseudo-elements for background-image, filter, and backdrop-filter values. It reports the full layer stack in paint order with the technique behind each layer.

The Skill runs fingerprint checks for Next.js, Nuxt, Remix, Astro, Svelte, Tailwind, CSS Modules, styled-components, and component libraries like Radix. Each detection is reported with its evidence, such as /_next/static asset paths, rather than as a bare claim.

Yes, but the result is a reconstruction rather than a reading. Only colors and contrast ratios are exact from pixels; sizes, spacing, and type are ratios since capture scale is unknown, and tokens, breakpoints, and motion cannot be determined at all.

No. Without a browser, the Skill fetches raw HTML and linked stylesheets with curl and greps for utility classes, inline gradients, :root tokens, media queries, and framework fingerprints. A browser is still preferred for computed values, paint order, and runtime-injected styles.

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