agentleFS
RandomNestRandomNest/aivideo-production-skills/skills/storyboard-generator/SKILL.md

storyboard-generator

Skill15 starsChanged 9 months agoMITView on GitHub

Use when creating visual pre-visualization frames before committing to full motion generation. Trigger when users mention "storyboard," "visual preview," "composition test," or when regen risk is high and layout validation is needed.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before generating complex shots.

    line 30
  2. Distinctive:

    When multi-character blocking exists.

    line 31
  3. Distinctive:

    When new sets introduced.

    line 32
  4. Distinctive:

    When camera movement is non-trivial.

    line 33
  5. Distinctive:

    When regen risk classified as medium or high.

    line 34
  6. Distinctive:

    Before escalating to final resolution.

    line 35
  7. Distinctive:

    Do NOT use for trivial single-character static shots.

    line 37
  8. Distinctive:

    All required characters present.

    line 99
  9. Distinctive:

    No extra characters inserted.

    line 100

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Role

You are a visual composition validator.

Your responsibility is to generate low-cost visual previews that confirm:

  • Spatial layout
  • Character placement
  • Lighting compliance
  • Framing intention
  • Lock adherence

You reduce risk before committing to full render cost.


When To Use

Use this skill:

  • Before generating complex shots.
  • When multi-character blocking exists.
  • When new sets introduced.
  • When camera movement is non-trivial.
  • When regen risk classified as medium or high.
  • Before escalating to final resolution.

Do NOT use for trivial single-character static shots.


Context Requirements

Before proceeding:

  1. Review SHOTLIST_<SCENE_ID>_v###.
  2. Review relevant locks.
  3. Review WORLD_STATE_v###.
  4. Confirm shot complexity level.
  5. Confirm cost tier.

Required Inputs

  • shot_id
  • Relevant GenPack (draft or partial)
  • Lock artifacts
  • Shot complexity classification
  • Resolution tier (always proxy for storyboard)

Required Artifacts

STORYBOARD_<SHOT_ID>_v###.png (or equivalent image artifact)

AND

STORYBOARD_REPORT_<SHOT_ID>_v###.md

Storyboard report must include:

  • Composition validation
  • Character placement check
  • Set anchor presence check
  • Lighting compliance check
  • Drift risk estimate
  • Recommendation (Proceed / Adjust / Simplify)

Process

  1. Generate low-resolution static frame.
  2. Compare against lock constraints.
  3. Validate:
    • Character position
    • Facial clarity (if hero-tier A)
    • Set anchors visible
    • Lighting directionality
  4. Assess visual clutter.
  5. Identify drift markers early.
  6. Recommend structural simplifications if needed.

Evaluation Checklist

  • All required characters present.
  • No extra characters inserted.
  • Set anchors visible.
  • Lighting consistent with lock.
  • Composition supports emotional beat.
  • No unexplained props.
  • Camera framing matches shot plan.
  • Drift risk acceptable.

Gate Behavior

FAIL if:

  • Lock violations visible.
  • Character appearance drift.
  • Set layout altered.
  • Lighting inconsistent.
  • Composition unclear.
  • Unjustified visual additions.

PASS when:

  • Visual anchors confirmed.
  • Framing intentional.
  • Drift risk low.
  • Shot geometry validated.

Escalation Policy

Escalate to Vision Tier if:

  • Complex blocking unclear.
  • Depth layering ambiguous.
  • Multi-plane staging required.
  • Action choreography spatially dense.

Escalate to Judgment Tier if:

  • Composition affects emotional interpretation.
  • Symbolism depends on framing nuance.

Common Failure Modes

  • Visual clutter.
  • Character too small in emotional shot.
  • Face obscured in hero-tier shot.
  • Background inconsistencies.
  • Lighting shift.
  • Added background extras.
  • Camera angle contradicts shot plan.

Related Skills

  • shot-planner
  • prompt-packager
  • qc-grader
  • cost-optimizer
  • continuity-supervisor

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.