Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/ux-design
Use when the user asks for UX, product flow, user journey, wireframes, usability, conversion, onboarding, checkout, signup, navigation, forms, state design, dashboard workflows, command palettes, settings, permissions, long-running task progress, admin/internal tools, activation, retention, or making an app easier to use over time. Designs and audits user experience flows, information architecture, content hierarchy, forms, onboarding, dashboards, settings, empty/loading/error/permission/success
Passed 20 of 22 test cases with the skill, and 17 of 22 without it.
and 2 more in the full report
4 fixed16 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.
I am building a high-volume B2B SaaS subscription management tool. Before we start designing any visual UI elements or writing frontend code, I need you to map out the core user flow and structure the interaction strategy. Please produce a structured UX brief covering the target job and user mode, a task ergonomics contract for repeated high-volume actions, a usability pattern evaluation, and the full state matrix including failure and edge conditions. Finally, provide a usability scenario test matrix covering first-time and power users so we can hand this off to our web design skill.
| Checked | Without skill | With skill |
|---|---|---|
| Formats the output using standard markdown code blocks for the requested briefs and contracts. | Passed | Passed |
| Recommends batch actions or keyboard shortcuts to optimize for repeated high-volume subscription operations. | Passed | Passed |
| Directs the visual handoff specifically to the web design skill. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when the product has to be understandable and usable, not just attractive. The output should make the user path clearer, reduce unnecessary decisions, and define states that survive real use.
Before designing screens, state the smallest useful context:
If any of these are unclear and materially affect the flow, ask one short question. If the answer is easy to infer from the request, infer it and continue.
Do not interrogate the user with a product-strategy questionnaire before helping. The skill should make useful assumptions, name them briefly, and move.
Write the minimum useful path:
test cases passed, vs 17 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.