explain-interface

Explains how a website or UI effect was built by inspecting live pages or screenshots.

6.7k|239|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/jakubkrehel/skills --skill explain-interface-jakubkrehel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: explain-interface
Source: https://github.com/jakubkrehel/skills/tree/main/skills/explain-interface
Command: npx skills add https://github.com/jakubkrehel/skills --skill explain-interface-jakubkrehel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When you see a gradient, animation, or layout on the web and wonder how it was built, there is no easy way to reverse-engineer it. This Skill inspects a live URL or a screenshot and explains the frontend stack, styling system, or the exact layer stack behind a specific visual effect. ## Core Features & Use Cases - Effect Deconstruction: Identifies the full layer stack behind a visual effect in paint order, including pseudo-elements, filters, blend modes, and animation states, using browser evaluation scripts. - Whole-System Reading: Detects the framework, styling approach, component library, design tokens, type scale, spacing rhythm, breakpoints, and fonts of any site. - Screenshot Reconstruction: When only an image is available, extracts exact colors and contrast values while clearly labeling everything else as ratios or inference. - Use Case: Ask how the hero gradient on a marketing site was built, and receive the oversized element, multi-stop gradient, blur filter, and backdrop-filter layers explained in paint order with measured values. ## Quick Start Ask the assistant to explain how the gradient animation on a specific website URL was built.

Frequently Asked Questions about explain-interface

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find out how a website effect was built?▼

Provide the URL and name the effect, such as a gradient or animation. The Skill runs browser evaluation scripts that search computed styles by property signature, checks pseudo-elements, and reports the full layer stack in paint order with measured values.

How to identify what framework and CSS system a website uses?▼

The Skill detects framework fingerprints like Next.js, Nuxt, Remix, Astro, and Svelte from globals and asset paths, plus styling systems like Tailwind, CSS Modules, and styled-components. Each detection is reported with its evidence rather than as a bare claim.

Can I explain a UI design from a screenshot instead of a URL?▼

Yes, but the answer becomes a reconstruction rather than a reading. Only sampled colors and contrast ratios are exact from pixels; sizes, spacing, and type are reported as ratios, and tokens, breakpoints, and motion cannot be determined at all.

What tools are needed to inspect a live webpage?▼

The Chrome DevTools MCP is recommended, installed via npx chrome-devtools-mcp, providing evaluate_script, resize_page, and screenshot capabilities. Without a browser, the Skill falls back to fetching raw HTML and CSS with curl and grep.

Why does CSS inspection miss some visual effects?▼

Effects often live on pseudo-elements, which getComputedStyle misses without the pseudo argument, or they are not CSS at all. Canvas, WebGL shaders, SVG filters, and video require separate detection, and cross-origin stylesheets cannot be read.