design-system-orchestrator

Orchestrates multi-skill design-system workflows by routing design.md sections to specialist skills.

2|Updated Jun 19, 2025
One-click install
npx skills add https://github.com/Prat05devs/dapper-city-threads --skill design-system-orchestrator-prat05devs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-system-orchestrator
Source: https://github.com/Prat05devs/dapper-city-threads/tree/main/.agent/skills/design-system-orchestrator
Command: npx skills add https://github.com/Prat05devs/dapper-city-threads --skill design-system-orchestrator-prat05devs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating brand, visual, verbal, and production work across many specialist design skills often leads to inconsistent outputs, stale context, and one-off visuals. This Skill enforces a single source of truth (a project design.md) and a structured routing process so every specialist works from the same confirmed decisions. ## Core Features & Use Cases - Canonical Handoff Management: Reads and maintains a project design.md as the authoritative input for every specialist skill, preventing routing from stale conversation memory. - Agent Routing & Sequencing: Directs work to child skills such as brand-strategy-engine, visual-language-system, token-component-system, and surface-specific production skills in the correct phase order. - Output Contracts & QA Gates: Defines a required folder structure (system, strategy, language, visual, tokens, architectures, outputs, qa) plus stop conditions that halt production when briefs, audiences, or approvals are missing. - Use Case: When launching a multi-surface campaign (social, web, print, motion), use this Skill to diagnose requirements, build a routing plan, assign each section to the right specialist, and assemble a reviewed final brand standard. ## Quick Start Use the design-system-orchestrator skill to read my project design.md and create a routing plan assigning each section to the right specialist skill.

Frequently Asked Questions about design-system-orchestrator

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

FAQPage Schema
How do I coordinate multiple design skills for a brand project?▼

Start by normalizing raw context into a project design.md, then use the orchestrator to diagnose requirements and route each section to specialist skills like brand-strategy-engine or visual-language-system. Every specialist must treat design.md as more authoritative than prior conversation context.

What is a design.md file and why is it required?▼

A design.md is the canonical project file containing confirmed brand and design decisions. The orchestrator requires it before routing any child skill, because routing from conversation memory produces stale or contradictory outputs.

Can I use this workflow for a single small design request?▼

Yes. For small requests the folder structure can be compressed, but creating or updating design.md remains mandatory. The single output brief covering surface, audience, message, and brand rules is still required before producing any final asset.

When does the orchestrator stop design production?▼

Production stops when the desired output or audience is unclear, design.md is missing or contradicted by newer sources, brand attributes are invented as confirmed, or claims and approvals are unverified. Work returns to architecture or clarifying questions first.

What outputs does a full design-system workflow produce?▼

A full run assembles design.md plus system, strategy, language, visual, tokens, architectures, outputs, and qa folders. This includes token JSON files, surface architecture documents, production assets, and per-surface review checklists.