What problem does it solve?
Choosing the right UI interaction pattern is hard because the wrong control hides alternatives, breaks user flow, or adds unnecessary ceremony for the decision the user must make.
Core Features & Use Cases
- Control-pattern selection for decision shape: maps common decision/interaction types (compare, choose one, choose many, sequence, search, edit, confirm, recover) to appropriate patterns like tabs vs pages, dropdown vs combobox, stepper vs wizard, modal vs inline edit, and disclosure/command menus.
- Pattern auditing before implementation: checks that context stays visible, cancel/escape/undo behaviors are defined, loading/empty/error/permission-limited states fit the pattern, and gesture/pointer interactions have keyboard or explicit alternatives.
- Boundaries with adjacent concerns: clearly excludes accessibility compliance (hand off to a11y), user-goal/task definition (task-analysis), feedback timing/state staging (interaction-feedback), and component API/token governance (design-system-architecture and design-module-composition).
Quick Start
Use the interaction-patterns skill to decide whether a combobox, dropdown, or command menu best supports your user’s selection task in a settings screen.