Decide from the current character, action, relationship, or spatial information how the type helps expression. Preserve the existing camera, color, space, action, material, and sound capabilities; use color charts and scene examples as needed without overriding the user's story, assets, imaging method, or locked photography.
Use according to the task
| Current task | Read and execute |
|---|---|
| Ask only 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 |
| Fix only one problem in an established image | First read the current finished work and locked items; add only the material that affects this problem, review the modified area and necessary connections, and do not reopen overall candidates |
| Type adaptation for storyboards/video, action/continuity/sound, or structured handoff | Read Execution contract the 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 examples, and 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 already-recorded rules online |
Reuse material that has been fully read in the same context and has not changed; when the task changes, add only the relevant parts. Each package is self-contained and does not read sibling skills, older versions, or personal knowledge bases.
Determine the image first, then choose the type's techniques
Determine this round's medium, viewing purpose, subject/environment relationship, imaging method, allowed changes, and user-locked items from the existing input. Ask only when a gap substantially changes the result and cannot be reasonably derived; for a given script, understand character goals and current state from the actual covered body text, and do not add plot based solely on a type word.
- Photography, composition, light and color, and material jointly serve the viewing order. Choose fixed or compound camera movement according to the action, and do not mechanically replace words such as "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 revisions preserve 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 received light can be explained; 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 proportions, or success rates.
Direct delivery and interface
Deliver only the visual solution, copyable prompts, parameters, or evidence-based diagnosis needed for this task. Use the natural names of characters, 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, or full self-check to ordinary results. When storyboards and prompts are explicitly requested, deliver both as the same design, and prioritize 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 task.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 already uses; 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; if an issue is found, fix the specific content and then 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 a finished render passing review.