user-centered-design
Apply UCD methodologies to evaluate and improve software from the user's perspective.
소스 정보
- 저장소
- glayph/Agent
- 최근 소스 활동
- 2026년 9월 19일 22:39
- 감지된 SKILL.md 언어
- 영어
- 스타
- 0
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- user-centered-design
- description
- Apply UCD methodologies to evaluate and improve software from the user's perspective.
- version
- 1.0.0
- author
- Miki
- license
- MIT
- platforms
- ["linux","macos","windows"]
- metadata
- {"Miki":{"tags":["ux","user-research","usability","design-thinking"],"related_skills":["wireframing","visual-design","accessibility"]}}
# User-Centered Design & Research
## Research methods
### Heuristic evaluation (Nielsen's 10)
Check against: visibility, match real world, user control, consistency, error prevention, recognition, flexibility, minimalism, recovery, help.
### Cognitive walkthrough
For each user action ask: will user know what to do? will they notice correct action? will they understand feedback?
### Accessibility audit (WCAG 2.1)
- A: color contrast (4.5:1), alt text, keyboard nav
- AA: focus indicators, resize text 200%, error identification
- AAA: sign language, extended descriptions
## Deliverable templates
### Persona
```
Name, Role, Goals, Pain points, Tech literacy, Environment
```
### User flow
```
Trigger → Screen → Action → Feedback → Next screen
```
### Usability issue report
```
ID, Severity (critical/major/minor/cosmetic), Location, Description, WCAG ref, Suggested fix
```
## Design principles
- **Progressive disclosure** — show advanced options only when needed
- **Error forgiveness** — undo, confirm before destructive actions
- **Consistent mental model** — match platform conventions
- **Feedback loops** — every action gets a visible response within 200ms
- **Fitts's law** — target size ≥ 44x44px (mobile), ≥ 32x32px (desktop)
## Research process
1. Define: user segments, goals, success metrics
2. Collect: analytics, surveys, interviews, session recordings
3. Analyze: affinity mapping, pain point clustering, journey mapping
4. Recommend: prioritized fixes with effort vs impact
GitHub에서 보기