Decide from the current character, action, relationship, or spatial information how the genre helps express. Retain the existing camera, color, space, action, material, and sound capabilities; adopt the color chart 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 a finalized image | First read the current finished work and locked items; add only the material affecting that problem, review the modified area and necessary connections, and do not reopen overall candidates |
| Genre adaptation of storyboards/videos, action/continuity/sound, or structured handoff | Read Execution contract for the applicable parts; for a new visual direction also read image relationships; existing photography is inherited directly |
| Need to locate a specific failure | Look up by problem in Negative examples, and do not default to applying all ten to the finished work |
| Need to state the preset source or evidence level | Read Source ledger; ordinary design does not repeatedly trace included rules online |
Reuse material already fully read in the same context and unchanged; when the task changes, add only the 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 the genre technique
From the existing input, determine this round's medium, viewing purpose, subject/environment relationship, imaging method, allowed changes, and user-locked items. Ask about gaps only when they substantially change the result and cannot be reasonably inferred; for a given 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 material jointly serve the viewing order. Choose fixed or compound camera movement according to 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 body text.
- Local revision preserves uninvolved characters, appearance, counts, action results, dialogue, shot order, and photography; reference images bear 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 can be explained; supernatural light allowed by world rules has its basis. New objects, realistic plastic, animation, or illustration are all handled per the target, without forcing wear, fog, wet surfaces, or photographic realism.
- Values are used for given constraints, explicit design choices, or actual execution needs; when there is no basis, describe 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 instance. Use natural names for people, scenes, and props in the body; 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 form, or full self-check to ordinary results. When storyboards and prompts are explicitly requested, deliver the same design separately, and prefer existing formats.
When a 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 key, filled with the rules and parameters selected for this instance.asset_contract、qc_checklist、negative_layers Provide it only when the 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, and retain the source status as a design preset, not externally verified.
Before delivery, check only the currently applicable scope conservation, viewing relationships, space/light sources, and action and material continuity; after fixing specific content when problems are found, recheck the 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 final approval.