planning-visual-creative-orchestrator

Coordinate cross-domain visual concept generation by dispatching Claude Code Task agents per pass.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/pelchers/MockTrialGame --skill planning-visual-creative-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-visual-creative-orchestrator
Source: https://github.com/pelchers/MockTrialGame/tree/main/.claude/skills/planning-visual-creative-orchestrator
Command: npx skills add https://github.com/pelchers/MockTrialGame --skill planning-visual-creative-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinate cross-domain visual concept generation across data-vis, animation, and graphic-design by dispatching isolated Claude Code Task agents for each pass.

Core Features & Use Cases

  • Read the central style-config.json to enumerate domains, styles, and per-pass definitions.
  • Read the library catalog to select domain-appropriate libraries and versions.
  • Dispatch separate Claude Code Task agents for each (domain, style, pass) combination with a comprehensive prompt.
  • Generate self-contained outputs per pass including index.html, style.css, app.js, README, and validation metadata.
  • Validate visuals with Playwright after each pass and enforce per-pass uniqueness plus anti-repeat constraints.

Quick Start

Invoke the orchestrator to generate all domain-style-pass outputs and run the Playwright validation after each pass.

Frequently Asked Questions about planning-visual-creative-orchestrator

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

FAQPage Schema
How do I coordinate multi-domain visual design generation across data visualization, animation, and graphic design?

Multi-domain visual design generation is coordinated by dispatching isolated Claude Code Task subagents for each pass, applying per-pass palettes, directions, libraries, and anti-repeat constraints to ensure unique cross-domain outputs.

Can I use Playwright to validate generated visual design concepts automatically?

Playwright-based validation runs automatically after each visual concept generation pass, enforcing per-pass uniqueness and anti-repeat constraints to verify the self-contained index.html, style.css, and app.js outputs.

Do I need a style-config.json file to automate cross-domain visual orchestration?

A central style-config.json file is required to enumerate domains, styles, and per-pass definitions, which the orchestrator reads to dispatch subagents and organize outputs under the design concepts directory.

What is the best way to generate self-contained HTML, CSS, and JavaScript outputs for multiple design domains?

Generating self-contained visual outputs per pass is best handled by dispatching isolated subagents that produce index.html, style.css, app.js, README, and validation metadata for each domain, style, and pass combination.

How does the orchestrator select domain-appropriate libraries for visual concept generation?

The orchestrator reads a library catalog to select domain-appropriate libraries and versions, ensuring each isolated subagent receives the correct dependencies for its specific data-vis, animation, or graphic-design pass.

What are the limitations of using isolated subagents for multi-pass visual design orchestration?

Subagent-based visual orchestration requires strict anti-repeat constraints and per-pass uniqueness enforcement, as isolated agents generate independent outputs that must be validated sequentially with Playwright to prevent conceptual duplication.