Suede AI Interface Explain Skills Understand what makes the interface work.
Bring an interface question: why a header sticks, how a panel opens, where a filter gets its state, or what controls a responsive layout. The skill traces the existing implementation and explains the causal path with source locations. Browser observations and inferred behavior are labeled separately, and application files stay unchanged.
"Explain this interface and trace the mechanism in the source."->/suede-interface-explainThe workflow router selects this task when the skill is available.
Follow the mechanism
Locate the source entry points and dependencies relevant to the user's question.
Trace inputs, event handlers, state transitions, layout rules and rendered output.
Cite concrete file locations for mechanism claims.
Explain the causal sequence in plain language, using a diagram when it makes that sequence easier to follow.
Know what the evidence shows
Source facts describe what the inspected code declares.
Rendered observations describe behavior actually seen in the available interface.
Inferences identify conclusions that still depend on runtime, data or environment assumptions.
Unobserved states stay explicit; source inspection does not earn a rendered visual pass.
Read-only by default
The explanation preserves the existing interface. It does not refactor, rebuild, add a demonstration route or perform live transactions. If source access is unavailable, it can explain observed behavior while identifying the mechanism details that remain uncertain.
The output follows the question's scope. A design review, workbench or implementation is a separate task with its own entry point.
Example request
Use $suede-interface-explain to explain how this filter panel opens, updates the URL and restores its state. Trace the relevant files, event handlers, state and rendering. Keep application files unchanged. Separate source facts, observed browser behavior and inference, and say which parts you could not observe.
This documentation-only skill lives under skills/suede-interface-explain/. Keeping it in the repository prepares it for future full-pack distribution; it does not install dependencies or activate the skill globally. Installation into an agent is a separate action.
Related skills
Suede AI Design Skills: Review flows and UI diffs, or build within your existing brand. Prioritize task success, hierarchy, tokens, accessibility and rendered visual evidence.
Suede AI Component Lab Skills: Build a dev-only component workbench with real imports, synthetic stress fixtures and live variants. Check states before changing production UI.
Suede AI Code Skills: Code review and ship grade in one run: severity-ranked findings with file and line evidence, plus an A to F grade capped by the weakest of seven lanes.
Suede AI Copy Skills: Conversion copy for landing sections, email, microcopy, buttons, headlines and CTAs, with one pass per surface and a score on every piece.
Suede AI Workflow Skills: Workflow skills router that picks the one specialist for your outcome across copy, design, review, SEO, launch and growth, then loads only that skill.
Install this skill
The repository includes this skill in full-pack discovery. Install a revision containing it to use the new entry point. Claude Code takes two commands the first time and one after that; Codex installs the same pack natively.