{"id":"0f151942-8e5e-4020-b45f-03cd0584e1f1","slug":"ai-animation-production-skill","kind":"skill","name":"ai-animation-production-skill","summary":"A reusable, evolving production workflow for AI-assisted animation — from story, Masters and shot planning to generation, recovery, editing and archive.","owner":"wyh245611-beep","repoUrl":"https://github.com/wyh245611-beep/ai-animation-production-skill","license":"Apache-2.0","licenseTier":"permissive","trust":"community","stars":2,"match":null,"fewStars":true,"format":"skill","createdAt":"2026-09-07T18:11:58.000Z","addedAt":"2026-10-21T23:49:56.327Z","logoUrl":"https://avatars.githubusercontent.com/u/286568683?u=eba0eb97c880809924f6c780811f8676e1447af7&v=4","linkOnly":false,"collection":null,"skillPath":null,"categories":["writing"],"tags":[],"runtime":"binary","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-26T21:21:45.082Z","sample":false,"url":"https://conduits.dev/tools/ai-animation-production-skill","language":"","transports":["stdio"],"install":{},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"# AI Animation Production Skill\n\nA reusable, evolving production workflow for AI-assisted animation.\n\nThis repository is built around **production reasoning**, not one specific model or platform.\n\n## Scope Boundary\n\nAI Animation Production Skill is currently a **production orchestration and decision framework**, not a fully autonomous animation generation engine. Future adapters and tools may connect an execution layer while `SKILL.md` remains the authoritative source for detailed Scope rules.\n\nIt helps answer questions such as:\n\n- What must be locked before generation?\n- When is a concept image ready to become a Master?\n- When should one cinematic shot be split into several generation nodes?\n- When should a new supporting still be created after video production has already begun?\n- How should character entrances, camera direction, and dialogue ownership stay continuous?\n- When should a result be trimmed, repaired, split, or fully regenerated?\n- How can generation credits and time be protected?\n- How should project state survive across sessions, tools, and agents?\n\n## Core Idea\n\n> A good AI-animation workflow is not a list of tools. It is a system for controlling story state, visual identity, continuity, cost, and failure.\n\nThe pipeline is iterative:\n\n```text\nProject Setup\n→ Story / Script Breakdown\n→ Masters\n→ Shot Planning\n→ Still + Voice Assets\n→ Video\n→ Review\n→ Repair / New Supporting Asset / Node Split\n→ Editing\n→ Export / Archive\n```\n\nThe workflow may move backward when production reveals a missing state.\n\nThat is expected.\n\n## Important Rules\n\n- One cinematic shot does **not** have to equal one generation node.\n- The end of Node A should intentionally prepare the beginning of Node B.\n- Do not rely on “continue the previous node” unless the platform actually persists state.\n- A character should not appear from nowhere merely because the composition looks balanced.\n- Supporting stills can be created **just in time** after video reveals a missing state.\n- Speaker ownership and visible lip-sync requirements should be explicit.\n- A good-looking draft is not automatically a Master.\n- Use the default two-failure retry guardrail unless the Project Profile defines another policy.\n- Minor defects should be solved in editing when that is safer and cheaper.\n- Tool choice follows the production need, not brand loyalty.\n- Research is not validation.\n\n## Visual Modes\n\nThe core workflow can support:\n\n- 2D / Flat\n- 3D\n- Hybrid\n\nDetailed full-2D and full-3D specializations are intentionally deferred until real production validates them.\n\n## Repository Structure\n\n```text\nai-animation-production-skill/\n├── SKILL.md\n├── README.md\n├── CHANGELOG.md\n├── STATUS.md\n├── references/\n│   ├── project-initialization.md\n│   ├── story-script-breakdown.md\n│   ├── character-workflow.md\n│   ├── environment-workflow.md\n│   ├── storyboard-shot-planning.md\n│   ├── camera-continuity.md\n│   ├── still-image-production.md\n│   ├── voice-production.md\n│   ├── video-production.md\n│   ├── prompt-rules.md\n│   ├── review-recovery.md\n│   ├── editing-export.md\n│   ├── file-naming-archive.md\n│   └── tool-registry.md\n├── templates/\n│   ├── project-profile.md\n│   ├── project-state.yaml\n│   ├── shot-spec.md\n│   ├── decisions.yaml\n│   ├── handoff.md\n│   ├── experience-update.md\n│   ├── tool-record.md\n│   └── failure-log.md\n└── examples/\n    └── example-project-profile.md\n```\n\n## Quick Start\n\n1. Read `SKILL.md`.\n2. Determine the Complexity Level: `LIGHT`, `STANDARD`, or `LONG-FORM`.\n3. Choose the minimum production structure justified by that level. A LIGHT task may need only an objective, necessary references, and a minimal Shot Spec; STANDARD and LONG-FORM projects should use the corresponding records defined in `SKILL.md`.\n4. Define the necessary Visual Mode, source-of-truth assets, retry policy, and constraints.\n5. Use `references/story-script-breakdown.md` and `references/storyboard-shot-planning.md` to turn story beats into shots and generation nodes when the project requires them.\n6. Build only the Masters and assets needed for the first viable production pass.\n7. Use the routing table in `SKILL.md` to open only the relevant reference module.\n8. During production, record meaningful failures with `templates/failure-log.md` when the selected production structure requires it.\n9. Promote only validated, reusable lessons into the Skill.\n\n## Tool Evidence\n\nTools are labeled by evidence level:\n\n`VALIDATED`, `EVALUATED`, `RESEARCHED`, `EXPERIMENTAL`, `DEPRECATED`.\n\nSee:\n\n`references/tool-registry.md`\n\nThe originating workflow validated several tools in real production and researched others as alternatives.\n\nA tool being listed does not mean every user should adopt it.\n\n## Rights, Consent, and Provenance\n\nBefore publication or collaboration, confirm relevant rights for:\n\n- voice cloning\n- reference images\n- footage\n- music\n- sound effects\n- third-party character / design material\n\nRecord provenance when it matters.\n\n## Current Stage\n\nThis repository is a **v0.2.0-pre workflow** built from real AI-animation production experience.\n\nThe core production loop is complete enough for review and real project testing.\n\nIntentionally deferred:\n\n- dedicated LibTV CLI adapter\n- LibTV internal Agent adapter\n- full 2D specialization\n- full 3D specialization\n- additional platform adapters\n- more case studies\n\n## Contributing / Iteration\n\nWhen adding a rule, prefer:\n\n```text\nProblem\n→ Context\n→ Cause\n→ Tested Solution\n→ Reuse Condition\n→ Scope\n```\n\nDo not turn one isolated accident into a universal rule.\n\n## License\n\nThis project uses the **Apache License 2.0**.\n\nReuse and contribution rights are governed by the Apache License 2.0.\n\n## Third-Party Tools\n\nThird-party product and project names are included only to document interoperability and production options.\n\nTheir inclusion does not imply affiliation or endorsement.\n\nCapabilities may change; verify official documentation before following tool-specific setup instructions.\n"}