Skip to content

zhangzhangco/film-production-skills / skills/compile-generation-prompts

compile-generation-prompts

Verified

Compile approved story, asset, and shot artifacts into provider-neutral semantic shot data, storyboard frames, image requests, video requests, provider adapters, and quality gates. Use when a film-production workflow needs traceable generation packages without changing narrative facts.

Compile Generation Prompts

Compile production decisions into executable requests. Do not use prompt writing as an opportunity to redesign the story.

Inputs

Read the shared request envelope and validate payload against schemas/input.schema.json.

Require:

  • story blueprint
  • production assets
  • shot plan
  • generation targets

Provider capability profiles are optional. Without one, produce provider-neutral requests and do not claim model compatibility. With profiles, require provider, model, media type, capability flags, and explicit limits.

Workflow

  1. Audit upstream status, IDs, asset references, duration, and continuity.
  2. Build a semantic shot representation that freezes story facts.
  3. Define storyboard frames as single observable moments.
  4. Compile image requests from identity, environment, composition, action state, lighting, and continuity constraints.
  5. Compile video requests from start state, action progression, camera motion, performance change, and end state.
  6. Select a generation mode from text-to-image, text-to-video, image-to-video, first/last-frame video, multi-reference video, or audio.
  7. Match each request against an explicit provider capability profile.
  8. Adapt only supported fields and return structured incompatibility issues with practical alternatives.
  9. Run quality gates for identity, action count, duration, spatial continuity, reference roles, and parameter support.

Output rules

Return:

  • skill: compile-generation-prompts
  • data.shot_ir
  • data.storyboard_frames
  • data.image_requests
  • data.video_requests
  • data.provider_requests
  • data.quality_gate

Every request must reference segment, beat, and asset IDs. Keep static frame descriptions separate from temporal video instructions. Every provider request must state the selected model, generation mode, asset references, reference roles, compatibility result, and mismatch alternatives.

Boundaries

  • Do not invent dialogue or sound.
  • Do not let style language weaken identity constraints.
  • Do not place unsupported parameters in provider requests.
  • Do not silently drop first-frame, last-frame, multi-reference, character reference, duration, or aspect-ratio requirements.
  • Do not combine unrelated dominant actions into one short video request.
  • Do not call generation services.

Read references/field-guide.md for compilation order and quality gates.

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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall