compose
Classify natural language design tasks, build multi-step plans, and execute them automatically. Specify components and outputs to generate specs, code, or audits.
Instructions
Run the agent orchestrator with a natural language design intent — classifies the task, builds a multi-step plan, and executes it.
Prerequisites: No Figma connection required for spec/code tasks. Figma-touching tasks (design generation, audits) require the bridge to be running. The orchestrator automatically dispatches to registered agent workers when available, or falls back to internal execution.
Returns on success: Orchestrator result object with shape { success: boolean, plan: { steps: [] }, results: [], summary: string, errors?: [] }. Each step includes the agent role that handled it and its output.
Error behavior: Returns success=false with an errors array if planning fails or execution throws. Individual step failures are captured per-step and do not abort the entire plan.
Intent examples:
"create a dashboard page with KPI cards, a chart, and a data table" — generates specs and code
"audit button variants for WCAG contrast and touch target compliance" — runs accessibility checks
"generate a login page with email/password form and OAuth buttons" — spec + codegen
"pull design system, then generate all missing component specs" — chained multi-step pipeline
"create a molecule spec for a search bar composing Input and Button atoms" — atomic design authoring
Be specific — vague intents like "make something nice" produce generic plans. Include component names, atomic levels, and target pages when relevant.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| intent | Yes | Natural language design task. Be specific about what to create, modify, or check. Include atomic level if relevant (atom/molecule/organism/template/page), component names, and target output (spec, code, audit). Examples: 'create a KPI card atom with value, label, and trend props', 'audit all organism specs for WCAG 2.2 compliance', 'generate the LoginPage template from the AuthForm organism spec'. | |
| dryRun | No | If true, returns the execution plan without running any steps. Use to inspect what the orchestrator intends to do before committing. Defaults to false. |