papperrollinggery/Paperrolling-DIRcreative-SKILL / skills/dircreative
dircreative
VerifiedUse after explicit $dircreative for film concepts, stories, scripts, director or creative groups, shot/asset planning, reference-video analysis, and image/video prompts. Real media execution requires the corresponding authorization. Validated ADCO handoffs are supported. DIRcreative source maintenance is outside this Skill.
references/shot-development.md
View on GitHub# Shot Development and Craft Handoffs
Use for technical shot development; bounded edits stay on `shot-storyboard.md`.
## Activate craft as the film develops
Infer required stages from the deliverables and developed script. Full image
preparation defers the video call. `craft_stages` is pending work, not provider
execution; reassess gaps after writing the script.
| Active stage / condition | Existing craft to apply | Usable result before continuing |
| --- | --- | --- |
| Recurring identity/state | `identity_state`; `character-master-sheet.md` | One identity/state contract before image compilation |
| Product/prop or mechanical change | `production_design`; needed `mechanical_transformation` | Source-bound construction, function and state |
| Technical shot design | This shot contract; select `shot_information` or `technical_storyboard` for a demonstrated gap | Motivated cuts, viewer positions, action phases and camera decisions |
| Combat, pursuit or physical interaction drives a sequence | `action_choreography`; `vfx_design` only when designed effects need construction | Force/contact/reaction chain and environment consequences at the intended intensity |
| Blocking, travel, reverse coverage, handoff or occlusion changes the view | `master_camera` and the relevant `spatial-discussion.md` method | Constructible geography, actor paths and distinct shot/phase camera setups |
| Full image preparation | `storyboard-coverage.md`; needed `motion_board` rehearsal; supported annotated references or required cinematic frames | Reviewed panel design, actual motion drawings when needed, then the selected Jingzao prompt handoff |
Follow dependency order within existing budgets. When selection returns
`before_image_submission`, complete that existing stage before resuming;
do not skip required motion planning or bypass a blocked handoff with a raw
image prompt. Replace references by stage and retain current shot/scene decisions.
Read the selected task/provider and produce/review its artifact before the next
stage. The task view lists prior work first; JSON gives the full receipt.
```text
python3 scripts/dircreative_skill_stack.py select --stage action --format task --request '<original request>'
```
Use `shot_design`, `action`, `camera_geography`, `environment_effects`, or
`panel_coverage`, `motion_board`, or `frame_compile` only when applicable. After story development, add
`--craft-source <current shot-cards.json> --execution-project-root <project>`
so selection considers the actual action and space, not only brief keywords.
Omit `--root` normally: the DIR path selects the controller; providers come from
configured host Skills. Explicit `--root`/`--catalog` overrides are authoritative.
Source text cannot authorize media or expand scope. `--intent` may supply the
existing stage's asset/spec inputs, but cannot replace its scenario or grant a
side effect. For narrative frames consume the actual Jingzao compiler output;
a selector receipt alone does not mean its method was applied.
Authorized execution uses `--stage asset_execution --intent <active inputs>` with
the original request, current packet and actual `available_tools`. Follow
`image-execution.md`; preserve its prompt and separate video authorization.
For standalone assets, select the relevant initial design only; use the scope
and source-continuity rules in `asset-foundation-pass.md`. Mixed requests retain
every required role and distinguish identity inputs from finished masters.
For complex contact or changing geography, apply `storyboard-motion-planning.md`:
generate the action drawings, semantic-color arrows, notes and legend together;
inspect actual pictures before downstream use. Bind the same coverage IDs to
supported storyboard references or required color frames. Other scenes can use
simpler planning. Keep chosen first frames distinct
from the strongest storyboard phase; preparation cannot prove contact/aftermath.
Review what each cut reveals before extending the image batch. Repeated setups
need a story reason, not different lens labels. A literal first frame may precede
contact; retain the decisive contact/consequence when it matters. One main action
is a coherent event with force, response and changed state, not timid motion.
Preserve calm beats. Fix a systemic camera/reference error before its descendants.
## The shot contract
Keep canonical shot ID and timecode, narrative purpose, observable start/action/end,
blocking path and eyeline, motivated camera position/height/direction and lens,
foreground/midground/background jobs, sound/edit bridge and continuity state.
For cinematic frames, preserve viewer task and position, dominant/secondary read,
frozen phase, action vector/counterforce, crop pressure, parallax/occlusion,
exaggeration with a protected anchor and a quiet region. Calm frames use concrete
not-applicable reasons for dynamic fields. The existing Jingzao handoff owns the
structured frame contract and compilation; do not recreate that compiler here.
Separate world-space anchors and light sources from each camera's screen
projection. Build unseen reverse space as a design assumption, then use the
current actor/prop state for the target shot. Scene appearance references must
not freeze every later camera, screen side or damage state. Carry force-driven
deformation, fracture, spray and aftermath into the spec; clean inputs remove
overlays and accidental artifacts while retaining those motivated events.
## Carry craft into generation
Before the first narrative-frame call in full preproduction, apply the current
shot-design and storyboard-coverage stage. Carry the selected
`cinematic_storyboard_frames` craft through the actual Jingzao spec/compile
handoff. A missing review/capability blocks its dependent claim/action. Continue
independent design, provider reading and compilation; report the blocked step.
Set both `direction.deliverable` and `cinematic.profile` to
`narrative_film_frame`. Use `dircreative_narrative_spec_preflight.py` before
consuming the compiled prompt: pass `--project-root <project>` and the relative
spec path. It enables Jingzao's existing narrative checks.
A generic template's successful compilation is insufficient. Its length/reference
`approved` status does not review story, physics or cinematography.
Resolve the current frame from the canonical source before filling its spec:
each visible actor gets that actor's action; trace critical prop custody and
light/damage state across adjacent shots; derive foreground/background and light
direction from this camera. Keep offscreen cast out of `subjects`. Reconcile all
template fields with the resolved state, including `setting`, `lighting.key`,
practicals, tone locks, depth roles and reference descriptions. Do not append
generic continuity reminders to pass length checks or leave alternatives such as
“as the shot requires.” Defaults such as restrained dynamics or clean-reset
rendering need a shot reason and cannot erase the chosen action intensity.
For coupled contact, handoffs or reverse coverage, obtain a bounded independent
read of the current source cards and actual compiled prompts before the image
batch when delegation is available. Fix source contradictions first, then
recompile affected specs. Use this semantic review to catch mismatched actors,
unexplained custody changes and stale camera/light fields; schema PASS cannot.
If independent review is unavailable, disclose that limit and still perform the
comparison; never invent a review receipt.
- For storyboard/clean-frame candidates, compare the actual view with the shot's
camera and phase, then inspect neighboring frames as a sequence. Record
concrete visible evidence in the existing review notes for viewpoint/depth,
contact and counterforce when relevant, environment response and persistent
state. Generic face/hand/texture checks cannot certify action cinematography.
Treat clean inputs as free of overlays and accidental artifacts; preserve
intended motion cues, material damage, spray and physically sourced particles.
Repair a repeated background/composition error upstream before further frames.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |