Decide from the current character, action, relationship or spatial information how the type helps the expression. Retain the existing camera, color, space, action, material and sound capabilities; adopt color tables 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 type alternatives are needed, read Visual preset library |
| Fixing only one problem in an already determined image | First read the current finished work and locked items; supplement only the material affecting that problem, review the modified area and necessary connections, and do not reopen overall candidates |
| Type adaptation, action/continuity/sound or structured handoff for storyboards/video | Read Execution contract applicable parts; for a new visual direction also read image relationships; inherit existing photography directly |
| Need to locate a specific failure | Look up by problem in Negative cases, do not apply all ten to the finished work by default |
| Need to explain preset sources or evidence level | Read Source ledger; ordinary design does not repeatedly trace collected rules online |
Reuse material already fully read in the same context and unchanged; when the task changes, supplement only the relevant part. Each package is self-contained and does not read sibling skills, old versions or personal knowledge bases.
Determine the image first, then choose type techniques
Determine this round's medium, viewing purpose, subject/environment relationship, imaging method, allowed variation and user-locked items from the existing input. Ask about gaps only when they substantively change the result and cannot be reasonably inferred; for a given script, understand character goals and current state from the text actually covered, and do not fill in plot from type words alone.
- Photography, composition, light and color, and material jointly serve the viewing order. Choose fixed or compound camera movement according to action; 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 further handles time, triggers, paths, sound and end states; storyboard requests go to shot design, and only prompt requests compile generative text.
- Local revisions retain 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, with position and received light explainable; supernatural light allowed by world rules has its basis. New objects, real plastic, animation or illustration are all handled according to the target, without forcing wear, fog, wet surfaces or photographic realism.
- Numerical values are used for given constraints, explicit design choices or genuine execution needs; when there is no basis, describe visible relationships and do not fabricate color temperature, shadow proportion or success rates.
Direct delivery and interface
Deliver only the visual solution, copyable prompts, parameters, or evidence-based diagnosis needed for this instance. 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 form, or full self-check to ordinary results. When storyboards and prompts are explicitly requested, deliver them as separate instances of the same design; prefer any existing format.
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 only when the handoff requires it; see the execution contract for specific fields. Do not arbitrarily change existing downstream key names or interfaces the user has already used; 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, motion, and material continuity; after fixing specific content when issues 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 use internal checks as a substitute for final-cut approval.