interaction-states-pass

Audits interactive elements for six UI states, transitions, and action feedback.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Mjlike123/ui-prototype-workbench --skill interaction-states-pass-mjlike123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interaction-states-pass
Source: https://github.com/Mjlike123/ui-prototype-workbench/tree/main/.agents/skills/monkren-design/skills/04-review/interaction-states-pass
Command: npx skills add https://github.com/Mjlike123/ui-prototype-workbench --skill interaction-states-pass-mjlike123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interactive elements often ship with missing hover, focus, disabled, or loading states, abrupt transitions, and silent success or failure feedback, which makes interfaces feel broken and hurts accessibility. This Skill systematically audits every interactive element in a design and reports or fixes the gaps. ## Core Features & Use Cases - Element Inventory: Enumerates buttons, links, form inputs, toggles, clickable cards, navigation items, and custom widgets like dropdowns and modals. - Six-State Verification: Checks default, hover, active, disabled, focus, and loading states per element, including focus-visible ring contrast and disabled-state reasoning. - Transition & Feedback Review: Validates transition durations (0.15–0.5s), prefers-reduced-motion handling, and visible success, error, and validation feedback. - Use Case: Before shipping a new settings page, run the pass to catch a submit button with no loading state, a link missing focus styles, and a form that fails silently on validation errors. ## Quick Start Ask the AI to run an interaction states check on the current page and report any missing hover, focus, disabled, or loading states.

Frequently Asked Questions about interaction-states-pass

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check interaction states on a web page?

Run an interaction states audit that inventories every interactive element, then verifies default, hover, active, disabled, focus, and loading states for each. The pass reports missing or unclear states and only fixes them when explicitly requested.

What states should every button have in a design system?

Buttons need default, hover, active, focus, and disabled states, plus loading when they trigger async work. Focus should use :focus-visible with a visible ring, and disabled should explain why via tooltip or inline message.

Does this check accessibility requirements like focus visibility?

Yes, it verifies focus rings meet 3:1 contrast against adjacent backgrounds, are at least 2px with 2px offset, and never rely on bare outline: none. It also checks that transitions respect prefers-reduced-motion.

Will the audit modify my code automatically?

No, the default behavior is report-only, flagging each missing or unclear state with confidence annotations. Fixes using existing design system tokens are applied only when the user explicitly asks.

What transition durations are recommended for UI state changes?

State changes like hover and focus should use 0.15–0.3s, while enter/exit animations for modals and toasts use 0.3–0.5s. Durations over 0.5s on micro-interactions or missing transitions entirely are flagged.