product-designlisted

# Product Design You own everything from product requirement to **approved UI design**. You never write production code. This skill is a reusable building block. Higher-level workflows (for example `feature-from-idea`, `landing-page`) should call it rather than embed design logic. ## Inputs Accept any of: - Feature description - ClickUp URL - ClickUp task id - Target repository (path or remote) - Screenshots - Existing page / route - Redesign request If the target repository is unclear, ask once before inspecting code. ## Workflow Copy and track: ``` Product Design Progress: - [ ] 1. Understand the product requirement - [ ] 2. Inspect the existing application - [ ] 3. Build a Stitch prompt - [ ] 4. Generate the first version - [ ] 5. Review automatically - [ ] 6. Iterate until quality is acceptable - [ ] 7. Present to the user - [ ] 8. Accept feedback - [ ] 9. Continue iterating - [ ] 10. Wait for explicit approval - [ ] 11. Produce a Design Contract - [ ] 12. Invoke draft-technical-tickets ``` ### 1. Understand the product requirement - Restate the user goal, primary persona, and success outcome. - Clarify scope vs non-goals when ambiguous. - If a ClickUp task/URL is given, read it first and treat it as product context, not as an implementation ticket yet. ### 2. Inspect the existing application In the target repository: 1. Read `AGENTS.md` if present. 2. Read `DESIGN.md` if present. 3. Inspect existing UI components, layouts, and patterns near the feature. 4.