home / skills / shotaiuchi / dotclaude / design-user-advocate
This skill evaluates proposals from end-user and developer perspectives, ensuring usability, accessibility, API ergonomics, and inclusive design.
npx playbooks add skill shotaiuchi/dotclaude --skill design-user-advocateReview the files below or copy the command above to add this skill to your agents.
---
name: design-user-advocate
description: >-
User-centric design analysis. Apply when evaluating design proposals for
end-user experience, developer experience, API usability, accessibility,
and consumer satisfaction.
user-invocable: false
---
# User Advocate Perspective
Evaluate design proposals from the standpoint of end-users and developers who consume the system.
## Analysis Checklist
### End-User Impact
- Assess whether the design improves or degrades the user experience
- Check that latency and responsiveness targets meet user expectations
- Verify that error states provide clear, actionable feedback to users
- Look for user-facing regressions introduced by the design change
- Confirm that user workflows remain intuitive and efficient
### Developer Experience
- Evaluate the onboarding complexity for developers new to the codebase
- Check that APIs and interfaces are self-documenting and discoverable
- Verify that debugging and local development workflows are preserved
- Assess whether the design increases or reduces cognitive load for contributors
### API Ergonomics
- Check that API naming follows conventions and is predictable
- Verify that common operations are simple and advanced ones are possible
- Assess whether error responses are informative and consistent
- Look for unnecessary boilerplate or ceremony in typical usage patterns
### Accessibility & Inclusivity
- Verify that the design accommodates assistive technologies
- Check for assumptions about user connectivity, device, or locale
- Assess whether internationalization and localization are supported
- Look for design decisions that exclude users with disabilities
## Output Format
Report findings with strength ratings:
| Strength | Description |
|----------|-------------|
| Strong | Excellent user and developer experience throughout |
| Moderate | Acceptable experience with some usability friction |
| Weak | Poor experience or significant accessibility gaps |
| Neutral | Insufficient information to assess user impact |
This skill evaluates design proposals from a user-advocate perspective, focusing on end-user experience, developer experience, API ergonomics, and accessibility. It produces a concise strengths-based report and actionable recommendations to improve usability and inclusivity. Use it to catch regressions and surface subtle UX, DX, and API issues before implementation.
The skill inspects design artifacts, API specs, and workflow descriptions to evaluate impact across four domains: end users, developers, APIs, and accessibility. It applies a checklist to identify latency risks, unclear error states, onboarding friction, naming antipatterns, and accessibility blockers. The output is a strengths-rated report (Strong/Moderate/Weak/Neutral) with concrete findings and prioritized recommendations.
What does a "Neutral" strength rating mean?
Neutral means there is insufficient information to assess user impact; more artifacts or context are required to make a judgment.
Can this skill quantify performance issues?
It flags likely performance and latency risks and recommends measurements, but it does not run benchmarks; pair it with telemetry or load testing for quantification.