| name | aidlc-ux-design-skill |
| description | The skill of designing user interfaces โ screen layouts, navigation flows, information architecture, and interaction patterns. Translates requirements and stories into visual structure that developers can implement.
|
UX Design
Purpose
Design the UI surface of a system โ what screens exist, how they connect, what data they show, and how users interact with them.
Principles
- Start from user journeys, not features โ map the flow a user takes to accomplish a goal
- Every screen must have a clear purpose โ if you can't state it in one sentence, split it
- Navigation should be obvious โ users should never be lost or unable to go back
- Data density matches the user's task โ dashboards are dense, forms are focused
- Consistency across screens โ same patterns for same interactions
- Responsive by default โ consider how layouts adapt across screen sizes
- Accessibility is not optional โ labels, contrast, keyboard navigation, screen reader support
- Error states and empty states are real screens โ design them, don't leave them to developers
Application
When producing wireframe artifacts:
- Read requirements and stories to understand what the system does
- Identify all screens needed (one per user goal or major action)
- Define the navigation map (how screens connect)
- For each screen: what data is displayed, what data is submitted, what actions are available
- Document layout guidance โ element placement, sizing, responsive behaviour
- Reference source stories for traceability