Explain Interface — Evidence-Based Visual Reverse Engineering

When to use it

Useful for learning how a visual effect works before adapting its principles. User-invoked explanation, not a design verdict or copied implementation. Browser access can inspect computed styles and active motion; fetched CSS cannot establish winning rules. Screenshot-only results are reconstructions, not proof of source implementation. Cross-origin stylesheets, canvas and shaders can limit inspection. Source reviewed only; not installed or runtime-tested. GitHub stars measure the whole repository.

Compatible agents

Claude Code

Installation

Run npx skills add jakubkrehel/skills and select explain-interface. Claude Code alternatively supports /plugin marketplace add jakubkrehel/skills and /plugin install interfaces@interfaces. Reload, then invoke /explain-interface with a specific URL, effect or screenshot. Keep adjacent method/reference files.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Oct 30, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.