ux-detail-review

Detail-focused UI/UX review workflow based on Buzz Usborne's "God is in the details". Use when reviewing screenshots, prototypes, websites, or apps for interaction polish, usability friction, feedback clarity, loading behavior, microcopy tone, and platform convention fit. Trigger for requests like "UX 리뷰", "UI 피드백", "디자인 검토", "사용성 분석", "인터랙션 개선", "디테일 점검", "UX review", "UI review", "design critique", "usability audit", or "interaction polish".

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "ux-detail-review" with this command: npx skills add simply-strong-lab/ux-detail-review/simply-strong-lab-ux-detail-review-ux-detail-review

UX Detail Review

Deliver a detail-level UX review that focuses on moments where users hesitate, mistrust, or lose flow.

Workflow

  1. Capture review context.
  • Identify artifact type (screenshot, prototype, live page, app screen).
  • Identify target user action (for example: sign up, buy, submit, compare, search).
  • Identify constraints (mobile/desktop, locale, accessibility needs, release scope).
  1. Run a 6-lens detail audit.
  • Action feedback: Verify each user action has immediate, visible confirmation.
  • Loading behavior: Check whether waiting states match task context and user intent.
  • Interaction honesty: Detect deceptive or hostile interaction patterns.
  • Native conventions: Check alignment with platform expectations and learned patterns.
  • Motion quality: Review transitions and micro-animations for clarity, not decoration.
  • Microcopy tone: Review labels, hints, errors, and empty states for clarity and respect.
  1. Record evidence before suggesting fixes.
  • Tie each finding to a concrete UI element, state, or path step.
  • Describe the current behavior and user impact in one sentence each.
  • Avoid abstract opinions that cannot be observed.
  1. Prioritize improvements.
  • P0: Blocks completion, causes likely abandonment, or creates major trust risk.
  • P1: Significant friction on key journeys.
  • P2: Noticeable polish gap with moderate user impact.
  • P3: Nice-to-have refinement.
  1. Propose fix + validation per finding.
  • Give one concrete change recommendation.
  • Define a validation method (usability check, event metric, A/B, or heuristic re-test).
  • Prefer fixes that can be implemented in the current release cycle.

Required Output Shape

Use the structure in assets/review-template.md.

Non-negotiables:

  • Include severity (P0 to P3) for every finding.
  • Include expected user impact and suggested implementation effort.
  • If no issues are found, state that explicitly and list residual risk areas.

Reference Files

  • Core principles and checklist: references/god-is-in-the-details.md
  • Response scaffold: assets/review-template.md

Read only the files above unless the user requests deeper expansion.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Security

compliance-evidence-assembler

把审计所需证据整理成目录、清单和缺失项,便于后续评审。;use for compliance, evidence, audit workflows;do not use for 伪造证据, 替代正式审计结论.

Archived SourceRecently Updated
Security

skillguard-hardened

Security guard for OpenClaw skills, developed and maintained by rose北港(小红帽 / 猫猫帽帽). Audits installed or incoming skills with local rules plus Zenmux AI intent review, then recommends pass, warn, block, or quarantine.

Archived SourceRecently Updated
Security

api-contract-auditor

审查 API 文档、示例和字段定义是否一致,输出 breaking change 风险。;use for api, contract, audit workflows;do not use for 直接改线上接口, 替代契约测试平台.

Archived SourceRecently Updated
Security

ai-workflow-red-team-lite

对 AI 自动化流程做轻量红队演练,聚焦误用路径、边界失败和数据泄露风险。;use for red-team, ai, workflow workflows;do not use for 输出可直接滥用的攻击脚本, 帮助破坏系统.

Archived SourceRecently Updated