multi-model-animation-studio-notes

Organize animation and manhwa/webtoon production notes across multiple AI models and reference sources. Use when extracting reference frames from recap videos or webtoon pages, planning scene packets, comparing model lanes, or preserving arc-level world continuity while allowing deliberate per-panel style shifts.

6 stars

Best use case

multi-model-animation-studio-notes is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Organize animation and manhwa/webtoon production notes across multiple AI models and reference sources. Use when extracting reference frames from recap videos or webtoon pages, planning scene packets, comparing model lanes, or preserving arc-level world continuity while allowing deliberate per-panel style shifts.

Teams using multi-model-animation-studio-notes should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/multi-model-animation-studio-notes/SKILL.md --create-dirs "https://raw.githubusercontent.com/issdandavis/SCBE-AETHERMOORE/main/external/codex-skills-live/multi-model-animation-studio-notes/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/multi-model-animation-studio-notes/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How multi-model-animation-studio-notes Compares

Feature / Agentmulti-model-animation-studio-notesStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Organize animation and manhwa/webtoon production notes across multiple AI models and reference sources. Use when extracting reference frames from recap videos or webtoon pages, planning scene packets, comparing model lanes, or preserving arc-level world continuity while allowing deliberate per-panel style shifts.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Multi Model Animation Studio Notes

Use this skill to turn scattered research, prompts, frames, screenshots, and render feedback into structured production notes that survive handoffs between tools, agents, and sessions.

This skill is story-first. It is not for forcing a single frozen art style across every panel.

## Use When

Trigger this skill when the work involves any of the following:

- extracting reference frames from YouTube recap videos or screenshots from manhwa/webtoon pages
- breaking a scene into reusable visual beats, narration notes, and prompt-ready style cues
- combining notes from GPT, Claude, image generators, video generators, editors, or browser research lanes
- comparing outputs from different model lanes for the same shot or scene
- locking what must stay stable for an arc while allowing deliberate style changes for comedy, emphasis, flashback, memory, or dramatic compression
- preparing a handoff packet so another person or agent can continue production without re-discovering prior decisions

## Creative Rule

Consistency is not uniformity.

Keep the world grounded per arc:

- environments
- architecture
- location geography
- prop logic
- core costume anchors
- lighting logic
- mood palette

Allow character rendering and panel finish to shift on purpose when the story benefits:

- chibi for comedy or emotional puncture
- painterly for awe, grief, or mythic scale
- sketch-like for memory, speed, or instability
- exaggerated expression panels for reaction beats

The skill should preserve `world continuity` while tracking `panel effect overrides`.

## Core Workflow

1. Capture the project frame.
- Record the title, target platform, duration, aspect ratio, audience, and delivery goal.
- Note whether the output is a recap video, vertical scroll episode, teaser, animatic, or reference packet.

2. Collect source references.
- For videos, sample frames around the target scene and record timestamps.
- For webtoon pages, capture representative panels and record chapter/page identifiers.
- Keep the source URL or source title with every extracted reference.

3. Split `Arc Locks` from `Panel Flex`.
- `Arc Locks` are the details that should remain stable across the arc.
- `Panel Flex` is where deliberate style variation is allowed.
- Never let a temporary panel gag rewrite the world model.

4. Break work into scene packets.
- Treat each scene or shot as a separate note unit.
- Give each unit a stable ID such as `scene-03-shot-02`.
- Record the narrative purpose before describing visuals.

5. Separate model lanes.
- Keep prompts, settings, and results grouped by model or tool.
- Do not merge outputs from different systems into one unlabeled note block.
- Preserve seeds, reference-image usage, timing values, and key generation parameters when available.

6. Build the narration lane.
- Treat on-screen recap subtitles as a narration source, not automatically as character dialogue.
- Capture the text beat, tone, and timing.
- Mark what should become TTS narration, what should stay visual text, and what should remain silent.

7. Record decisions explicitly.
- Mark outputs as `approved`, `candidate`, `rejected`, or `needs-revision`.
- When something becomes canon, note why it was selected and what it replaces.
- Keep rejected variants briefly documented so the same failed branch is not retried blindly.

8. Emit a handoff-ready summary.
- End with the current best version, open questions, blockers, and next actions.
- Keep the final packet short enough that another lane can resume work quickly.

## Arc Locks vs Panel Flex

Use these categories every time the task involves manhwa/webtoon work.

### Arc Locks

These should usually remain stable inside the same arc:

- room layout and environment identity
- architecture and worldbuilding cues
- recurring prop placement and costume anchors
- faction colors, emblem usage, and magic/world rules
- baseline body proportions and recognizable character features

### Panel Flex

These can change deliberately when the story calls for it:

- chibi reaction panels
- comedic face distortion
- painterly splash treatment
- sketch-memory treatment
- speed-line or impact-frame exaggeration
- selective detail spikes on key dramatic panels

If a style shift is used, note the purpose. Do not treat it as random variance.

## Reference Extraction Checklist

For each useful frame or panel, record:

- source URL or title
- timestamp, chapter, or page ID
- shot type: wide, medium, close-up, insert, reaction, reveal
- characters present and pose logic
- environment anchor
- text overlay, subtitle, SFX, or narration present on screen
- palette and lighting notes
- emotional function of the image
- reusable style tags

The goal is not to copy the image. The goal is to extract techniques that can be reused legally and intentionally.

## Scene Packet Template

Use this template when turning rough notes into a durable production packet:

```md
## scene-01-shot-03

- Story Beat: What the audience should understand or feel here
- Purpose: Why this shot exists in the sequence
- Duration: Estimated seconds or beats
- Camera: Framing, motion, lens feel, angle
- Action: What visibly changes in the shot
- Narration/Text: Recap subtitle, dialogue, SFX, or silence
- Source References: Timestamps, panel IDs, or URLs that informed the shot
- Arc Locks: Environment and canon details that must not drift
- Panel Flex: Any allowed style override and why it exists
- Model Lanes:
  - Planning lane: GPT/Claude reasoning, beat notes, prompt drafts
  - Image lane: Prompt, seed, reference inputs, best output
  - Video lane: Prompt, timing, camera instructions, best output
- Decision: approved | candidate | rejected | needs-revision
- Next Step: Exact follow-up action
```

Convert nested lists to the user or repo's preferred format if a project template already exists.

## What Makes A Recappable Manhwa Scene

Based on successful recap patterns, look for these signals:

- a clear story beat that can be summarized in one or two lines
- readable emotional expressions with deliberate exaggeration
- strong environment anchors so the world feels coherent
- a mix of close-up, mid-shot, and reveal framing
- on-screen narration or text that cleanly carries exposition
- repeatable costume and setting cues that survive compression into recap format
- a few high-detail cornerstone panels surrounded by simpler bridge panels

Do not chase maximum detail in every frame. Use detail as emphasis.

## Comparison Rules

- Compare models on concrete output traits: composition, emotional readability, facial stability, background fidelity, text overlay legibility, motion quality, and editability.
- Keep subjective reactions separate from production facts.
- If a model is strong only for ideation or only for final polish, say that directly.
- Prefer one canonical prompt per approved shot, with alternates kept as fallback notes rather than mixed into the main prompt.
- Judge style shifts by whether they improve the beat, not whether they look identical to nearby panels.

## Deliverables

A good output from this skill usually leaves behind one or more of these:

- a reference atlas with timestamps or panel IDs
- an arc-lock sheet for environments and canon anchors
- a scene-by-scene storyboard note packet
- a model comparison table with an explicit recommendation
- a narration strip that can feed custom TTS
- a short handoff note with approved assets and next render actions

Related Skills

multi-agent-cloud-offload

6
from issdandavis/SCBE-AETHERMOORE

Deterministically sort, bundle, verify, and offshore local files through multiple AI/model lanes while capturing training rows and method evidence. Use when Codex needs to inventory folders, batch-process files, upload them to cloud targets such as rclone-backed Google Drive, Hugging Face, or GitHub, and only delete sources after the configured number of verified targets succeed.

multi-agent-review-gate

6
from issdandavis/SCBE-AETHERMOORE

Run a structured review gate before merging multi-agent outputs. Use when multiple agents have produced work packets that need quality checks, conflict detection, and approval before integration.

multi-agent-orchestrator

6
from issdandavis/SCBE-AETHERMOORE

Coordinate multi-agent workflows end to end. Use when a task should be decomposed into parallel sub-work with explicit ownership, dependency ordering, collision avoidance, checkpoint tracking, and final output recomposition.

hugging-face-model-trainer

6
from issdandavis/SCBE-AETHERMOORE

This skill should be used when users want to train or fine-tune language models using TRL (Transformer Reinforcement Learning) on Hugging Face Jobs infrastructure. Covers SFT, DPO, GRPO and reward modeling training methods, plus GGUF conversion for local deployment. Includes guidance on the TRL Jobs package, UV scripts with PEP 723 format, dataset preparation and validation, hardware selection, cost estimation, Trackio monitoring, Hub authentication, and model persistence. Should be invoked for tasks involving cloud GPU training, GGUF conversion, or when users mention training on Hugging Face Jobs without local GPU setup.

scbe-training-pair-authoring

6
from issdandavis/SCBE-AETHERMOORE

Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.

scbe-spin-conversation-engine

6
from issdandavis/SCBE-AETHERMOORE

Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.

scbe-research-training-bridge

6
from issdandavis/SCBE-AETHERMOORE

Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.

scbe-document-management

6
from issdandavis/SCBE-AETHERMOORE

Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.

scbe-colab-bridge

6
from issdandavis/SCBE-AETHERMOORE

Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.

scbe-claim-to-code-evidence

6
from issdandavis/SCBE-AETHERMOORE

Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.

scbe-autonomous-worker-productizer

6
from issdandavis/SCBE-AETHERMOORE

Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.

long-form-work-orchestrator

6
from issdandavis/SCBE-AETHERMOORE

Run long-form engineering work in checkpointed phases with deterministic artifacts, resilience handling, and end-of-run reliability reporting.