arndvs/ux-create-screen-goals
skills/ux-create-screen-goals/SKILL.md
Step 5.1 of Sketch the Solution. Define 1-2 goals for each screen in the flow diagram. Use when asked to 'create screen goals', 'define screen purpose', 'screen objectives', or 'what should each screen do'.
development
Updated Apr 30, 2026
$ install --global
skillsauthnpx skillsauth add arndvs/ctrlshft ux-create-screen-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 AM20.1s1 file scanned
SKILL.md
- name:
- ux-create-screen-goals
- description:
- Step 5.1 of Sketch the Solution. Define 1-2 goals for each screen in the flow diagram. Use when asked to 'create screen goals', 'define screen purpose', 'screen objectives', or 'what should each screen do'.
UX Step 5.1 — Create Screen Goals
Output "Read UX Create Screen Goals skill." to chat to acknowledge you read this file.
Phase: /ux-screen-requirements → Step 1 of 3
Every screen must have a clear purpose. Define 1-2 primary goals that answer: "Why does this screen exist? What should the user accomplish here?"
Process
-
Take each screen from
flow-diagram.md -
Define 1-2 goals per screen:
- What is the ONE thing a user should accomplish on this screen?
- What's the secondary goal (if any)?
-
Generate goals table:
## Screen Goals
| Screen | Goal 1 | Goal 2 |
|--------|--------|--------|
| Landing Page | Understand the value proposition | Sign up or log in |
| Dashboard | See overview of activity | Navigate to key features |
| Member Directory | Find members with specific skills | View member profiles |
| Content Feed | Discover relevant content | Post new content |
| Create Content | Publish content quickly | Tag/categorize properly |
| Member Profile | Understand member's expertise | Contact the member |
Rules
- Maximum 2 goals per screen — if you need more, the screen is doing too much (split it)
- Goals must be user-centric ("find a member") not system-centric ("display member list")
- Every screen's goals must connect to at least one user story
- The goal drives what gets prominent placement on the screen
Output
Start screen-requirements.md with Screen Goals 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