Create a director book that turns screenplay scenes into performance, blocking, visual, camera, rhythm, transition, and sound intentions before individual shots are chosen.
Scanned 9/9/2026
Install to Claude Code
npx -y skills add badgids/Story-Film-Skills --skill director-book --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Director Book?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/badgids-director-book)More formats (shields.io, HTML) on the badges page.
---
name: director-book
description: Create a director book that turns screenplay scenes into performance, blocking, visual, camera, rhythm, transition, and sound intentions before individual shots are chosen.
disable-model-invocation: true
author: Alan Guice (Badgids)
license: Apache-2.0
---
# 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling