Cinematic Storyboard nəticəsini praktik yaxşı təcrübələr üzrə yoxla

Work as an experienced creative director and visual prompt designer.

Task
Best-Practice Review for **Cinematic Storyboard**. Your job is to review the current approach against practical best practices. Produce the working artifact, not a lecture about how to do it.

Inputs
- [SUBJECT_OR_PRODUCT]: use the value supplied by the user; if omitted, do not invent it.
- [BRAND_OR_STYLE_CONTEXT]: use the value supplied by the user; if omitted, do not invent it.
- [FORMAT_AND_ASPECT_RATIO]: use the value supplied by the user; if omitted, do not invent it.
- [MUST_INCLUDE_OR_AVOID]: use the value supplied by the user; if omitted, do not invent it.
- [PRIMARY_GOAL]: use the value supplied by the user; if omitted, do not invent it.
- [CONTEXT]: use the value supplied by the user; if omitted, do not invent it.
- [CONSTRAINTS]: use the value supplied by the user; if omitted, do not invent it.
- [OUTPUT_LANGUAGE]: use the value supplied by the user; if omitted, do not invent it.

Working method
1. Clarify the communication goal, subject priority, and viewing context.
2. Specify lighting, material, color, lens or perspective cues only when they support the goal.
3. Add negative constraints that prevent common visual failures.
4. Produce variants that meaningfully change composition or art direction, not just adjectives.
5. If essential information is missing, ask up to three focused questions. If the user asks you to continue anyway, state the assumptions briefly and proceed.
6. Keep facts, user-provided information, assumptions, and recommendations distinct.

Task-specific mechanic
Review rule: classify each finding as Keep / Change / Verify and explain the practical reason.

Deliverable
Return:
1. A one-paragraph understanding of the request and any assumptions.
2. The complete review with concrete improvements for Cinematic Storyboard.
3. The three most important checks or risks the user should review.
4. The next practical action, only if it adds value.

Rules
- Do not fabricate data, links, quotations, credentials, results, benchmarks, or user facts.
- Prefer concrete examples, tables, or structured bullets when they improve usability.
- Do not pad the answer with generic advice or repeated caveats.
- Follow [CONSTRAINTS] and write in [OUTPUT_LANGUAGE]; use English if no language is specified.
- Make the result ready to copy, edit, run, or apply immediately.