Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-ux-principles
Core UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.
Passed 23 of 25 test cases with the skill, and 20 of 25 without it.
and 4 more in the full report
4 fixed19 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our engineers currently output raw SQL error strings like 'ERR_DB_502' in toaster notifications. What three elements must every error message contain to be usable for end users?
| Checked | Without skill | With skill |
|---|---|---|
| Requires error messages to state what happened. | Passed | Passed |
| Requires error messages to state why it happened. | Missed | Passed |
| Requires error messages to state what to do next. | Passed | Passed |
The instructions your model reads when the skill loads.
Evidence-based UX fundamentals for guiding interface design during requirements gathering. Use to evaluate designs, write better AC, and ask the right questions during discovery.
Apply when reviewing any interface design or writing AC.
| # | Heuristic | Product Owner Action |
|---|---|---|
| 1 | Visibility of system status | Require feedback for every action within 100ms. Status indicators for all async ops. |
| 2 | Match system and real world | Ban internal jargon from UI. Use domain language from user research. |
| 3 | User control and freedom | Every destructive action needs undo or confirmation. Navigation always allows going back. |
| 4 | Consistency and standards | Require design system. Audit for inconsistent terminology across features. |
| 5 | Error prevention | Require input validation, constraints, confirmation for irreversible actions. |
| 6 | Recognition over recall | Prefer dropdowns over free text when options known. Show recent items. Contextual help. |
| 7 | Flexibility and efficiency | Require keyboard shortcuts for frequent actions. Support mouse and keyboard workflows. |
| 8 | Aesthetic and minimalist design | Challenge every UI element: does it serve current task? Remove decorative clutter. |
| 9 | Help with errors | Error messages state what happened, why, and what to do next. No raw error codes. |
| 10 | Help and documentation | Require contextual help (tooltips, inline guidance). Documentation by task, not feature. |
For each screen or workflow under review:
Score each 0 (no problem) to 4 (usability catastrophe). Fix 3s and 4s before launch.
test cases passed, vs 20 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.