references/generation-prompt

Generates production-grade prompts for image and video generation models with typed reference anchors.

38|4|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/6174/recut --skill references-generation-prompt-6174
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: references/generation-prompt
Source: https://github.com/6174/recut/tree/main/service/skills/recut-director/references/generation-prompt
Command: npx skills add https://github.com/6174/recut --skill references-generation-prompt-6174

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Writing prompts for image and video generation models often produces inconsistent styles, drifting characters, and unverifiable reference bindings across shots. This Skill standardizes how a production-grade generation prompt is constructed so every shot reuses a frozen style block, declares typed reference anchors, and enforces sound-picture and negative constraints. ## Core Features & Use Cases - Fixed Prompt Structure: Builds every prompt in a strict five-section order: STYLE LOCK, reference anchor table, audio track, shot sequence, and negative constraints. - Typed Reference Anchors: Defines a controlled <reference> tag vocabulary with roles (pov, character, voice, style-ref, motion-ref, storyboard, and more) so every cited asset is machine-verifiable and hallucination anchors are rejected. - Multi-Shot Continuity Rules: Enforces one information change per shot, first/last frame contracts between shots, and explicit HARD CUT markers for coherent sequences. - Use Case: When directing an AI short film, use this Skill to translate confirmed shot intent and character assets into a submittable prompt where the protagonist's character image and voice reference are bound, the style is frozen verbatim, and each shot's end state matches the next shot's start state. ## Quick Start Write a generation prompt for the next three shots of my video using the frozen style template, binding the main character image and voice reference, with per-shot start and end states.

Frequently Asked Questions about references/generation-prompt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a prompt for an AI video generation model?▼

Structure the prompt in five fixed sections: a verbatim STYLE LOCK block, a typed reference anchor table, an audio track description, a shot sequence with one dominant motion per shot, and 4-6 specific negative constraints. Never include ratio, resolution, or duration parameters in the prompt body.

How to keep characters consistent across AI-generated video shots?▼

Bind a reference image with role="character" whenever the main character appears on screen, and reuse the frozen STYLE LOCK verbatim across all shots. Each shot's end state must equal the next shot's start state so continuity is enforced as a contract.

What reference roles can I attach to a video generation prompt?▼

The controlled role vocabulary includes pov, color-card, environment, character, prop, style-ref, storyboard, motion-ref, voice, sfx, and music. Voice, sfx, and music roles require audio assets, while color-card requires an image, and each role may be declared only once per prompt.

Can I use a storyboard grid image as a generation reference?▼

Yes, submit the entire storyboard sheet as a single image with role="storyboard" so it occupies only one reference slot. Only slice individual cells when the model handles storyboard references weakly or precise first/last frame endpoints are required.

Why does my AI video prompt produce drifting styles between shots?▼

Style drift happens when the style description is rewritten per shot instead of reused verbatim in a STYLE LOCK block. It also occurs when reference frames or clips are described with adjectives like "cinematic" instead of being bound as style-ref or motion-ref anchors.

What should not go into an AI video generation prompt?▼

Exclude technical parameters like ratio, resolution, duration, and modeType, which belong to the app adapter layer. Also avoid category-style negative words, empty quality adjectives, asset IDs in the model-facing string, and unbound reference tokens.