Explain Interface is an agent skill by Jakub Krehel that explains how something on the web was built, from a live URL or a screenshot.
What it does
Answers either how a whole site was built or how one effect was made.
For a site, covers the framework, styling system, components, tokens, type, color, motion, and breakpoints.
For an effect, lists the layers behind it in paint order, with the technique each one uses.
Says whether it read the page in a browser or from fetched source, and labels what it measured versus inferred.
Ends on what you can take into your own work, not a copied snippet.
When to use it
Reach for it when a site or effect catches your eye and you want to understand the technique behind it.
How to get it
The skill is free on GitHub under the MIT license, in Jakub Krehel's skills repo. You call it by name, as /explain-interface followed by your question; your agent won't start it on its own.
more skills
Explain Interface is an agent skill by Jakub Krehel that explains how something on the web was built, from a live URL or a screenshot.
What it does
Answers either how a whole site was built or how one effect was made.
For a site, covers the framework, styling system, components, tokens, type, color, motion, and breakpoints.
For an effect, lists the layers behind it in paint order, with the technique each one uses.
Says whether it read the page in a browser or from fetched source, and labels what it measured versus inferred.
Ends on what you can take into your own work, not a copied snippet.
When to use it
Reach for it when a site or effect catches your eye and you want to understand the technique behind it.
How to get it
The skill is free on GitHub under the MIT license, in Jakub Krehel's skills repo. You call it by name, as /explain-interface followed by your question; your agent won't start it on its own.
more skills
Explain Interface is an agent skill by Jakub Krehel that explains how something on the web was built, from a live URL or a screenshot.
What it does
Answers either how a whole site was built or how one effect was made.
For a site, covers the framework, styling system, components, tokens, type, color, motion, and breakpoints.
For an effect, lists the layers behind it in paint order, with the technique each one uses.
Says whether it read the page in a browser or from fetched source, and labels what it measured versus inferred.
Ends on what you can take into your own work, not a copied snippet.
When to use it
Reach for it when a site or effect catches your eye and you want to understand the technique behind it.
How to get it
The skill is free on GitHub under the MIT license, in Jakub Krehel's skills repo. You call it by name, as /explain-interface followed by your question; your agent won't start it on its own.

