--- name: design-orchestrator description: "Use for brand-led website, product UI or design-system work that should combine Taste, Impeccable, Playwright CLI, Awesome Design and image-to-Three.js. Route each stage to its actual bundled source, preserve the owning brand and verify the rendered result. Also use when the user invokes the Starlight design toolkit." --- # Design orchestrator Resolve the plugin root as two directories above this file. Read `playbooks/design-skill-integration.md` once; it defines authority, source pins, runtime limits and evidence boundaries. Run `node /scripts/design-toolkit.mjs verify` before using bundled third-party scripts. Use `doctor` to inspect executable availability without installing anything. ## Route by contribution | Stage | Read | Required result | | --- | --- | --- | | Brief and authority | Owning product instructions; `brand-packs//`; `skills/world-class-web-release/SKILL.md` | Recipient, job, primary action, current truth, retained constraints | | Reference selection | `skills/design-reference-selector/SKILL.md` | One compatible visual mechanism, mapped to owned tokens | | Art direction | `skills/taste-studio/SKILL.md` | Exactly three distinct directions for flagship work; one selected with reason | | Implementation and critique | `skills/impeccable-studio/SKILL.md` | Surface mode, working UI, prioritized corrections and failure states | | Browser proof | `skills/browser-verify/SKILL.md` | Real desktop/mobile captures and functional observations | | Image-led 3D, when useful | `skills/image-to-threejs/SKILL.md` | An inspected scene with stated fidelity, performance and fallback | Use every capability when it contributes; load only the selected source files. Do not invent a 3D feature merely to exercise a module. On a narrow task, use the relevant adapter directly. Never execute six complete upstream playbooks in parallel against the same surface. ## Starlight lab material studies For a lab brief involving liquid glass, texture, depth, particles or a Starlight object, resolve the candidate foundation against the owning product revision. Use the material contract for limits and the original identity manifest for the mark. Record both revisions and any disagreement before rendering. [Observatory Glass candidate](https://github.com/Starlight-Intelligence/starlight-design-intelligence/blob/eed60eff204574583fdfd6beb8a20a2d464d9b3b/brand-packs/sis/foundations/README.md) ยท [material tokens](https://github.com/Starlight-Intelligence/starlight-design-intelligence/blob/eed60eff204574583fdfd6beb8a20a2d464d9b3b/brand-packs/sis/foundations/tokens.json) Hold the object, viewpoint and light direction fixed while comparing materials. Give porcelain a broad opaque reflection, obsidian a dark body with a narrow edge and glass a transparent center with a second thin rim. Inspect the three side by side with their labels hidden. If hue is the only reliable distinction, revise the reflections. Keep essential reading on the opaque substrate. Exercise finite replay, interruption, static reduced motion and the solid fallback on the actual component. Compare the Figma specimen with the same material and depth in the product. Record visual defects separately from token validation and use the product's release checks for promotion. [Material acceptance gate](https://github.com/Starlight-Intelligence/starlight-design-intelligence/blob/eed60eff204574583fdfd6beb8a20a2d464d9b3b/evals/starlight-material-foundations.md) ## Resolve conflicts User instructions and the owning product contract govern scope. The selected Starlight brand pack governs identity. External sources supply techniques and diagnostics. Apply upstream stylistic bans as signals, then resolve any conflict with the explicit brand and surface mode. Record intentional exceptions. Keep FrankX practical and founder-led, SIS precise and operational, Arcanea world-led, and GenCreator faithful to its own pack. No shared costume. Preserve existing functionality, verified claims, content rights and interaction states. ## Close the loop Capture before, change the highest-impact defect, inspect the actual result, correct it, and capture again. Require a separate substantive verifier for release-affecting work. Name source revision, files actually loaded, tested viewport/state, evidence paths, unresolved dependency and next release gate. Distinguish bundled instructions, available executable, loaded host, rendered output and deployed result. A source hash verifies bytes, not quality or adoption.