What problem does it solve? Design feedback and UI direction often get lost in chat threads or ad-hoc handoff files, leaving no durable record of accepted decisions, critique, or validation evidence. This Skill structures UI/UX design collaboration around GitHub planning issues so design state stays recoverable across sessions. ## Core Features & Use Cases - Issue-Backed Design State: Uses github-plan issues with standard headings (Objective, Finish Line, Current Status, Decisions, Validation) as the canonical design record instead of local handoff files. - Structured Design Requests: Provides a checklist for requesting first-pass or second-pass design work from Claude Design, Codex, or other collaborators, covering required states, constraints, and response format. - Returned Design Evaluation: Guides critique of returned mockups against acceptance criteria, required states, and repo constraints before implementation. - Use Case: A developer wants an external design pass on a dashboard page. The Skill creates a canonical GitHub issue with product context and required states, captures the returned critique in issue comments, records accepted tokens in Decisions, and links browser QA evidence before closeout. ## Quick Start Use the design-collaboration skill to create a GitHub planning issue requesting a first-pass visual design review of the settings page.
