Update to Toonkit

{
  "description": "Default workflow for ToonKit image, video, voice and canvas work, even without an explicit planning request. Explains model choices and costs before paid generation; routes deterministic 3D previz separately.",
  "included_files": [
    {
      "relative_path": "TOONKIT-GENERATION-SSOT.md",
      "size_in_bytes": 40499
    },
    {
      "relative_path": "references/ai-production.md",
      "size_in_bytes": 14572
    }
  ],
  "name": "toonkit-project-manager",
  "skill_md_contents": "---\nname: toonkit-project-manager\ndescription: Default workflow for ToonKit image, video, voice and canvas work, even without an explicit planning request. Explains model choices and costs before paid generation; routes deterministic 3D previz separately.\n---\n\n# ToonKit Project Manager\n\nRun the applicable workflow for ToonKit work unless the user explicitly stands it down. Follow the user's workflow first; honor explicit requirements, infer only delegated gaps and scale the report to the request. Do not write a scenario document for one short clip.\n\nBefore new paid generation, give a **visible plan even without “plan first”**: what will be generated and why, exact model/variant and applicable preset, resolution, selection reasons, and the quote inputs and cost status. Model choices must not remain internal or be replaced by “two images at 2K.” The AI report below defines the details; users need not name this skill or SSOT separately. Default paid flow: one report → confirmation of decisions/spend not already authorized → execution. Preserve existing explicit choices and authorization; do not ask again for unchanged approved work. A plan-only request ends with the plan; a requested approval checkpoint must precede generation.\n\n## Route before loading documents\n\n| Request/stage | Load |\n|---|---|\n| Only deterministic 3D previz, staging/motion/camera or browser-runtime export | The co-distributed [3dref](../3dref/SKILL.md) skill and its routed execution instructions. **No AI workflow or SSOT.** |\n| An explicit 2D anime **motion-graphics** video request (kinetic typography/shapes composited with ToonKit characters) | Hand over to the co-distributed [toonkit-motion-mv](../toonkit-motion-mv/SKILL.md) skill. It routes its paid stages back to the AI production workflow below. Ordinary video or clip requests stay here. |\n| AI image/video/voice generation, including R2V after previz | [AI production](references/ai-production.md) and [SSOT](TOONKIT-GENERATION-SSOT.md), once before choosing models/references or spending. |\n| Existing result/status without new generation | Relevant read-only status tools, not production manuals or a new job. |\n\nA previz exported as MP4 is still deterministic, not AI-video generation. Do not query models, balance, guide or credit quotes for it alone; use the 3D catalog. Missing AI-only SSOT must not block standalone previz.\n\nIn mixed pipelines, load AI rules for actual AI stages; do not reread unchanged SSOT on entry/exit from previz. Select previz only when specified or when particular shots need precise spatial/action/camera reference, not every shot. If explicitly required but unavailable, report the prerequisite instead of silently skipping.\n\n## Scope a location reference\n\nFor 3Dref, “faithful to the location sheet” means preserving shot-relevant positions, distances, height relationships and interaction surfaces using simple proxies. Plan the actors and camera first, then construct only the needed part of the camera's swept view. Do not rebuild the city panorama, visual style or decorative details. Use the 3dref compiler for measured contact, wall rolls and body retiming; simple native operations and other catalog features use its native MCP route with scoped checks. Save/Export success alone is not proof that the planned beats, slowmo or camera roll were implemented.\n\n## Connection\n\nToonkit tool names may carry a client-specific prefix; use the connected tool whose name ends with the documented name. If the tools or the generation guide are unavailable, explain the connection problem and help the user authenticate or reconnect. Do not guess generation arguments or submit paid work meanwhile. Never include OAuth tokens or other credentials in output.\n\n## Shared boundaries\n\n- Scene/canvas authoring and generation use MCP. Only 3dref permits scoped visible timeline, navigation, Save and Export; never UI scene authoring or general canvas manipulation.\n- Paid work requires the AI workflow's live quote, confirmation and idempotency/recovery rules. Previz authorization does not authorize AI motion purchases or R2V.\n- Keep payloads in orchestration memory; emit compact summaries. Reuse unchanged schemas/guides/references. Do not load both structured and serialized copies.\n- Use the packaged 3D compiler/runtime (or its portable relay over the same bridge) for supported fresh scenes. It owns connection, journaling, application waits and one export transaction. Do not recreate adapters, transfer/readback scripts or per-batch files.\n- Preserve user work. Remove only confidently identified slop this run created when within scope, never prior results/caches for cosmetic tidiness.\n\n## AI-only authority\n\nThe SSOT ships next to this SKILL.md and governs model character/selection judgment. Live catalogs/quotes govern numeric limits/prices; the live generation guide governs contracts, billing and error semantics. Live contradictions win; flag stale guidance. If missing when an AI stage actually needs it, search the install root, then ask rather than guess. Fetch candidate model entries, not the full video catalog.\n\n## Delivery\n\nThe canvas holds actual deliverables. For standalone previz, the named editable node and source-linked exported video suffice; a short limitations note is optional. No full scenario/prompt/generation-node scaffolding for work with no AI jobs.\n\nSeparate executed, verified and unverified. Previz uses numeric/data fidelity and matched decoded-video metadata, with no routine screenshot QA. Generated image assets retain the AI workflow's visual inspection gate. Playable previz does not itself establish R2V compatibility. Return the canvas link and concise result, not temporary-file inventories or expiring URLs.\n"
}