orchestrator-designer

Generate design tokens and component specifications for the Claude Orchestrator UI.

Updated Nov 19, 2025
One-click install
npx skills add https://github.com/Fire-ants-never-die/PB.ai_Web --skill orchestrator-designer-fire-ants-never-die
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-designer
Source: https://github.com/Fire-ants-never-die/PB.ai_Web/tree/main/.claude/skills/orchestrator-designer
Command: npx skills add https://github.com/Fire-ants-never-die/PB.ai_Web --skill orchestrator-designer-fire-ants-never-die

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps translate planning documents into concrete design specifications and design tokens to ensure visual consistency across the Claude Orchestrator UI.

Core Features & Use Cases

  • Design System Definition: Define design tokens (colors, typography, spacing) and establish a consistent visual language across components.
  • UI Design Output: Create comprehensive design specs and component guidelines for developers.
  • Design-Code Verification: Compare implemented UI against design specs and provide feedback.
  • Accessibility & Responsiveness: Include guidelines to ensure accessibility and responsive behavior.

Quick Start

Generate a complete design token set for the Orchestrator Web UI and export a component spec sheet.

Frequently Asked Questions about orchestrator-designer

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

FAQPage Schema
How do I create design tokens for a multi-platform UI?

Design tokens are reusable variables (colors, typography, spacing) that maintain consistency across platforms. This Skill generates a complete token set for Android, iOS, and Web, defining naming conventions and platform-specific guidelines so developers can implement designs uniformly without manual interpretation.

What's included in a component specification for developers?

A component spec documents visual behavior, layout rules, states, and accessibility requirements for each UI element. This Skill creates comprehensive specs that pair design decisions with implementation details—colors, spacing, typography, responsive breakpoints—so developers build exactly what designers intended.

How do I ensure my UI design meets accessibility standards?

Accessibility compliance requires defined contrast ratios, semantic sizing, touch targets, and responsive behavior across devices. This Skill incorporates accessibility guidelines into design tokens and component specs, ensuring color, typography, and spacing choices meet WCAG standards before implementation begins.

Can I verify that implemented UI matches the design specification?

Design-code verification compares live UI against design specs to catch misalignment early. This Skill provides a reference specification and token definitions that developers use to validate their implementation, reducing rework and ensuring visual consistency in the final product.

Do I need separate design tokens for each platform?

Yes. While core token logic stays consistent, Android, iOS, and Web each have platform conventions—touch targets, typography scales, spacing ratios. This Skill generates platform-specific token sets and guidelines so each platform feels native while maintaining a unified design language.

What information should I provide to generate design tokens?

Start with planning documents, design intent, color palettes, typography choices, and spacing scale. This Skill takes those inputs and transforms them into structured token definitions, component guidelines, and responsive behavior rules ready for implementation across all platforms.