design-flow

Name: design-flow
Availability: InStock
Author: concept2cure

Sequence design sub-skills into a guided workflow from briefs to frontend design.

1|Updated Nov 13, 2025

Search Tags:#workflow #tasks #tokens #phases #brief #designer #design-flow

Ready to run

npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill design-flow-concept2cure

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-flow
Source: https://github.com/concept2cure/ClinicalSageAI-2-replit/tree/main/.claude/skills/design-flow
Command: npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill design-flow-concept2cure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of guiding designers through a complete, multi-phase workflow, ensuring consistency and progress across grilling, briefs, IA, tokens, tasks, and frontend design.

Core Features & Use Cases

Orchestrates sequential phases of the design process by invoking individual skills for each phase.
Generates artifacts and coordinates outputs (DESIGN_BRIEF.md, INFORMATION_ARCHITECTURE.md, TASKS.md) while allowing optional phase skipping.
Use Case: When starting a new project, run the full design flow to produce a complete plan and artifacts for build.

Quick Start

Start the full design flow and follow the guided prompts to progress through each phase.

Frequently Asked Questions about design-flow

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

FAQPage Schema

How do I manage a complete design-to-build workflow from project inception to frontend development?▼

A design-to-build workflow orchestrates sequential phases like grilling, briefs, information architecture, tokens, and frontend design. It guides you through each step, ensuring consistent progress and generating artifacts like DESIGN_BRIEF.md and TASKS.md.

What is the best way to generate a design brief and information architecture for a new project?▼

Generating a design brief and information architecture is best handled by running a structured design flow. This process sequentially invokes targeted phases to extract requirements, producing structured artifacts like DESIGN_BRIEF.md and INFORMATION_ARCHITECTURE.md.

Can I skip certain phases like information architecture or token generation in a structured design process?▼

Yes, you can skip optional phases in a structured design process. The workflow coordinates end-to-end design activities by sequencing sub-skills, allowing you to bypass specific stages like token generation while still producing core planning artifacts.

How do I coordinate design tokens and frontend tasks after finalizing a project brief?▼

To coordinate design tokens and frontend tasks after a brief, use a guided workflow that sequences these specific phases. It bridges the gap between planning and building by generating a TASKS.md file to track implementation outputs.

Does a guided design workflow help maintain consistency across grilling, briefs, and frontend design?▼

A guided design workflow ensures consistency across grilling, briefs, and frontend design by orchestrating each phase sequentially. It coordinates outputs and maintains progress throughout the entire design-to-build cycle.

When do I need a full design-to-build cycle instead of individual design tools?▼

You need a full design-to-build cycle when starting a new project that requires a complete plan and build artifacts. It solves the challenge of guiding designers through multi-phase workflows, ensuring consistency from grilling to frontend design.