Token导航 LogoToken导航TokenDH.com
前端设计权限需确认github未标认证来源可访问clear审计通过

ux-friction-analyzerux 摩擦分析仪

Agent Skill

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。

总安装

3,136

周安装

132

GitHub Stars

98

下载量

1,098
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:ux-friction-analyzer(ux 摩擦分析仪)
来源仓库:https://github.com/erichowens/some_claude_skills
仓库路径:skills/ux-friction-analyzer
安装命令:
npx skills add https://github.com/erichowens/some_claude_skills --skill ux-friction-analyzer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/erichowens/some_claude_skills --skill ux-friction-analyzer

简介

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。

  • 使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。
  • 适用于用户体验摩擦力检测与分析。
  • 需结合用户行为数据验证假设。
  • ux-friction-analyzer 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

UX Friction Analyzer

A comprehensive skill for analyzing and optimizing user experience through cognitive psychology, ADHD-friendly design, and flow state engineering.

Activation

Use this skill when:

  • Designing new interfaces or user flows
  • Auditing existing UX for friction points
  • Optimizing for neurodivergent users (ADHD, autism)
  • Simulating user journeys before building
  • Reducing cognitive load in complex applications

Trigger phrases: "analyze UX", "friction audit", "user journey", "ADHD-friendly", "optimize flow", "reduce cognitive load"


Core Frameworks

1. ADHD-Friendly Design Principles

Apply these patterns to ALL interfaces:

PrincipleImplementationWhy It Matters
Progressive DisclosureShow one task at a time; hide future stepsPrevents overwhelm, maintains focus
Context PreservationAuto-save every keystroke; never lose workReduces anxiety about losing progress
Gentle RemindersStatus updates, not alarms; no red urgencyAvoids panic, maintains calm
Pause & ResumeSession state persists across days/weeksRespects inconsistent schedules
Minimal DistractionsSingle focus area; dim non-active panelsReduces competing stimuli
Chunked ProgressVisual cards/steps, not endless scrollingCreates completion dopamine hits
Predictable NavigationSame layout always; no surprisesReduces reorientation cost
Calm Mode OptionReduced animations, muted colors on demandAccommodates sensory sensitivity

2. Gestalt Psychology

Apply these perception principles:

PROXIMITY
─────────
Elements close together = perceived as related
White space creates natural boundaries

┌─────────┐  ┌─────────┐     ┌─────────┐  ┌─────────┐
│ Related │  │ Related │     │ Other   │  │ Other   │
│ Item A  │  │ Item B  │     │ Group A │  │ Group B │
└─────────┘  └─────────┘     └─────────┘  └─────────┘
     ↑ CLOSE = GROUPED            ↑ SEPARATE = DISTINCT

SIMILARITY
──────────
Same color/shape/size = perceived as related function

┌──────┐  ┌──────┐  ┌──────┐     ┌──────┐  ┌──────┐
│ BLUE │  │ BLUE │  │ BLUE │     │ CORAL│  │ CORAL│
│ Save │  │ Copy │  │ Edit │     │ Del  │  │ Clear│
└──────┘  └──────┘  └──────┘     └──────┘  └──────┘
     ↑ SAME = Related actions         ↑ DIFFERENT = Destructive

CONTINUITY
──────────
Eye follows lines/paths naturally

Step 1 ──→ Step 2 ──→ Step 3 ──→ Complete
   ●──────────●──────────●──────────●

CLOSURE
───────
Brain completes incomplete shapes
Use for progress indicators, loading states

[ ████████░░░░░░░░ ] 50% - brain "sees" the end

3. Cognitive Load Theory

Three types of mental load to manage:

TypeDefinitionStrategy
IntrinsicTask complexity itselfCan't eliminate; acknowledge it
ExtraneousPoor design adding effortELIMINATE THIS - your job
GermaneLearning/understandingMinimize for repeat users

Working Memory Limits:

  • 7±2 items maximum (Miller's Law)
  • 4 chunks optimal for complex tasks
  • Micro-breaks every 25 minutes

Reduce Extraneous Load By:

  • Removing unnecessary choices
  • Using recognition over recall
  • Providing smart defaults
  • Eliminating decorative elements that don't inform

4. Fitts' Law

Time to acquire target = f(Distance / Size)

IMPLICATIONS FOR BUTTONS:
─────────────────────────

  ┌───────────────────┐          vs          ┌──┐
  │     GENERATE      │                      │Go│
  │                   │                      └──┘
  └───────────────────┘
         ↑                                     ↑
  44px+ touch target                   Hard to hit
  Easy to acquire                      Frustrating

MINIMUM SIZES:
- iOS: 44x44 CSS pixels
- Android: 48x48 CSS pixels
- Desktop: 32x32 minimum, 44x44 preferred

EDGE TARGETS ARE INFINITE:
  ┌─────────────────────────────────────────────────────┐
  │ ■ LOGO                                    MENU ■   │
  │                                                     │
  │   Screen edges = can't overshoot                   │
  │   Place critical actions at corners/edges          │
  │                                                     │
  │ ■ HELP                                  EXPORT ■   │
  └─────────────────────────────────────────────────────┘

ICON + LABEL > ICON ALONE:
- Larger target area
- Reduced ambiguity
- Faster acquisition

5. Flow State Engineering

Key Metrics:

  • 15-25 minutes to enter flow state
  • 23 minutes to recover from interruption
  • 40% productivity loss with frequent interruptions
  • Only 41% of work time spent in flow (McKinsey)

Flow Conditions:

  1. Clear goals for the current task
  2. Immediate feedback on actions
  3. Balance between challenge and skill
  4. No anxiety about failure

Preserve Flow By:

  • Background processing (don't block UI)
  • Push notifications when ready (bring user back faster)
  • Quick re-orientation panels after breaks
  • Auto-save eliminating "save anxiety"
  • Undo everything (confidence to experiment)

Analysis Methodology

Step 1: Create Decision Tree

Map every user path with probabilities:

                    ┌─────────────┐
                    │ USER LANDS  │
                    └──────┬──────┘
                           │
           ┌───────────────┼───────────────┐
           ▼               ▼               ▼
     ┌──────────┐   ┌──────────┐   ┌──────────┐
     │ Action A │   │ Action B │   │ Action C │
     │  (40%)   │   │  (45%)   │   │  (15%)   │
     └────┬─────┘   └────┬─────┘   └────┬─────┘
          │              │              │
          ▼              ▼              ▼
        [Next]         [Next]         [Next]

For each edge, record:

  • Probability (%)
  • Friction score (1-10)
  • Time to complete (seconds/minutes)
  • Cognitive load (low/medium/high)

Step 2: Simulate User Journeys

Create detailed simulations for each persona:

Template:

TIME    ACTION                           COGNITIVE STATE           FRICTION
─────────────────────────────────────────────────────────────────────────────
0:00    [User action]                    [Mental state]            Low/Med/High
        └─ [System response or UI shown]

0:15    [Next action]                    [How they feel]           Low/Med/High
        └─ [What happens]
        └─ PROBLEM: [Friction point if any]

...continue...
─────────────────────────────────────────────────────────────────────────────
TOTAL TIME: X minutes
FRICTION POINTS: N (list them)
ABANDONMENT RISKS: N (critical moments)
DELIGHT MOMENTS: N (positive surprises)

Personas to simulate:

  1. Expert User - Knows the system, moving fast
  2. New User - First time, needs guidance
  3. Distracted User - Context switching, interruptions
  4. Explorer - No goal, seeing what's possible
  5. Completer - Trying to finish, hitting obstacles

Step 3: Friction Analysis Matrix

Quantify and prioritize:

Friction PointUsers AffectedSeverity (1-10)Fix DifficultyPriority Score
[Issue 1]X%NEasy/Med/HardHIGH/MED/LOW
[Issue 2]X%NEasy/Med/HardHIGH/MED/LOW

Priority Formula:

Priority = (Users Affected × Severity) / Fix Difficulty

Step 4: Impedance Mapping

Compare current vs ideal:

TASK                          CURRENT IMPEDANCE     IDEAL IMPEDANCE
────────────────────────────────────────────────────────────────────
[Task 1]                      Low (X sec)           ✓ Optimal
[Task 2]                      Medium (X sec)        Could be Y sec
[Task 3]                      HIGH (X min)          Should be Y sec

Step 5: Time-Loss Analysis

Calculate context switch costs:

Action                        Frequency    Time Lost Each    Total Impact
─────────────────────────────────────────────────────────────────────────
[Interruption type 1]         X/session    Y min             Z min
[Interruption type 2]         X/session    Y min             Z min
─────────────────────────────────────────────────────────────────────────
TOTAL CONTEXT SWITCH LOSS                                    Z min/session

Optimization Patterns

Immediate Fixes (Low Effort, High Impact)

  1. Giant CTA on Landing <button class="cta" style="min-height: 60px; min-width: 200px;"> Primary Action <span class="subtext">Supporting text</span> </button>
  2. Visible Edit Affordances

- Show pencil/edit icons by default, not just on hover - Add tooltips: "Click to edit"

  1. Auto-Fill Prompts

- After user completes 1 item manually, offer to auto-complete rest - "Want me to fill in the remaining X items?"

  1. Floating Action Buttons

- Critical actions always visible (not buried in menus) - Bottom-right for mobile thumb zone

  1. Progress Indicators

- Show "Step X of Y" always - Visual progress bar at top

Medium-Term Improvements

  1. Re-Orientation Panels ┌─────────────────────────────────────────────┐ │ Welcome back! Here's where you left off: │ │ │ │ ✓ Step 1: Complete │ │ → Step 2: In progress (60%) │ │ ○ Step 3: Not started │ │ │ │ [Continue where I left off] │ └─────────────────────────────────────────────┘
  2. Keyboard Shortcuts

- Number keys for mode switching (1, 2, 3...) - Cmd+Enter for primary action - Escape for cancel/close

  1. Background Processing

- Never block UI for long operations - Show progress, allow user to continue - Push notification when complete

  1. Smart Defaults

- Pre-fill based on user history - Remember last-used settings - Suggest most common option first

Long-Term Vision

  1. Predictive UI

- Anticipate next action based on patterns - Pre-load likely next screens - Suggest before user asks

  1. Personalized Complexity

- Simple mode for new users - Power user mode unlocks over time - User controls their complexity level

  1. Accessibility Suite

- High contrast mode - Reduced motion option - Screen reader optimization - Keyboard-only navigation


Checklist for New Features

Before shipping any feature, verify:

Cognitive Load

  • Can user complete with ≤4 things in working memory?
  • Are there unnecessary choices that could be defaults?
  • Is recognition used instead of recall?

ADHD-Friendly

  • Can user pause and resume without losing context?
  • Are there gentle progress indicators (not anxiety-inducing)?
  • Is the interface calm (not visually noisy)?

Fitts' Law

  • Are primary buttons ≥44px tall?
  • Are destructive actions away from common paths?
  • Do buttons have labels, not just icons?

Flow Preservation

  • Does any action block the UI for >2 seconds?
  • Can long operations run in background?
  • Is there a clear "done" state?

Error Recovery

  • Can every action be undone?
  • Are error messages actionable (not just "Error")?
  • Is auto-save enabled?

Example Analysis Output

When running this skill, produce a document with:

  1. Executive Summary - Key findings in 3 bullets
  2. Decision Tree - All user paths with probabilities
  3. User Journey Simulations - 3-5 personas, full timeline
  4. Friction Matrix - Prioritized issues table
  5. Optimization Recommendations - Immediate/Medium/Long-term
  6. Implementation Checklist - Specific changes to make

Integration Points

  • web-design-expert: Implement UX recommendations visually
  • adhd-design-expert: Deep neurodivergent design patterns
  • frontend-developer: Technical implementation of fixes
  • diagramming-expert: Create user flow diagrams

Sources


Core Philosophy: Every click, every second of confusion, every moment of "where am I?" is friction stealing from your users. Design for the distracted, optimize for the overwhelmed, and everyone benefits.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

展示第三方安全扫描或审计结果

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

平台分布

Claude Code

27.45%
按下载量换算301

windsurf

24.24%
按下载量换算266

Codex

16.99%
按下载量换算187

Antigravity

11.92%
按下载量换算131

OpenCode

7.25%
按下载量换算80

Cursor

3.38%
按下载量换算37

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills