design-is

Topics in the source

• Design Is
• Do not use for
• The Ten Principles (Dieter Rams)
• Delegation Model
• Subagent Reporting Contract (MANDATORY)
• Output Artifacts
• Phases
• Phase 0: Scope Lock (ALWAYS FIRST)

Routine UI code reviews → use /review Pure copy edits → use a separate copy pass Pre-design ideation with no artifact yet → start with /make-plan directly You are an ORCHESTRATOR. Audit a design against Dieter Rams' ten principles, score each principle with evidence, decide the outcome verdict (NEW / REFINE / REDESIGN), and hand off to /make-plan with a ready-to-run prompt. You do not write implementation code. You produce: evidence-cited scores, a verdict, and a /make-plan handoff prompt. Audit each principle in this exact order. Each gets a score 0–3 and ≥1 piece of evidence (file:line, screenshot region, copy excerpt, or measured value). 1. Good design is innovative — Does it advance the form, or imitate? Innovation rides on technology; never an end in itself. 2. Good design makes a product useful — Does it serve the primary task? Emphasizes usefulness; disregards anything that detracts. 3. Good design is aesthetic — Is it beautiful? Only well-executed objects can be beautiful; aesthetic quality affects well-being. 4. Good design makes a product understandable — Does the structure clarify function? Or is it self-explanatory at best? 5. Good design is unobtrusive — Does it stay o

This is an excerpt. Refer to the complete source and its current requirements.