Explain Interface

Find out how a site, effect, or animation was built.

By

Jakub Krehel

Price

Free

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

Matt Pocock

Code Review

Matt Pocock

Review a branch against your standards and the spec.

Matt Pocock

Prototype

Matt Pocock

Answer a design question with throwaway code.

Jakub Krehel

Better Typography

Jakub Krehel

Set the type scale, spacing, and wrapping right.

Matt Pocock

Improve Codebase Architecture

Matt Pocock

Find the refactors that make a codebase easier to change.

Explain Interface

Find out how a site, effect, or animation was built.

By

Jakub Krehel

Price

Free

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

Matt Pocock

Code Review

Matt Pocock

Review a branch against your standards and the spec.

Matt Pocock

Prototype

Matt Pocock

Answer a design question with throwaway code.

Jakub Krehel

Better Typography

Jakub Krehel

Set the type scale, spacing, and wrapping right.

Matt Pocock

Improve Codebase Architecture

Matt Pocock

Find the refactors that make a codebase easier to change.

Explain Interface

Find out how a site, effect, or animation was built.

By

Jakub Krehel

Price

Free

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

Matt Pocock

Code Review

Matt Pocock

Review a branch against your standards and the spec.

Matt Pocock

Prototype

Matt Pocock

Answer a design question with throwaway code.

Jakub Krehel

Better Typography

Jakub Krehel

Set the type scale, spacing, and wrapping right.

Matt Pocock

Improve Codebase Architecture

Matt Pocock

Find the refactors that make a codebase easier to change.