UX Artifacts
Produce evidence-labelled UX needs, journey, structure, inclusion, and...
Install
npx skills add microsoft/hve-core --skill ux-artifacts -g -a claude-code -y- Repository
- microsoft/hve-core1.6k
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,954 tokens
- Runs scripts
- No, instructions only
What it does
Produce evidence-labelled UX needs, journey, structure, inclusion, and engineering-handoff assets. Use when a practitioner needs a durable UX artifact rather than coaching.
UX Artifacts
Produce one durable, evidence-labelled UX asset from supplied context. Use this skill directly or through an agent when the required outcome is an artifact rather than a coached conversation.
Goal
Turn supplied UX evidence and decisions into a current Markdown asset that another practitioner, agent, or engineer can consume without inventing research or losing uncertainty.
Modes
Load exactly one mode reference for each invocation.
| Mode | Outcome | Reference |
|---|---|---|
frame-needs | Current context, user needs, desired outcomes, and known workarounds | references/frame-needs.md |
map-journey | Staged journey with actions, thoughts, pain points, and opportunities | references/map-journey.md |
sketch-structure | Surface composition, controls, interaction states, and transitions | references/sketch-structure.md |
decide-inclusion | Concept-stage exclusion risks, demands, alternatives, and coverage gaps | references/decide-inclusion.md |
prepare-handoff | Implementation-facing flow, states, recovery, rationale, and open decisions | references/prepare-handoff.md |
The modes are operations over supplied evidence. They are not practitioner roles, project phases, persistent workflows, or prerequisites for one another. Never invoke another mode automatically.
