본문으로 건너뛰기
cccskills
무료GitHub에 공개

ui-review

Review UI designs and implementations for accessibility, consistency, usability, and visual quality. Use when asked to review a design, audit accessibility, check UI consistency, compare implementation against mockups, or evaluate a user interface.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

UI Review

Systematic UI/UX review methodology for designs (in Penpot) and implementations (in code).

Process

  1. Understand context — what product, who are the users, what's the goal of this screen?
  2. Gather materials — pull the Penpot designs and/or the live implementation
  3. Run the checklist — score each category
  4. Report — use the structured output format

Review Checklist

1. Accessibility (WCAG 2.1 AA)

Color & Contrast

  • Text contrast ≥ 4.5:1 against background (normal text)
  • Text contrast ≥ 3:1 against background (large text ≥ 24px or 18.67px bold, equivalent to WCAG 18pt/14pt)
  • UI component contrast ≥ 3:1 against adjacent colors (borders, icons, controls)
  • Information not conveyed by color alone (use icons, patterns, labels too)
  • Tested with color blindness simulation (protanopia, deuteranopia, tritanopia)

Keyboard Navigation

  • All interactive elements reachable via Tab key
  • Logical tab order (left-to-right, top-to-bottom, follows visual flow)
  • Visible focus indicator on all focusable elements (no outline:none without replacement)
  • Escape closes modals/dropdowns
  • Enter/Space activates buttons and links
  • Arrow keys navigate within composite widgets (tabs, menus, radio groups)

Screen Reader

  • All images have meaningful alt text (or aria-hidden if decorative)
  • Form inputs have associated labels (not just placeholder text)
  • ARIA landmarks used (main, nav, aside, footer)
  • Dynamic content changes announced (aria-live regions for toasts, errors)
  • Headings follow a logical hierarchy (h1 → h2 → h3, no skipping)

Motion & Interaction

  • Animations respect prefers-reduced-motion
  • No content that flashes more than 3 times per second
  • Touch targets ≥ 44x44px on mobile (WCAG 2.1 AAA — optional but recommended)
  • Adequate time for timed interactions (or ability to extend)

2. Design System Compliance

  • All colors from the token palette (no hex codes outside the system)
  • Typography uses defined scale (no arbitrary font sizes)
  • Spacing uses the 4px grid (no magic numbers)
  • Components match design system variants (no custom one-offs)
  • Icons from the approved set (Lucide)
  • Border radius from token scale
  • Shadows from token scale

3. Layout & Responsiveness

  • Works at all breakpoints: 375px, 768px, 1280px, 1536px
  • No horizontal scroll on mobile
  • Text remains readable at all sizes (no text smaller than 12px)
  • Touch-friendly spacing on mobile (no cramped click targets)
  • Images and media scale properly
  • Content hierarchy maintained across breakpoints

4. Interaction Design

  • Clear affordances (buttons look clickable, links look linkable)
  • Hover states on all interactive elements (desktop)
  • Loading states for async operations (skeleton screens or spinners)
  • Empty states designed (no blank pages — always guide the user)
  • Error states with clear recovery actions
  • Success feedback for completed actions
  • Confirmation for destructive actions (delete, discard)
  • Undo available where possible

5. Visual Quality

  • Consistent alignment (nothing looks "off" by a pixel)
  • Visual hierarchy clear (primary action stands out, secondary is quieter)
  • Whitespace used effectively (not cramped, not wastefully sparse)
  • Typography hierarchy clear (heading → subheading → body → caption)
  • Icon sizes consistent and proportional to surrounding text
  • No orphaned words in headings (line breaks make sense)

6. Content & Copy

  • Labels are clear and concise (no jargon)
  • Error messages explain what went wrong AND how to fix it
  • Button text describes the action ("Save changes" not "Submit")
  • Placeholder text is a hint, not a label
  • Consistent terminology throughout (don't mix "delete"/"remove"/"trash")

Output Format

## UI Review — [Screen/Component Name]

**Reviewed:** [date]
**Context:** [product, screen, purpose]
**Overall:** 🟢 Good | 🟡 Needs Work | 🔴 Significant Issues

### Accessibility
Score: X/10
[Specific findings with severity]

### Design System Compliance
Score: X/10
[Specific findings]

### Layout & Responsiveness
Score: X/10
[Specific findings]

### Interaction Design
Score: X/10
[Specific findings]

### Visual Quality
Score: X/10
[Specific findings]

### Content & Copy
Score: X/10
[Specific findings]

### 🔴 Must Fix
1. [Critical issues — accessibility violations, broken layouts]

### 🟡 Should Fix
1. [Important issues — inconsistencies, missing states]

### 🔵 Nice to Have
1. [Polish items — minor alignment, copy tweaks]

### ✅ What's Working Well
1. [Call out good patterns — reinforces what to keep doing]

Quick Review (for smaller changes)

For minor changes or single components, use a shortened format:

  1. Accessibility — contrast OK? Keyboard accessible? Screen reader friendly?
  2. Consistency — matches the design system?
  3. States — all states present? (hover, focus, disabled, error, loading)
  4. Responsive — works on mobile?
  5. Copy — labels clear and actionable?

Report as: ✅ Pass | 🟡 Minor issues | 🔴 Blocking issues

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Audit, generate, update, and lint AGENTS.md files across all projects. Use when asked to check project context files, scaffold AGENTS.md for new projects, update stale ones, or run a cross-project audit.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

espennilsen/pi1222026년 10월 12일 업데이트

blog-post

무료

Draft, edit, and publish blog posts for e9n.dev. Use when creating new posts, editing drafts, or refining existing content. Handles Eleventy frontmatter, Tailwind formatting, and Espen's authentic voice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

espennilsen/pi1222026년 10월 12일 업데이트

Generate a full operational status report for the Aivena bot. Checks all subsystems: extensions, webserver, Telegram, chat bridge, heartbeat, cron, database, memory, CRM, calendar, task management, jobs/telemetry, and storage. **Triggers — use this skill when:** - User asks for "status", "bot status", "system status", "operational status" - User asks "is everything running?", "how's Aivena doing?" - User says "health check", "diagnostics", "systems check" - User asks "what's the state of the bot?"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

espennilsen/pi1222026년 10월 12일 업데이트

Parse git history and produce or update a CHANGELOG.md following the Keep a Changelog convention. Supports Conventional Commits, basic prefix conventions, and unstructured commit messages. Intelligently categorizes changes, detects breaking changes, links to PRs/issues, and handles both initial generation and incremental updates. **Triggers — use this skill when:** - User asks to "generate", "create", "update", or "write" a changelog - User mentions "CHANGELOG", "changelog", "release notes" - User says "document changes", "what changed since last release" - User wants to "prepare a release" and needs a changelog entry - User asks to "clean up" or "reformat" an existing changelog **Covers:** Any git-based project. Handles Conventional Commits (feat/fix/chore), Angular convention, basic prefixes (Add/Fix/Remove), and freeform commit messages. Outputs Keep a Changelog format with optional Common Changelog enhancements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

espennilsen/pi1222026년 10월 12일 업데이트

cmux

무료

Orchestrate cmux terminal panes — split terminals, run parallel processes, read output from other panes, and use the built-in browser. Use when working inside cmux and you need to run a dev server, watch tests, spawn sub-agents, or preview web pages.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

espennilsen/pi1222026년 10월 12일 업데이트

Review code for quality, security, performance, and maintainability. Use when reviewing PRs, auditing a codebase, or refactoring. Covers TypeScript, Node.js, infrastructure-as-code, and full-stack web apps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

espennilsen/pi1222026년 10월 12일 업데이트

espennilsen의 스킬 모두 보기

이 스킬의 문제 신고