arndvs/ux-screen-requirements
skills/ux-screen-requirements/SKILL.md
Phase 5 of Sketch the Solution. Define goals and ABC requirements for every screen. Use when asked to 'screen requirements', 'screen specs', 'define screens', or 'screen goals'.
development
Updated Apr 30, 2026
$ install --global
skillsauthnpx skillsauth add arndvs/ctrlshft ux-screen-requirementsInstall 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 AM13.6s1 file scanned
SKILL.md
- name:
- ux-screen-requirements
- description:
- Phase 5 of Sketch the Solution. Define goals and ABC requirements for every screen. Use when asked to 'screen requirements', 'screen specs', 'define screens', or 'screen goals'.
UX Phase 5 — Screen Requirements
Output "Read UX Screen Requirements 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
Goals for each screen in a flow diagram. The purpose is to get a user to the next phase in UX.
Define what every screen must contain so users know: where they are, what they can do, and where they can go. This is the hand-off document for UI designers.
Prerequisites
flow-diagram.mdfrom Phase 3 (screen list and navigation paths)attributes.mdfrom Phase 4 (data attributes per entity)system-map.mdfrom Phase 2
Steps
Step 1 — Create 1-2 Goals
Invoke /ux-create-screen-goals
Define 1-2 primary goals for each screen in the flow diagram.
Step 2 — Apply Inform → Engage → Invite
Invoke /ux-inform-engage-invite
Structure each screen's intent: inform the user (trust, context), engage them (show value), invite them forward (CTA).
Step 3 — List Screen Attributes (ABC)
Invoke /ux-list-screen-attributes
For each screen define: A) what the user gets, B) what they can do, C) how they navigate next.
Output
Generate screen-requirements.md containing:
- Per-screen goals table
- Per-screen Inform/Engage/Invite breakdown
- Per-screen ABC specification (Gets / Does / Navigates)
- Prioritized requirements (most important actions = most prominent)
Rules
- Every screen must answer: "Where am I? What can I do? Where can I go?"
- Landing pages need trust elements: testimonials, press, featured customers
- Engage before asking for anything — show value first
- Prioritize requirements by user importance within each screen
- This document IS the designer hand-off if you have a UI designer
Handoff
After completion, offer:
/ux-interface-design— proceed to Phase 6/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