design-orchestration
Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order.
Best use case
design-orchestration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order.
Teams using design-orchestration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/design-orchestration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How design-orchestration Compares
| Feature / Agent | design-orchestration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Design Orchestration (Meta-Skill) ## Purpose Ensure that **ideas become designs**, **designs are reviewed**, and **only validated designs reach implementation**. This skill does not generate designs. It **controls the flow between other skills**. --- ## Operating Model This is a **routing and enforcement skill**, not a creative one. It decides: - which skill must run next - whether escalation is required - whether execution is permitted --- ## Controlled Skills This meta-skill coordinates the following: - `brainstorming` — design generation - `multi-agent-brainstorming` — design validation - downstream implementation or planning skills --- ## Entry Conditions Invoke this skill when: - a user proposes a new feature, system, or change - a design decision carries meaningful risk - correctness matters more than speed --- ## Routing Logic ### Step 1 — Brainstorming (Mandatory) If no validated design exists: - Invoke `brainstorming` - Require: - Understanding Lock - Initial Design - Decision Log started You may NOT proceed without these artifacts. --- ### Step 2 — Risk Assessment After brainstorming completes, classify the design as: - **Low risk** - **Moderate risk** - **High risk** Use factors such as: - user impact - irreversibility - operational cost - complexity - uncertainty - novelty --- ### Step 3 — Conditional Escalation - **Low risk** → Proceed to implementation planning - **Moderate risk** → Recommend `multi-agent-brainstorming` - **High risk** → REQUIRE `multi-agent-brainstorming` Skipping escalation when required is prohibited. --- ### Step 4 — Multi-Agent Review (If Invoked) If `multi-agent-brainstorming` is run: Require: - completed Understanding Lock - current Design - Decision Log Do NOT allow: - new ideation - scope expansion - reopening problem definition Only critique, revision, and decision resolution are allowed. --- ### Step 5 — Execution Readiness Check Before allowing implementation: Confirm: - design is approved (single-agent or multi-agent) - Decision Log is complete - major assumptions are documented - known risks are acknowledged If any condition fails: - block execution - return to the appropriate skill --- ## Enforcement Rules - Do NOT allow implementation without a validated design - Do NOT allow skipping required review - Do NOT allow silent escalation or de-escalation - Do NOT merge design and implementation phases --- ## Exit Conditions This meta-skill exits ONLY when: - the next step is explicitly identified, AND - all required prior steps are complete Possible exits: - “Proceed to implementation planning” - “Run multi-agent-brainstorming” - “Return to brainstorming for clarification” - "If a reviewed design reports a final disposition of APPROVED, REVISE, or REJECT, you MUST route the workflow accordingly and state the chosen next step explicitly." --- ## Design Philosophy This skill exists to: - slow down the right decisions - speed up the right execution - prevent costly mistakes Good systems fail early. Bad systems fail in production. This meta-skill exists to enforce the former. ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
ckm:design
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.
ckm:design-system
Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.
ckm:banner-design
Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.
figma-implement-design
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.
figma-generate-design
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code'. This is the preferred workflow skill whenever the user wants to build or update a full page, screen, or view in Figma from code or a description. Discovers design system components, variables, and styles via search_design_system, imports them, and assembles screens incrementally section-by-section using design system tokens instead of hardcoded values.
figma-create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
workflow-orchestration-patterns
Master workflow orchestration architecture with Temporal, covering fundamental design decisions, resilience patterns, and best practices for building reliable distributed systems.
web-design-guidelines
Review files for compliance with Web Interface Guidelines.
ui-ux-designer
Create interface designs, wireframes, and design systems. Masters user research, accessibility standards, and modern design tools.
tool-design
Build tools that agents can use effectively, including architectural reduction patterns. Use when creating new tools for agent systems, debugging tool-related failures or misuse, or optimizing existing tool sets for better agent performance.
tailwind-design-system
Build production-ready design systems with Tailwind CSS, including design tokens, component variants, responsive patterns, and accessibility.
stitch-ui-design
Expert guidance for crafting effective prompts in Google Stitch, the AI-powered UI design tool by Google Labs. This skill helps create precise, actionable prompts that generate high-quality UI designs for web and mobile applications.