skills/ux-list-screens/SKILL.md
Step 3.1 of Sketch the Solution. Derive the complete screen list from the system map. Use when asked to 'list screens', 'screen inventory', 'what screens do I need', or 'enumerate pages'.
npx skillsauth add arndvs/ctrlshft ux-list-screensInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Output "Read UX List Screens skill." to chat to acknowledge you read this file.
Phase: /ux-flow-diagram → Step 1 of 3
Derive every screen the product needs from the system map. Think of each screen as a "neighborhood" in a city.
Walk through the system map entity by entity:
Generate a combined screen list (not separated by user type):
Output screen inventory table:
## Screen Inventory
| # | Screen Name | Purpose | Derived From |
|---|-------------|---------|--------------|
| 1 | Landing Page | Entry point, value proposition | System entry |
| 2 | Sign Up | Account creation | User entity |
| 3 | Login | Authentication | User entity |
| 4 | Dashboard | Main hub after login | System map |
| 5 | Member Directory | Browse/search members | Member entity |
| 6 | Member Profile | View member details | Member entity |
| 7 | Content Feed | Browse/filter content | Content entity |
| 8 | Create Content | Post new content | Content CRUD |
| 9 | View Content | Read content + comments | Content entity |
Start flow-diagram.md with Screen Inventory table.
development
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.
development
Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
tools
Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
testing
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.