interaction-patternslisted

# Interaction Patterns ## Coverage Choose and audit interaction patterns before implementation. Covers control selection, mode switching, progressive disclosure, modals, drawers, tabs, accordions, command menus, comboboxes, steppers, wizards, inline edit, bulk selection, filters, sorting, gestures, keyboard alternatives, and pattern fit under task pressure. ## Philosophy Most confusing interfaces are not missing components; they chose the wrong pattern for the decision the user has to make. A dropdown hides options that need comparison. A modal blocks context the user needs. A wizard adds ceremony to a task that only needed one form. Choose the pattern from the user's decision shape: compare, choose one, choose many, sequence, search, edit, confirm, or recover. ## Method 1. Name the user decision or action the control must support. 2. Classify the choice set: small, large, searchable, hierarchical, ordered, destructive, reversible, or repeated. 3. Choose the simplest known pattern that keeps needed context visible. 4. Preserve alternatives for keyboard and non-pointer users before handoff to `a11y`. 5. Define what happens on selection, cancel, escape, undo, and invalid action. 6. Check whether the pattern works with loading, empty, error, and permission-limited states. 7. Hand off component API concerns to `design-system-architecture`. ## Evals This skill ships a comprehension-eval artifact at [`examples/evals/interaction-patterns.json`](https://github.com/jacob-bals