Decide from the current character, action, relationship, or spatial information how the genre helps the expression. Preserve existing camera, color, space, action, material, and sound capabilities; adopt color palettes and scene examples as needed without overriding the user's story, assets, imaging method, or locked photography.
Use as needed per task
| Current task | Read and execute |
|---|---|
| Only asking about color values, scene presets, sources, or interfaces | Read the relevant part of the corresponding material below and answer directly; do not expand into a full design |
| New image, overall visual rewrite, or overall image diagnosis | Read Image Relationship Judgment; when genre alternatives are needed, read Visual Preset Library |
| Only change one problem in an already determined image | First read the current result and locked items; supplement only the material affecting that problem, review the modified area and necessary connections, and do not reopen overall candidates |
| Genre adaptation, action/continuity/sound, or structured handoff for storyboards/videos | Read Execution Contract for applicable parts; for a new visual direction also read image relationships, and directly inherit existing photography |
| Need to locate a specific failure | Look up by problem in Negative Cases, and do not by default apply all ten to the result |
| Need to state preset source or evidence level | Read Source Ledger; ordinary design does not repeatedly trace already included rules online |
Reuse materials already fully read in the same context and unchanged; for task changes, supplement only relevant parts. Each package is self-contained and does not read sibling skills, old versions, or personal knowledge bases.
Determine the image first, then choose genre techniques
Determine this round's medium, viewing purpose, subject/environment relationship, imaging method, allowed changes, and user-locked items from the existing input. Ask about gaps only when they substantially change the result and cannot be reasonably inferred; for a provided script, understand character goals and current states according to the actual covered text, and do not fill in plot from genre words alone.
- Photography, composition, light and color, and materials jointly serve the viewing order. Choose fixed or compound camera movement according to the action, and do not mechanically replace words like "grand", "oppressive", or "romantic" with fixed focal lengths, color schemes, slow push-ins, or aerial shots.
- A static image contains only information that can coexist at the same moment. Video then handles time, triggers, paths, sound, and end states; storyboard requests go to shot design, and only prompt requests compile generated text.
- Local revisions preserve uninvolved characters, appearance, counts, action results, dialogue, shot order, and photography; reference images assume only the responsibilities specified by the user and do not automatically change the story or imaging method.
- Light sources may be off-screen, and position and illumination must be explainable; supernatural light permitted by world rules has its basis. New objects, realistic plastic, animation, or illustration are all handled according to the target, without forcing wear, fog, wet surfaces, or photographic realism.
- Values are used for given constraints, explicit design choices, or real execution needs; when there is no basis, describe the visible relationships and do not fabricate color temperature, shadow proportion, or success rate.
Direct delivery and interfaces
Deliver only the visual plan, copyable prompts, parameters, or evidence-based diagnosis needed for this task. Use natural names for people, scenes, and props in the body text; do not expand a single image into a series, do not attach a video timeline to a still frame, and do not attach an asset ledger, ten-section fill-in form, and full self-check set to ordinary results. When storyboards and prompts are explicitly requested, deliver the same design separately; prefer existing formats.
When structured handoff is needed, retain style_module and style_route: the former retains the current package name string, and the latter retains the camera/color/scene/action/material/continuity keys, filled with the rules and parameters selected for this task.asset_contract、qc_checklist、negative_layers Provide only when handoff requires it; see the execution contract for specific fields. Do not arbitrarily change existing downstream key names or interfaces already used by the user; retain source status as design preset, not externally verified.
Before delivery, check only the currently applicable scope conservation, viewing relationships, space/light sources, and action and asset continuity; after fixing specific content when problems are found, recheck affected items. When generation is needed, use the tools actually callable by the host and the current authorization; report prompt completion, actual generation, image/video inspection, and user acceptance separately, and do not pass off internal checks as finished-output approval.