DanielNoamTuby Design Flow
Guide the designer through these phases in order:
- Grill Me → clarify the idea
- Design Brief → capture intent
- Information Architecture → define structure
- Design Tokens → establish the visual system
- Brief to Tasks → plan buildable slices
- Frontend Design → build the interface
- Design Review → review the result separately
Rules
- At the start, show the sequence and ask which phases to skip. A clear idea may skip grilling; a single component may skip information architecture; an established token system may skip token generation.
- Before each phase, state what it produces.
- Invoke the corresponding skill and follow its full instructions.
- After each phase, summarize its output, decisions, and open questions. Confirm before continuing.
- Check whether each phase changes the next one. Tokens should follow the brief's chosen direction; tasks should follow the resulting structure.
- The designer may stop at any phase. State what is complete and what comes next.
The review phase is separate and requires built work. Do not run it automatically when nothing exists to inspect.
Returning to an unfinished flow
Look for the feature's existing design documents, identify the next incomplete
phase, and ask which feature to resume if more than one exists. Keep all
artifacts in the same .design/<feature-slug>/ folder:
.design/<feature-slug>/
├── DESIGN_BRIEF.md
├── INFORMATION_ARCHITECTURE.md
├── TASKS.md
├── DESIGN_REVIEW.md
└── screenshots/
Adapted from designer-skills by Julian Oczkowski under the Apache License,
Version 2.0. Modified for general use; see ../NOTICE.md.