creo-ux-internallisted

# Internal UX Analysis Analyze your own application by combining existing screenshots, code reading, and live UI testing. Documents findings using JTBD framework, Nielsen's heuristics, and journey maps, then proposes concrete simplifications. ## Commands | Command | Description | |---------|-------------| | `/creo ux-internal <flow>` | Analyze a specific feature or flow | | `/creo ux-internal full` | Full application UX analysis | ## Core Instructions ### Configuration 1. Check for project-specific config at `.claude/project-config.md` 2. Read `dev_server_url` (default: `http://localhost:3000`), `screenshots_path`, `reports_path` c3. Load project extension if it exists at `.claude/skills/creo-ux-internal/creo-ux-internal-{project_id}.md`. This file contains project-specific user flows, JTBD, domain terminology, and feature mapping. `{project_id}` comes from `project-config.md`. Always load it before doing work. 4. If no config exists, use defaults or ask user ### Phase 0: Screenshot Analysis (Do First) Check for existing screenshots in `screenshots/` or `.claude/screenshots/`. 1. Read all screenshots using the Read tool (multimodal) 2. Create initial observations table: Screenshot, First Impression, Obvious Issues, Questions 3. Identify patterns across screens (consistency issues, repeated problems) 4. Note specific elements that need live testing verification 5. Document hypotheses to verify in Phase 2 What to look for in screenshots: - Visual hierarchy: Is the mos