agentleFS
badgidsbadgids/Story-Film-Skills/skills/director-book/SKILL.md

director-book

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Create a director book that turns screenplay scenes into performance, blocking, visual, camera, rhythm, transition, and sound intentions before individual shots are chosen.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read core contract, CHARACTER_PROFILE.md, dramaturgy rules, film grammar, screenplay, canon, current story state, continuity, and …

    line 13
  2. Very specific:

    Write 03_preproduction/director_book.md scene by scene.

    line 14
  3. Distinctive:

    Use canonical movement/stillness and ensemble baselines as performance defaults, then account for current relationship and story state.

    line 16
  4. Distinctive:

    Keep camera strategy at scene level until a shot has a specific purpose.

    line 17
  5. Distinctive:

    Do not direct actors with abstract emotion only.

    line 18
  6. Distinctive:

    Every scene has a clear directorial strategy that a shot designer can translate into setups without inventing the scene's intent.

    line 22

≈ “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

Director Book

Workflow

  1. Read core contract, CHARACTER_PROFILE.md, dramaturgy rules, film grammar, screenplay, canon, current story state, continuity, and breakdowns.
  2. Write 03_preproduction/director_book.md scene by scene.
  3. For each scene, state: audience question, immediate desire, obstacle, power changes, geometry, gaze, rhythm, character objectives, blocking logic, visual strategy, camera behavior, optional dynamic register, light logic, sound perspective, transition in, transition out, performance notes, recurring motif, break or reversal, and final image or sound.
  4. Use canonical movement/stillness and ensemble baselines as performance defaults, then account for current relationship and story state. Scene-specific exceptions are allowed when motivated.
  5. Keep camera strategy at scene level until a shot has a specific purpose. A dynamic register never forces camera motion.
  6. Do not direct actors with abstract emotion only. Use playable behavior and circumstance.

Done

Every scene has a clear directorial strategy that a shot designer can translate into setups without inventing the scene's intent.

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.