From daffy0208-ai-dev-standards
Design user experiences and interfaces. Use when creating user journeys, wireframes, prototypes, or improving usability. Covers user flows, information architecture, interaction design, and accessibility.
npx claudepluginhub joshuarweaver/cascade-content-creation-misc-1 --plugin daffy0208-ai-dev-standardsThis skill uses the workspace's default tool permissions.
Design intuitive, accessible user experiences grounded in research.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Design intuitive, accessible user experiences grounded in research.
Design for users, not yourself. Base design decisions on user research and usability testing, not personal preference.
Goal: Organize content and functionality logically
Activities:
Validation:
Goal: Map paths users take to complete tasks
Key Flows to Design:
Flow Diagram Elements:
[Entry Point] → [Decision] → [Action] → [Outcome]
↓
[Alternative Path]
Validation:
Goal: Create low-fidelity layouts focusing on structure
Fidelity Levels:
Key Screens to Wireframe:
Wireframe Checklist:
Goal: Create interactive prototypes for usability testing
Prototyping Tools:
Usability Testing:
Script:
1. Welcome (5 min): Explain process, get consent
2. Context (5 min): Ask about current solutions
3. Tasks (20 min): "Try to [complete task]"
4. Think-aloud: "What are you thinking?"
5. Debrief (5 min): Overall impressions
Metrics:
- Task completion rate (target: >70%)
- Time on task
- Error rate
- Satisfaction (1-5 scale)
Validation:
Goal: Create high-fidelity, production-ready designs
Design System Elements:
Accessibility (WCAG 2.1 AA):
Developer Handoff:
Validation:
Use familiar patterns. Don't reinvent standard UI elements.
Confirm user actions (success messages, loading states).
Design to prevent errors, not just handle them.
Show options rather than requiring memory.
Support both novice and expert users (shortcuts, defaults).
Form Design:
Navigation:
Empty States:
Loading States:
Design Tools:
Prototyping:
Testing:
Accessibility:
Related Skills:
user-researcher - For grounding design in researchfrontend-builder - For implementing designsproduct-strategist - For validating design directionRelated Patterns:
STANDARDS/design-systems/component-library.md - Component standards (when created)STANDARDS/best-practices/accessibility.md - Accessibility guidelines (when created)Related Playbooks:
PLAYBOOKS/conduct-usability-test.md - Testing procedure (when created)PLAYBOOKS/design-handoff.md - Developer handoff process (when created)