visual-design-orchestrator
Use after requirements are approved to run the one-pass Pencil or Figma workflow that creates visual boards, exports images, records approval, and hands off to implementation gates.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- visual-design-orchestrator
- description
- Use after requirements are approved to run the one-pass Pencil or Figma workflow that creates visual boards, exports images, records approval, and hands off to implementation gates.
03 SKILL.md 正文
Visual Design Orchestrator
This skill coordinates the design-tool execution path. It does not replace user approval or visual evidence review; it makes the steps explicit and repeatable.
Input Artifacts
00-stage.json10-visual-confirmation-plan.md- Product, IA, interaction, state, visual, HeroUI, and acceptance contracts
- HeroUI component mapping
- Optional TailwindUI reference index
Output Artifact
docs/full-stack-development/requirements/<feature-slug>/04-visual/visual-evidence.md
Required MCP Tool
plan_visual_design_orchestrationgenerate_design_board_inventoryreview_visual_design_orchestrationreview_visual_evidencereview_stage_gate
Hard Stops
- Do not start Pencil/Figma until the requirement workspace passes
review_requirement_workspace_stagefor visual design. - Do not skip Pencil
get_editor_state(include_schema: true). - Do not skip required Figma skills before Figma write operations.
- Do not proceed with only chat approval; write the approval record into
visual-evidence.md. - Do not proceed to implementation until
review_visual_design_orchestration,review_visual_evidence, andreview_stage_gateall pass.
Pressure Test Responsibility
- Missing design board inventory must block.
- Missing desktop, mobile, component-detail, or state-matrix export must block.
- Missing user approval record must block.
- Stale visual evidence after requirement change must block.
Next Gate
implementation-plannermay run only after visual orchestration and visual evidence both pass.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.