Purpose
Separate website requirements, wireframing, design-system review, motion concepts, and prompt adaptation so web work stays clean and stage-specific.
Use when
- The main router has identified a website or landing-page creation request.
- The user needs help picking the right web-creation skill.
- A request is clearly web-focused but still needs web-specific clarification.
Required inputs
- Website objective and page or experience type.
- Brand/context status and any approved requirements [if known].
- Whether the user needs a brief, structure, audit, motion concept, or prompt specification.
Safety/authority
- Do not invent requirements, UX evidence, or implementation commitments.
- Keep execution recommendations draft-only unless approved.
- Use the briefing step first when requirements are still unclear.
Workflow
- Clarify the page type, objective, and stage of work.
- Route to:
- requirements intake:
web-design-brief-builder
- structural page concept:
landing-page-wireframe-draft
- current-system review:
ui-design-system-audit
- motion or interaction concepts:
web-animation-microinteraction-concept
- prompt-spec adaptation from approved requirements:
superdesign-ui-prompt-adapter
- Keep the stack to 1–3 skills, usually one planning skill plus one optional support layer.
- Optionally pair with
ai-creative-router or cross-asset-consistency-check when the website work must align with broader asset systems.
- If the exact skill is unavailable, use the closest same-stage website alternative or ask for clarification.
Output format
- Website task stage: ...
- Selected skills (1-3): ...
- Missing inputs: ...
- Optional support layer: ...
- Next step prompt: ...
Quality checks
- Briefing, wireframing, auditing, and prompt adaptation remain separate.
- The route stays stage-specific.
- Multi-asset alignment is optional, not default.
- Unknown requirements are made explicit.
Related skills
agency-router, web-design-brief-builder, landing-page-wireframe-draft, ui-design-system-audit, web-animation-microinteraction-concept, superdesign-ui-prompt-adapter, ai-creative-router
1---2name: website-creation-router3description: Route website creation work to the right web brief, wireframe, audit, motion, or prompt-adapter skill.4---56## Purpose78Separate website requirements, wireframing, design-system review, motion concepts, and prompt adaptation so web work stays clean and stage-specific.910## Use when1112- The main router has identified a website or landing-page creation request.13- The user needs help picking the right web-creation skill.14- A request is clearly web-focused but still needs web-specific clarification.1516## Required inputs1718- Website objective and page or experience type.19- Brand/context status and any approved requirements [if known].20- Whether the user needs a brief, structure, audit, motion concept, or prompt specification.2122## Safety/authority2324- Do not invent requirements, UX evidence, or implementation commitments.25- Keep execution recommendations draft-only unless approved.26- Use the briefing step first when requirements are still unclear.2728## Workflow29301. Clarify the page type, objective, and stage of work.312. Route to:32 - requirements intake: `web-design-brief-builder`33 - structural page concept: `landing-page-wireframe-draft`34 - current-system review: `ui-design-system-audit`35 - motion or interaction concepts: `web-animation-microinteraction-concept`36 - prompt-spec adaptation from approved requirements: `superdesign-ui-prompt-adapter`373. Keep the stack to 1–3 skills, usually one planning skill plus one optional support layer.384. Optionally pair with `ai-creative-router` or `cross-asset-consistency-check` when the website work must align with broader asset systems.395. If the exact skill is unavailable, use the closest same-stage website alternative or ask for clarification.4041## Output format4243```44- Website task stage: ...45- Selected skills (1-3): ...46- Missing inputs: ...47- Optional support layer: ...48- Next step prompt: ...49```5051## Quality checks5253- Briefing, wireframing, auditing, and prompt adaptation remain separate.54- The route stays stage-specific.55- Multi-asset alignment is optional, not default.56- Unknown requirements are made explicit.5758## Related skills5960agency-router, web-design-brief-builder, landing-page-wireframe-draft, ui-design-system-audit, web-animation-microinteraction-concept, superdesign-ui-prompt-adapter, ai-creative-router
danthamanvoiss