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/visual-asset-to-jingzao.md
View on GitHub# Visual asset to Jingzao
For requested product CG styles, use [product CG direction](product-cg-direction.md)
and only the selected capsule within this existing handoff. Preserve target facts
and current generation scope.
Use this handoff only after DIR has decided that a formal image asset needs a
maintainable visual spec, reference-aware compilation, an edit/preserve plan, or
complex continuity/layout control. It is not the default for every image.
Typical triggers include a multi-view character master, multiple required
references, exact scene geography, a high-risk prop state, a mask/region edit,
or a previously observed material/artifact failure. A simple single-subject
image with no continuity, attachment, edit, or precision-layout requirement may
keep the concise direct ImageGen path.
Standalone asset requests use the existing visual plan with `scope: asset_only`
and `medium: still`; leave time-based fields null and timeline arrays empty.
The same active-asset and handoff checks apply without a fictitious film brief.
DIR owns the asset ID, role, purpose, truth hash, dependency order, approved
upstream artifacts, and downstream state. `jingzao-image-forge` owns the
`visual_generation_spec`, prompt compilation, prompt review, reference handoff,
and image-call plan. The host image tool remains the execution adapter. Neither
prompt compilation nor a successful tool call grants visual approval.
When a selected Jingzao style capsule is used, copy the exact chosen JSON into
the project and bind it as `output_spec.style_capsule: {relative_path, sha256}`.
Compile with `--style-capsule PATH`; DIR replays those same bytes and that option.
The capsule is a text/style input, not an image attachment or an extra identity
reference. Preserve its relevant material, palette and character-adaptation rules
alongside the target's authoritative five-view/layout and subject facts. Do not
replace a style system with one dark palette, fabric or decorative formula.
Read the current provider's conditional style references as well as its base
references and bind them in `reference_reads`. Changsheng costume work in
Jingzao v1.8.0 also needs `references/changsheng-wardrobe-system.md`; its old
v1.7.0 test capsule is historical evidence, not a default generation source.
The handoff must bind:
- the active visual-plan snapshot and asset truth;
- the Skill Stack receipt that selected `jingzao-image-forge` for
`visual_asset_compile`;
- the installed Jingzao Skill body and exact reference files read;
- the selected asset-foundation design stages and any required image-reference hashes;
- the input request, validated visual spec, validation receipt, compiled prompt
manifest, prompt hash, and ImageGen call-plan status;
- the delivery route without claiming that an image was generated.
The inventory-derived visual plan stores `compile_route` as `direct_concise`,
`selected_skill_handoff`, or `deterministic_assembly`; execution cannot infer a
direct route merely because the handoff is absent. Before an asset exists, use
the `in_progress` design pass described in `asset-foundation-pass.md`; do not
require the image being created or a post-generation stress report. Its selected
stages bind owners, collaborators and exact structured artifact hashes; arbitrary
nonempty Markdown cannot replace them. A complete certified pass remains valid
for existing assets. The Jingzao spec must match the active
operation and purpose. Every image reference must already appear in the
foundation source set with an allowed rights/approval state, then appear exactly
once as a local `must_attach` input and in the compiled call plan.
An authored 2D layout/sketch can be a `planning_only` foundation source and a
`layout` input with exact path/hash and `reference_only_approved` scope. It controls
only its declared arrangement, never identity or material. A layout declaring
`spatial_source` still requires the verified spatial export; an ordinary panel
guide does not need to impersonate a measured 3D scene.
Validation replays the current DIR selector and the hash-bound Jingzao validator
and compiler from sealed copies. On macOS provider replay runs with isolated
Python, a minimal environment, no network, no home-directory reads, and no file
writes outside the replay directory. Provider identity failure stops before any
script execution. Replay uses the exact reference bytes that were hash-checked,
and compilation starts only after spec validation succeeds. Provider and project
roots must not contain each other. For edits, add Lira or constraint input only
when needed.
The execution packet must consume the exact compiled prompt hash from this
handoff. Missing provider files, changed upstream truth, unresolved required
references, or a non-ready ImageGen call plan
blocks the formal asset. A direct DIR prompt may still be used for rough or
low-risk work, but it cannot impersonate this handoff.
Accept `ready`, or the provider's genuine `approved` result for
`length_and_reference_complexity_only` or
`surface_risk_length_and_reference_complexity`, only with exact replay.
`--approve-review` is the executor's review of nonblocking prompt complexity or
intentional surface language, not another user approval or visual acceptance.
Detected contamination and empty prompts remain blocked. Do not shrink style
detail merely to satisfy an obsolete DIR approval whitelist. Automated residue
checks cover known wording, not every semantic conflict.
Recheck installed provider identity after an update and reprepare affected
unexecuted calls. Preserve completed/approved image versions and their chosen
style source; a provider update is not permission to restyle them.
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: 472k | 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 |