arndvs/ux-user-stories
skills/ux-user-stories/SKILL.md
Phase 1 of Sketch the Solution. Write pain-state user stories per avatar, highlight entities and actions. Use when asked to 'write user stories', 'user stories', 'capture user goals', or starting the UX process.
development
Updated Apr 30, 2026
$ install --global
skillsauthnpx skillsauth add arndvs/ctrlshft ux-user-storiesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 2:38 AM15.4s1 file scanned
SKILL.md
- name:
- ux-user-stories
- description:
- Phase 1 of Sketch the Solution. Write pain-state user stories per avatar, highlight entities and actions. Use when asked to 'write user stories', 'user stories', 'capture user goals', or starting the UX process.
UX Phase 1 — User Stories
Output "Read UX User Stories skill." to chat to acknowledge you read this file.
Pipeline position: /ux-user-stories → /ux-system-map → /ux-flow-diagram → /ux-model-attributes → /ux-screen-requirements → /ux-interface-design → /ux-test-driven-design
What versus how. Capture imagination and magic.
Write empathy-driven narratives that describe every user's current pain, workflow, environment, and emotions — BEFORE any solution design begins.
Prerequisites
- Customer avatar(s) from idea extraction
- ID call notes / interview transcripts
- Understanding of user pain points
Steps
Step 1 — Identify Goals
Invoke /ux-identify-goals
Define goals for each user type. Identify every distinct user avatar and what they're trying to accomplish.
Step 2 — Write User Story
Invoke /ux-write-user-story
Write a pain-state narrative for each avatar/goal. Describe the CURRENT challenge, not your solution.
Step 3 — Highlight Key Terms & Verbs
Invoke /ux-highlight-key-terms
Extract entities (nouns) and actions (verbs) from stories into structured tables. These feed directly into the System Map.
Output
Generate user-stories.md containing:
- Avatar profiles with goals
- Narrative user stories (pain-state, per avatar)
- Entity table (highlighted nouns)
- Action table (highlighted verbs)
- Formal user story templates: "As a [role], I want to [behavior], so that [value]"
Rules
- Stories describe the CURRENT pain — never how your product solves it
- Write stories for EVERY user type, not just the primary one
- Find "the need behind the need" — ask WHY at every step
- Stories are living documents — update after future customer calls
Handoff
After completion, offer:
/ux-system-map— proceed to Phase 2/sketch-the-solution— return to orchestrator
If context is high, follow the standard handoff protocol (@~/dotfiles/instructions/handoff.instructions.md).
Related Skills
arndvs/visual-feedback
development
VerifiedTrustedCommunity
Use when implementing UI, checking dark/light mode, or validating animations — adds a visual feedback loop via browser screenshots so frontend changes are verified, not assumed.
SKILL.mdUpdated May 21, 2026
arndvs/press1-check
development
VerifiedTrustedCommunity
Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
SKILL.mdUpdated May 21, 2026
arndvs/plan-archive
tools
VerifiedTrustedCommunity
Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
SKILL.mdUpdated May 21, 2026
arndvs/grill-with-docs
testing
VerifiedTrustedCommunity
Use when stress-testing a plan against the project's domain model — grills the design, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
SKILL.mdUpdated May 21, 2026