Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/ux-design
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
Passed 15 of 19 test cases with the skill, and 4 of 19 without it.
and 10 more in the full report
11 fixed4 passed either way4 still failing0 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to define standard interaction patterns across our game (drag-and-drop, hold-to-confirm, radial menus). What file path should be targeted for this interaction pattern library?
| Checked | Without skill | With skill |
|---|---|---|
| Direct the document output to `design/ux/interaction-patterns.md`. | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,docs.density
Resolved above — use as-is. No block → defaults in
.claude/docs/config-resolution.md.
When this skill is invoked:
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Authoring guidance: the skeletons below are self-contained — author from them directly. When a section needs depth (worked examples, pattern catalogs, accessibility criteria), the matching guide has it:
| Producing | Guide |
|---|---|
| UX spec | .claude/docs/templates/guidance/ux-spec-guide.md |
| HUD design | .claude/docs/templates/guidance/hud-design-guide.md |
| Interaction patterns | .claude/docs/templates/guidance/interaction-pattern-library-guide.md (routes to three topic files) |
| Accessibility requirements | .claude/docs/templates/guidance/accessibility-requirements-guide.md |
Load a guide per-section, never whole — each is organised by section and the pointers in the templates name the exact section to read.
workflow (see .claude/docs/workflow-modes.md):
full — a UX spec is required per screen.standard — core screens only (main menu, HUD, primary game loop).minimal — not required. Can still be run voluntarily.docs.density — it controls per-section depth, where workflow
controls which screens are specced. modes.rigor sets both together; set
docs.density explicitly to vary depth alone: terse (the default, via rigor: minimal) = wireframe descriptions +
interaction bullets; balanced = wireframes + paragraph descriptions of flows
(rigor: standard); thorough = full prose including user-research summaries and
alternative flow considerations. Apply it to every section you author.
test cases passed, vs 4 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.