Design Router
Coordinate the design family without duplicating specialist instructions.
Route by deliverable
| Need |
Primary skill |
| Brand strategy, voice, identity governance |
brand |
| Tokens, components, themes, state architecture |
design-system |
| Product direction, UX evidence, stack guidance |
ui-ux-pro-max |
| Tailwind, component styling, responsive implementation |
ui-styling |
| Campaign banner, cover, ad, hero image |
banner-design |
| Pitch deck or HTML presentation |
slides |
For logos, icons, illustration, or photography, use the active host's native design or image-generation capability and the brand/design-system constraints. Do not require a fixed provider or model.
Mixed-deliverable workflow
- Define the shared brief: audience, objective, message, brand, platforms, required assets, deadlines, and acceptance criteria.
- Establish dependencies. Brand decisions precede token and asset decisions; tokens precede UI and presentation implementation.
- Invoke only the specialist skills required for the deliverables.
- Keep one owner for shared tokens, copy, logos, and source assets.
- Reconcile specialist outputs into one visual language.
- Validate consistency, accessibility, responsiveness, production dimensions, and export completeness.
Deliverable map
Before production, list each artifact with:
- owner or specialist workflow;
- source inputs;
- dimensions or platform;
- file format;
- dependencies;
- validation method;
- approval status.
Guardrails
- Do not activate every design skill for a narrow request.
- Do not let independent workstreams invent different brand tokens.
- Do not mix unrelated visual directions to appear more creative.
- Do not assume an image or browser tool is available; use the host's exposed capabilities and provide a fallback specification.
- Do not include provider/model names unless selected by the user.
1---2name: design-23description: Route broad or mixed visual-design requests into a coherent workflow spanning brand, design systems, UI/UX, interface styling, banners, presentations.4---56# Design Router78Coordinate the design family without duplicating specialist instructions.910## Route by deliverable1112| Need | Primary skill |13|---|---|14| Brand strategy, voice, identity governance | brand |15| Tokens, components, themes, state architecture | design-system |16| Product direction, UX evidence, stack guidance | ui-ux-pro-max |17| Tailwind, component styling, responsive implementation | ui-styling |18| Campaign banner, cover, ad, hero image | banner-design |19| Pitch deck or HTML presentation | slides |2021For logos, icons, illustration, or photography, use the active host's native design or image-generation capability and the brand/design-system constraints. Do not require a fixed provider or model.2223## Mixed-deliverable workflow24251. Define the shared brief: audience, objective, message, brand, platforms, required assets, deadlines, and acceptance criteria.262. Establish dependencies. Brand decisions precede token and asset decisions; tokens precede UI and presentation implementation.273. Invoke only the specialist skills required for the deliverables.284. Keep one owner for shared tokens, copy, logos, and source assets.295. Reconcile specialist outputs into one visual language.306. Validate consistency, accessibility, responsiveness, production dimensions, and export completeness.3132## Deliverable map3334Before production, list each artifact with:3536- owner or specialist workflow;37- source inputs;38- dimensions or platform;39- file format;40- dependencies;41- validation method;42- approval status.4344## Guardrails4546- Do not activate every design skill for a narrow request.47- Do not let independent workstreams invent different brand tokens.48- Do not mix unrelated visual directions to appear more creative.49- Do not assume an image or browser tool is available; use the host's exposed capabilities and provide a fallback specification.50- Do not include provider/model names unless selected by the user.
yigityildiz0