design-flow

Orchestrates a six-phase design-to-build workflow from project grilling through frontend implementation.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/yashmishra2006/LexWrite-Website --skill design-flow-yashmishra2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-flow
Source: https://github.com/yashmishra2006/LexWrite-Website/tree/main/.agents/skills/design-flow
Command: npx skills add https://github.com/yashmishra2006/LexWrite-Website --skill design-flow-yashmishra2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new design project without structure leads to skipped discovery, inconsistent decisions, and lost context between phases. This Skill guides you through the complete design workflow as an ordered sequence, ensuring each phase is completed and confirmed before moving on. ## Core Features & Use Cases - Guided Phase Orchestration: Runs six phases in order—Grill Me, Design Brief, Information Architecture, Design Tokens, Brief to Tasks, and Frontend Design—with confirmation gates between each. - Persistent Design Artifacts: Saves outputs like DESIGN_BRIEF.md, INFORMATION_ARCHITECTURE.md, TASKS.md, and token files under a per-feature .design/<feature-slug>/ folder so multiple features stay independent. - Mid-Flow Resume: Detects existing artifacts in the .design/ folder and resumes from the next incomplete phase when you return. - Optional Design Review: Runs a screenshot-based review against the brief only on request, using Playwright MCP or a browser fallback. - Use Case: You are starting a new dashboard feature from scratch. Invoke the flow, get grilled on key decisions, produce a brief and IA document, generate tokens, break work into tasks, and build each component with checkpoints. ## Quick Start Ask the assistant to run the full design flow for your new feature and follow the guided phases from grilling through the build.

Frequently Asked Questions about design-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a full design workflow from scratch?

Invoke the design flow and it walks you through six phases in order: grilling, design brief, information architecture, design tokens, task planning, and frontend build. Each phase ends with a summary and a confirmation prompt before continuing.

Can I skip phases in the design flow?

Yes. At the start you are asked which phases to skip. Common skips include grill-me when the idea is clear, information-architecture for single components, and design-tokens when a project already has tokens.

Where are design flow artifacts saved?

All outputs are saved under .design/<feature-slug>/, including DESIGN_BRIEF.md, INFORMATION_ARCHITECTURE.md, token files, TASKS.md, and DESIGN_REVIEW.md with screenshots. Each feature gets its own folder so designs do not overwrite each other.

Does the design review run automatically?

No. The design review only runs when explicitly requested or via a separate review command after code is built. It captures screenshots of the running app using Playwright MCP, a browser fallback, or manually provided images.

What happens if I stop the design flow midway?

The flow summarizes your current position and the next phase. When you return, it checks the .design/ folder for existing artifacts, reads them to restore context, and resumes from the next incomplete phase.