Explain Interface

Explains how a website, a visual effect or an animation was built, from a live URL or a screenshot.

12,359 stars 483 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add jakubkrehel/skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jakubkrehel/skills --skill explain-interface
Manual install
git clone --depth 1 https://github.com/jakubkrehel/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/explain-interface ~/.claude/skills/explain-interface

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Explain interface

This skill answers how something on the web was built. `/explain-interface how the gradient on example.com was built` finds the layers producing that gradient and explains what each one contributes.

It explains rather than judges. There is no verdict, because how someone else built their interface is not a finding. Reviewing against a standard is `interface-review` and `better-interface`, and exploring alternatives for your own is `variant`. Name what you find in the vocabulary of the domain skill that owns it, such as `better-typography` for type or `better-colors` for palette.

## Scope to the question

| The question | What you produce | Method |
| --- | --- | --- |
| How was this **site** built? | The frontend: framework and rendering strategy, styling system, component library, tokens, the type, spacing and color systems, motion, breakpoints, how fonts and images are served | [read-the-system.md](read-the-system.md) |
| How was **this** built? | The layer stack behind one effect, in paint order, with the technique on each layer | [find-the-effect.md](find-the-effect.md) |

Given a named thing, scope to it. A type scale and a token dump are not a longer answer to "how is the gradient built". Pull in a neighbour only where the effect cannot be explained without it, and say why.

Either question can be asked of a screenshot instead of a URL. See **From a screenshot, it is a reconstruction**.

## What you can actually read
Read the full skill on GitHub

Details

Skill name
explain-interface
Path
skills/explain-interface/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Explain Interface skill do?

Explains how a website, a visual effect or an animation was built, from a live URL or a screenshot.

How do I install the Explain Interface skill?

Claude Code plugin: /plugin marketplace add jakubkrehel/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Explain Interface popular?

It lives in jakubkrehel/skills, which has 12,359 GitHub stars and 483 forks.

Related skills

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.