| name | ux-design-principles |
| description | Applies UX principles for clear, task-centred journeys, navigation and forms. Use when designing new screens, workflows, information architecture, or user journeys. |
| aliases | ["redesign-settings","settings-page","user-experience-design","ux"] |
UX Design Principles
When to use
Use this skill when designing or changing user journeys, task flows, forms, navigation, information architecture, workflow screens, review and approval flows, onboarding screens, or data-quality user journeys.
Objective
Create user-facing workflows that help users complete meaningful tasks with minimal cognitive load, clear feedback, visible system status, and explicit evidence for decisions.
Procedure
- Identify the primary user role.
- State the task the user is trying to complete.
- Identify the user's decision point and required evidence.
- Map the smallest useful flow from entry point to completion.
- Identify states: default, loading, empty, success, warning, error, partial success, blocked and awaiting approval.
- Remove unnecessary choices, fields, screens and jargon.
- Group information by user decision, not backend structure.
- Apply progressive disclosure for advanced or high-risk details.
- Make next actions explicit.
- Validate the flow against accessibility, error recovery and evidence needs.
Rules
- Do not start by mirroring database tables, API endpoints or internal architecture.
- Do not make users infer system status from missing information.
- Do not hide failures, warnings, partial results or uncertainty.
- Do not overload a single screen with all available data.
- Do not ask for information the system already knows.
- Prefer clear task language over implementation terms.
Optional overlay
For product-specific DataOps/MCP examples, load skills_docs/overlays/mas-dataops-mcp-overlay.md.
References
Verification
