Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计未展示

ux-design用户体验设计

Agent Skill

用于辅助界面设计、视觉规范、排版、配色、布局和交互体验优化。它适合让 Agent 根据产品场景整理页面结构、生成 UI 方案、检查视觉一致性或改进组件层级。使用时需要结合现有品牌、设计系统和用户任务,不应只堆装饰元素;涉及真实页面改动时,应通过截图或浏览器预览检查文本溢出、对齐和响应式表现。

总安装

436

周安装

18

GitHub Stars

公开资料未说明

下载量

143
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ux-design(用户体验设计)
来源仓库:https://github.com/srstomp/pokayokay
仓库路径:skills/ux-design
安装命令:
npx skills add srstomp/pokayokay --skill "ux-design"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

AgentSkills.tonpx skills
npx skills add srstomp/pokayokay --skill "ux-design"

简介

ux-design 用于界面视觉与交互体验优化,提供布局建议、配色方案和动效说明。

  • 它适合让 Agent 生成原型草图、检查响应式表现或改进信息层级结构。
  • 安装命令:npx skills add srstomp/pokayokay --skill "ux-design",需上传现有页面截图或 Figma 链接。
  • 设计方案应适配主流设备尺寸,特别注意文本溢出和对齐问题。
  • 涉及品牌规范时须严格遵循主色调、字体和间距系统,保持视觉一致性。

SKILL.md

name
ux-design
description
Comprehensive UX design guidance covering research, information architecture, interaction patterns, and accessibility. Activates on ANY UI/UX work including user flows, navigation, forms, onboarding, error handling, and responsive design. Covers both process (Design Thinking, user research, personas) and implementation (patterns, accessibility, mobile UX). Use this skill for all user experience decisions on web and mobile platforms.

UX Design

User experience is the foundation. Visual aesthetics built on poor UX will fail. This skill ensures structural soundness before surface polish.

Related skills:

  • aesthetic-ui-designer — Visual execution after UX decisions are made
  • persona-creation — Deep user research, personas, JTBD, journey mapping
  • accessibility-auditor — Comprehensive WCAG 2.2 AA audits

Design Thinking Framework

A pragmatic approach: Design Thinking structure with Lean UX speed.

Empathize → Define → Ideate → Prototype → Test → Iterate
    ↑                                              |
    └──────────────────────────────────────────────┘

Quick Process Guide

PhaseGoalOutput
EmpathizeUnderstand users deeplyResearch insights, empathy maps
DefineFrame the right problemProblem statement, personas
IdeateExplore solutions broadlySketches, concepts, user flows
PrototypeMake ideas tangibleWireframes, clickable prototypes
TestValidate with real usersFeedback, iteration priorities

For detailed process guidance: See references/design-thinking-process.md


Core UX Principles

1. User Control & Freedom

  • Always provide escape routes (cancel, undo, back)
  • Don't trap users in flows
  • Confirm destructive actions, but don't over-confirm routine ones

2. Consistency & Standards

  • Follow platform conventions (web vs iOS vs Android)
  • Internal consistency: same action = same result everywhere
  • Use familiar patterns before inventing new ones

3. Error Prevention > Error Messages

  • Disable invalid actions rather than allowing then rejecting
  • Use constraints (date pickers vs free text)
  • Provide smart defaults

4. Recognition Over Recall

  • Show options, don't require memorization
  • Persistent navigation and context
  • Recently used items, search history

5. Flexibility & Efficiency

  • Shortcuts for experts, guidance for novices
  • Customizable workflows
  • Progressive disclosure: simple default, advanced available

6. Feedback & Visibility

  • Every action needs acknowledgment
  • System status always visible
  • Loading states, progress indicators, success confirmations

7. Help Users Recover

  • Clear error messages: what happened, why, how to fix
  • Preserve user input on errors
  • Offer alternatives when primary path fails

Information Architecture

Structure content so users find what they need.

Navigation Principles

  • 7±2 rule: Limit top-level items to 5-9
  • 3-click guideline: Major content within 3 clicks (flexible, not rigid)
  • Clear labeling: User language, not internal jargon
  • Visible location: Users should always know where they are

Navigation Patterns

PatternUse WhenPlatform
Top navbarFew primary sectionsWeb
SidebarMany sections, dashboard appsWeb
Bottom tabs3-5 primary destinationsMobile
Hamburger menuSecondary nav, space-constrainedBoth
Tab barContent categories at same levelBoth
BreadcrumbsDeep hierarchies, need path visibilityWeb

For detailed IA guidance: See references/information-architecture.md


Implementation Patterns

Forms

Structure:

  • One column layouts outperform multi-column
  • Group related fields visually
  • Logical order (don't ask shipping before cart)

Inputs:

  • Label above field (not placeholder-only)
  • Appropriate input types (email, tel, date)
  • Inline validation after field blur, not while typing

Actions:

  • Primary action visually dominant
  • Destructive actions require confirmation
  • Disabled submit until valid (with clear indication why)

Feedback States

Every interactive element needs:

  • Default: Resting state
  • Hover: Mouse over (desktop)
  • Focus: Keyboard navigation (accessibility critical)
  • Active: Being pressed/clicked
  • Disabled: Unavailable, with clear reason
  • Loading: Processing, with indicator
  • Success/Error: Outcome confirmation

Loading & Empty States

Loading:

  • Skeleton screens over spinners
  • Progress indicators for long operations
  • Optimistic UI where safe

Empty states:

  • Explain why empty
  • Guide toward first action
  • Never just blank space

Error Handling

[Clear icon] What went wrong
             Why it happened (briefly)
             [Primary action to fix] [Secondary: help/retry]
  • Position near the source
  • Don't blame the user
  • Offer recovery path

Onboarding

  • Delay account creation until necessary
  • Value first, signup second
  • Progressive profiling over long forms
  • Skippable for returning users

For detailed patterns: See references/patterns.md For modern patterns (AI, dark mode, animation): See references/modern-patterns.md


Mobile-Specific UX

Touch Targets

  • Minimum 44×44pt (iOS) / 48×48dp (Android)
  • Spacing between targets to prevent mis-taps
  • Primary actions in thumb zone (bottom of screen)

Gestures

  • Swipe for delete/archive (with undo)
  • Pull-to-refresh for lists
  • Pinch-to-zoom for images/maps
  • Avoid gesture-only actions; provide visible alternatives

Mobile Navigation

  • Bottom tab bar for primary nav (≤5 items)
  • Stack navigation for hierarchical content
  • Modal for focused tasks (with clear dismiss)
  • Avoid hamburger menus as primary nav

Performance UX

  • Perceived performance matters more than actual
  • Instant feedback, background processing
  • Offline states and graceful degradation

Accessibility Essentials

Accessibility improves UX for everyone. For comprehensive audits, use the accessibility-auditor skill.

Quick Checklist

Perceivable:

  • [ ] Text alternatives for images (alt text)
  • [ ] Color contrast: 4.5:1 for text, 3:1 for large text
  • [ ] Don't convey info by color alone

Operable:

  • [ ] Full keyboard navigation
  • [ ] Visible focus indicators
  • [ ] Touch targets ≥44px
  • [ ] No keyboard traps

Understandable:

  • [ ] Clear error messages with recovery path
  • [ ] Labels for all form inputs
  • [ ] Consistent navigation

Robust:

  • [ ] Semantic HTML (use right elements)
  • [ ] ARIA only when HTML isn't sufficient

For implementation details: See references/accessibility.md For full WCAG 2.2 AA audits: Use the accessibility-auditor skill


Responsive Design

Breakpoint Strategy

  • Design mobile-first, enhance upward
  • Content determines breakpoints, not devices
  • Common: 640px (sm), 768px (md), 1024px (lg), 1280px (xl)

What Changes Per Breakpoint

  • Navigation pattern (tabs → sidebar → topnav)
  • Grid columns
  • Touch vs hover interactions
  • Content density

What Stays Consistent

  • Core functionality
  • Information hierarchy
  • Brand identity
  • Accessibility

UX Anti-Patterns

Navigation Anti-Patterns

Anti-PatternWhy It's BadInstead
Hamburger as primary navHides key options, reduces discoveryBottom tabs (mobile), visible nav (web)
Mystery meat navigationIcons without labels confuse usersLabel icons, or use text links
Deep nesting (5+ levels)Users get lost, high abandonmentFlatten hierarchy, use search
Inconsistent back behaviorBreaks mental modelPredictable back = previous screen
Pagination in infinite contentJarring interruptionInfinite scroll with "load more" option

Form Anti-Patterns

Anti-PatternWhy It's BadInstead
Placeholder as labelDisappears, accessibility issuesLabel above field
Validating while typingPremature errors frustrate usersValidate on blur
Clearing form on errorPunishes users for mistakesPreserve input, highlight error
Generic error messages"Invalid" doesn't helpSpecific: "Use 8+ characters"
**Required \* everywhere**Noise if most are requiredMark optional fields instead
Multi-column formsIncreases completion timeSingle column (exceptions: city/state/zip)

Feedback Anti-Patterns

Anti-PatternWhy It's BadInstead
Silent failuresUser doesn't know what happenedAlways confirm or explain failure
Modal for everythingInterrupts flow, modal fatigueToast for success, inline for errors
Auto-dismissing errorsUser can't read/act in timePersist until dismissed or fixed
Spinners for contentNo layout stabilitySkeleton screens
Blocking loadersUI feels frozenNon-blocking indicators

Onboarding Anti-Patterns

Anti-PatternWhy It's BadInstead
Feature tours upfrontUsers forget, want to exploreContextual hints when relevant
Mandatory lengthy signupHigh drop-offDelay signup, progressive profiling
Tooltips everywhereOverwhelmingMax 1-3 per session
Can't skipFrustrates returning usersAlways allow skip
Empty state with no guidanceUsers don't know what to doExplain + clear first action

Mobile Anti-Patterns

Anti-PatternWhy It's BadInstead
Tiny touch targetsMis-taps, frustration≥44pt/48dp
Hover-dependent featuresNo hover on touchTap/press alternatives
Desktop modals on mobileHard to dismiss, blocks screenBottom sheets
Fixed position nav + keyboardCovers input fieldsHide nav during input
Gesture-only actionsDiscoverable, accessibilityVisible buttons + gesture shortcut

General Anti-Patterns

Anti-PatternWhy It's BadInstead
Confirmation for routine actionsSlows users downOnly confirm destructive/irreversible
Jargon in UIUsers don't understandPlain language
Disabled without explanationUser doesn't know whyExplain what's needed
Infinite scroll for all listsCan't bookmark, no sense of progressPaginate long lists with stable URLs
Auto-playing video/audioStartling, consumes dataUser-initiated playback

UX Decision Trees

Modal vs Page vs Drawer

Is the task focused and short?
├── Yes: Does user need to reference background content?
│   ├── Yes → Drawer/Panel (side sheet)
│   └── No → Modal
└── No: Is the task a full workflow?
    ├── Yes → Full page
    └── No: Is it contextual actions?
        ├── Yes → Bottom sheet (mobile) / Dropdown (web)
        └── No → Consider page or panel

Tabs vs Accordion vs Sections

Is content mutually exclusive (only one visible at a time)?
├── Yes: Are items few (≤5) and parallel?
│   ├── Yes → Tabs
│   └── No → Accordion
└── No: Should all content be scannable?
    ├── Yes → Stacked sections (all visible)
    └── No → Progressive disclosure (expand on demand)

Pagination vs Infinite Scroll

Does user need to find specific item or reach specific point?
├── Yes → Pagination (URL stability, can bookmark)
└── No: Is content time-based / feed-like?
    ├── Yes: Is list long and exploratory?
    │   ├── Yes → Infinite scroll + "back to top"
    │   └── No → Load more button
    └── No → Pagination with visible page count

Toast vs Inline vs Modal (for messages)

Is immediate action required?
├── Yes → Modal with action buttons
└── No: Is it an error related to specific field?
    ├── Yes → Inline (near field)
    └── No: Is it a success/info message?
        ├── Yes → Toast (auto-dismiss ok)
        └── No: Is it a system-level warning?
            ├── Yes → Banner (top of page)
            └── No → Toast or inline

UX Checklist

Before finalizing any interface:

Structure

  • [ ] Clear information hierarchy
  • [ ] Intuitive navigation
  • [ ] User always knows their location
  • [ ] Important actions are prominent

Interaction

  • [ ] Every action has feedback
  • [ ] Error states are helpful
  • [ ] Loading states are present
  • [ ] Empty states guide users

Accessibility

  • [ ] Keyboard navigable
  • [ ] Screen reader compatible
  • [ ] Sufficient color contrast
  • [ ] Touch targets adequate

Mobile

  • [ ] Thumb-zone friendly
  • [ ] Touch targets ≥44pt
  • [ ] Works offline or degrades gracefully
  • [ ] No hover-dependent functionality

References:

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

27.84%
按下载量换算40

windsurf

22.44%
按下载量换算32

trae

19.19%
按下载量换算27

OpenCode

12.84%
按下载量换算18

Codex

8.31%
按下载量换算12

github-copilot

3.47%
按下载量换算5

安全审计

暂无安全审计结果可展示。

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills