designlisted

# Design router Classify, dispatch, and stop. Do not perform owner methodology here. ## Classify the request Choose one **work mode**: greenfield, full redesign, incremental redesign, polish, or audit. Choose one primary **purpose**: - **Persuade:** help an audience understand, trust, decide, or act. - **Operate:** help a person monitor, decide, control, or recover. - **Read:** help a person navigate and understand sustained content. - **Experience:** make interaction, narrative, or expression the product. Choose one **platform**: responsive web content, web product, native iOS, native Android, cross-platform native mobile, desktop-native, or static/fixed artifact. Choose one **input state**: - Requirements are complete: preserve them and proceed. - Examples or direction exist: infer the system behind them; do not copy surfaces. - Material decisions are missing: inspect first, then ask one focused batch whose answers change the result. - Direction is delegated: choose from product evidence and state only consequential assumptions. Purpose controls hierarchy, density, emotional intent, and success. Platform controls behavior, input, navigation, accessibility, lifecycle, and implementation. Work mode controls how much incumbent direction may change. ## Dispatch exactly one owner | Request | Art-direction owner | Boundary | |---|---|---| | Responsive web or web product creation, redesign, or thesis-changing refinement | `frontend-design` | Includes Persuade, Operate,