跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

interaction-patterns-components

Use when choosing, critiquing, or designing UI interaction patterns and reusable components for web, mobile, SaaS, dashboards, or design systems.

hueyexe · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add hueyexe/frontend-agent-skills --skill interaction-patterns-components

技能说明


name: interaction-patterns-components description: "Use when choosing, critiquing, or designing UI interaction patterns and reusable components for web, mobile, SaaS, dashboards, or design systems." license: MIT metadata: author: hueyexe

Interaction Patterns Components

Purpose

Help an agent choose, critique, and design effective UI interaction patterns and reusable product components.

The skill covers navigation patterns, menus, cards, tables, dashboards, modals, flows, states, and component behavior. It treats visual polish only where it affects interaction clarity, hierarchy, accessibility, or component usability.

When to use this skill

Use this skill when the user asks for any of the following:

  • Critique, redesign, or UX review of an app screen, website, product flow, wireframe, component, or frontend implementation.
  • Selection of UI patterns such as navigation, menus, breadcrumbs, dashboards, cards, tables, forms, modals, wizards, split panes, tabs, accordions, toolbars, hover tools, lists, grids, or feedback states.
  • Design of reusable components or design-system behavior.
  • Frontend guidance for interaction behavior, accessibility, responsive behavior, component APIs, or UI state handling.
  • Creation of product UX recommendations where the best answer depends on tasks, user skill, device context, data complexity, or risk.

When not to use this skill

Do not use this skill as the main framework when the user primarily needs:

  • Brand identity, illustration, mood boards, or visual polish not tied to interaction clarity.
  • Deep copywriting, messaging strategy, or content design beyond labels, help text, errors, and microcopy.
  • Pure graphic design, logo design, or marketing creative.
  • Native voice, AR/VR, spatial, or non-screen interaction design unless the task also includes screen-based controls or companion UI.
  • Backend architecture, database design, or API design except where implementation constraints affect component behavior.

Core principles

1. Start with people, goals, and context

Identify what the user is trying to accomplish before choosing a component. A form, menu, table, modal, or dashboard is only a means to a user goal. Ask “why” until the job, risk, and success criteria are clear enough to design the simplest useful interface.

Default: infer the user goal from the feature and proceed. Ask only when the missing context changes the pattern choice, such as expert vs novice users, mobile vs desktop, or high-risk vs low-risk actions.

2. Treat interaction as a conversation

Every UI should respond as if it is a considerate partner: it listens, acknowledges input, shows progress, prevents confusion, and makes the next step clear. Encode this into components through visible states, feedback, labels, focus behavior, and recovery paths.

Default: every interactive component must define at least default, hover/pressed where applicable, focus, loading, disabled, success, empty, and error states.

3. Choose the simplest pattern that preserves context

Prefer patterns that keep the user oriented and reduce unnecessary navigation. Keep tools close to the object they affect, but do not hide critical actions behind hover-only affordances or ambiguous icons.

Default: use in-place editing, contextual tools, inline validation, and same-page previews when they reduce context switching and remain discoverable.

4. Preserve wayfinding

Users need to know where they are, where they can go, what changed, and how to recover. Navigation is not just chrome; it includes signposts, hierarchy, breadcrumbs, progress indicators, deep links, escape hatches, and stable screen regions.

Default: provide a stable primary navigation model, a clear page title, visible current location, and a reversible route back to the previous or parent context.

5. Let information structure drive layout

Layout should reflect task structure, not decoration. Use grouping, proximity, alignment, visual hierarchy, progressive disclosure, and screen regions to show relationships and priorities.

Default: use a single clear primary action per task area; group related controls; make the most important content or object the center of attention.

6. Match the pattern to the data and task

A table, card grid, list, dashboard, feed, wizard, or detail page is correct only when it fits what users compare, scan, select, create, monitor, or edit.

Default: for structured, comparable, sortable data, use a table or dense list. For heterogeneous, visually recognizable items, use cards or thumbnails. For stepwise unfamiliar tasks, use a wizard. For expert repeated work, use a denser workspace with shortcuts and visible tools.

7. Make actions safe

Support safe exploration through preview, undo, cancel, clear labels, confirmation only for consequential actions, and strong recovery. Avoid blocking confirmations for routine reversible actions.

Default: prefer undo over confirmation when the action is reversible. Use a confirmation or buffer step only for destructive, costly, irreversible, privacy-sensitive, financial, or broadly propagating actions.

8. Design for interruption, re-entry, and repetition

Users change direction, pause, resume, repeat actions, and rely on memory. Keep state stable, avoid rearranging controls unexpectedly, remember safe progress, and bring forward recent/repeated actions when helpful.

Default: preserve unsaved work where possible, retain filters and scroll position after detail views, and do not move controls after users begin a task.

9. Make forms short, purposeful, and forgiving

Ask only for information needed now. Use labels, hints, appropriate input types, smart defaults, validation, examples, and error recovery. Do not rely on placeholder text as the only label or instruction.

Default: use visible labels, one-column flow for most forms, inline errors tied to fields, forgiving formats where possible, and smart prefills only wh

阅读完整来源 ↗