skills/ux-create-system-map/SKILL.md
Step 2.1 of Sketch the Solution. Identify core players and actions from entity inventory. Use when asked to 'create system map', 'identify entities', 'core players', or 'entity inventory'.
npx skillsauth add arndvs/ctrlshft ux-create-system-mapInstall 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 Create System Map skill." to chat to acknowledge you read this file.
Phase: /ux-system-map → Step 1 of 2
Take the grouped entities and actions from Phase 1 and build a structured entity inventory with their properties and capabilities.
Take the entity categories from user-stories.md (grouped nouns)
For each entity, define three dimensions:
Apply the CRUD model — for every action, verify completeness:
Generate entity inventory:
## Entity: [Name]
**Has:** [list of properties/sub-entities]
**Being:** [identity, role, states]
**Does:** [actions — create, edit, delete, view, search, filter, share]
**CRUD Check:** ✓ Create / ✓ Read / ✓ Update / ✓ Delete
Start system-map.md with Entity Inventory section.
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.