What is the design flow skill?
The design flow skill is in julianoczkowski/designer-skills. It orchestrates the other designer skills in order: grill me, design brief, information architecture, design tokens, brief to tasks and frontend design, with design review on request. The agent announces each phase, summarizes the output and waits for your go ahead before moving on.
It is the design-flow skill in julianoczkowski/designer-skills, a collection of eight skills for designers who prototype with AI coding tools. Its description says it runs the full design to build workflow as a guided sequence.
The skill does not add new design rules. It reads each phase's own SKILL.md and follows it in full, while you stay in control through a confirmation after every phase.
What changes in your agent's output
- The agent opens by showing the whole sequence and asking which phases to skip, such as grilling when your idea is clear or tokens when a project already has them.
- Each phase is announced with what it will produce. Artifacts land under a .design folder in a named feature subfolder.
- After each phase the agent summarizes the file, key decisions and open questions, then asks if you are ready to continue.
- Design review never runs on its own. It needs built code and runs only when you ask, with screenshots saved beside the review.
The six phases
- Grill me clarifies your thinking and produces shared understanding, with no file.
- Design brief writes DESIGN_BRIEF.md with intent, goals and aesthetic direction.
- Information architecture writes INFORMATION_ARCHITECTURE.md covering structure and navigation.
- Design tokens produces a token file as CSS variables, a Tailwind config or a theme file.
- Brief to tasks writes TASKS.md as an ordered build checklist.
- Frontend design builds the components and pages task by task.
Who the design flow skill is for
Best for
- Designers starting a project from scratch who want structure before code.
- Anyone who wants the brief, tokens and task list saved in the project for a later session.
- Teams using the design brief skill or the frontend design skill alone who now want them chained.
Not for
- Quick one-off components, where skipping most phases leaves little for the flow to do.
- Anyone expecting automatic review. The review phase is on request only.
Use it with UiChemy
Run the flow for a marketing page, then rebuild the result in WordPress. UiChemy Composer writes HTML, CSS and JS for WordPress. Click Get Started on uichemy.com. For the token phase, see the design tokens skill.
How to install Design Flow Skill: A Guided Design to Build Workflow
/plugin marketplace add julianoczkowski/designer-skillsThe README says the skills work with Claude Code, Cursor, Codex, Windsurf and more than 40 other agents.Add the marketplace
In Claude Code run
/plugin marketplace add julianoczkowski/designer-skills.Install the plugin
Run
/plugin install designer-skills@designer-skills. This installs all eight skills, which design-flow needs so it can read each phase.Or use the skills CLI
The README lists an interactive skills CLI route that lets you pick skills, target agents and choose project or global scope.
Start the flow
Ask for the full design flow, or call it by name. You can skip phases at the first prompt.
Check that it loaded
Say run the full design flow. The agent should print the phase sequence, ask which phases to skip and wait for your answer before starting the first one.
Key features
- Upfront sequenceShows phases one to six, with review separate, and asks which phases to skip before starting.
- Phase announcementsBefore each phase it says what the phase will produce and asks whether you are ready.
- Full skill executionFor each phase it reads the matching SKILL.md and follows it completely, with no summarizing or abbreviating.
- Confirmation gatesAfter each phase it summarizes the output and waits for confirmation before the next one.
- Cross-phase checksBetween phases it checks whether earlier output changes the next step, such as a brief philosophy feeding the tokens.
- Stop and resumeYou can stop at any point. If you return, it reads the .design folder and resumes from the next incomplete phase.
- Per-feature foldersArtifacts live in .design with a lowercase hyphenated feature slug, so features do not overwrite each other.
- Task-by-task buildThe build phase works through TASKS.md in order, checking off each task and confirming before the next.
- Review on requestDesign review needs built code and runs only when asked, saving screenshots at several widths into the feature folder.
- Skip patternsSuggested skips include grill-me for a clear idea, information architecture for a single component and tokens for existing projects.
Frequently asked questions
What is the design flow skill?
It is a skill in julianoczkowski/designer-skills that chains the repository's designer skills into one guided sequence, from clarifying questions and a brief through architecture, tokens and tasks to a built front end, with confirmation after each phase.
How do I install the design flow skill?
Use the plugin marketplace route in Claude Code, or the interactive skills CLI the README describes. Install the whole collection, since design-flow reads the other skills' instructions in each phase.
Which agents does it work with?
The README badge and install section say the skills work with Claude Code, Cursor, Codex, Windsurf and more than 40 other agents through the skills CLI. The plugin route is specific to Claude Code.
Can I skip phases?
Yes. The agent asks at the start. Common skips are grill-me when you know what you want, information architecture for a single component, and design tokens when the project already has them.
Where are the outputs saved?
Under a .design folder, in a subfolder named for the feature. You get DESIGN_BRIEF.md, INFORMATION_ARCHITECTURE.md, a token file and TASKS.md, plus DESIGN_REVIEW.md and a screenshots folder if you run the review. Each feature keeps its own subfolder.
Does it run a design review automatically?
No. Review is phase seven and runs only if you ask, or run the review command later. It needs built components or pages, and the skill reminds you to build first if nothing exists.
How is it different from the frontend design skill?
The frontend design skill focuses on building the interface. Design flow wraps it as the last build phase, after a brief, structure, tokens and a task list have been written.
What license does it use?
GitHub shows julianoczkowski/designer-skills under the Apache-2.0 license. Check the LICENSE file in the repository for the full terms before you reuse or adapt the skills, and note that Apache-2.0 carries its own attribution conditions.


