arndvs/ux-identify-goals
skills/ux-identify-goals/SKILL.md
Step 1.1 of Sketch the Solution. Identify goals for each user type/avatar. Use when asked to 'identify user goals', 'define user goals', 'map user types', or 'list personas'.
development
Updated Apr 30, 2026
$ install --global
skillsauthnpx skillsauth add arndvs/ctrlshft ux-identify-goalsInstall 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:37 AM11.6s1 file scanned
SKILL.md
- name:
- ux-identify-goals
- description:
- Step 1.1 of Sketch the Solution. Identify goals for each user type/avatar. Use when asked to 'identify user goals', 'define user goals', 'map user types', or 'list personas'.
UX Step 1.1 — Identify Goals
Output "Read UX Identify Goals skill." to chat to acknowledge you read this file.
Phase: /ux-user-stories → Step 1 of 3
Identify every distinct user avatar and define what they're trying to accomplish. Each user type has different goals, pain points, and workflows.
Process
- List all user types from ID calls and customer interviews. Include obvious AND non-obvious users (Carl's Tesla mistake: forgot in-store staff, only considered online buyers).
- For each user type, define:
- Who they are (role, demographics, tech comfort level)
- What they're trying to accomplish (1-3 primary goals)
- What frustrates them about the current process
- What devices/tools they currently use
- Output a structured persona table:
## User Avatars
### [Avatar Name] — [Role]
- **Demographics:** [age range, tech proficiency, context]
- **Goals:**
1. [Primary goal]
2. [Secondary goal]
- **Current Pain:** [What frustrates them today]
- **Devices/Tools:** [What they use now]
Rules
- Include ALL user types — not just the primary customer
- Consider: end users, admins, managers, support staff, external stakeholders
- Goals describe what users WANT, not what your product does
- Source everything from real customer data, not assumptions
Output
Append to user-stories.md: User Avatars section with persona table.
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