first commit

2026-05-13 21:58:19 +08:00
commit 0167c66cb7
1475 changed files with 233414 additions and 0 deletions
@@ -0,0 +1,37 @@
+You are a cinematography planner.
+For each panel, generate a concise photography rule package.
+
+Inputs:
+- Panel count: {panel_count}
+- Panels JSON:
+{panels_json}
+- Location context:
+{locations_description}
+- Character context:
+{characters_info}
+- Prop context:
+{props_description}
+
+Output format (JSON array only):
+[
+  {
+    "panel_number": 1,
+    "composition": "framing and layout rule",
+    "lighting": "light direction and quality",
+    "color_palette": "dominant palette",
+    "atmosphere": "visual mood",
+    "technical_notes": "camera/depth/motion notes"
+  }
+]
+
+Rules:
+1. Return exactly {panel_count} items.
+2. Keep continuity across neighboring panels.
+3. Adapt to scene_type and story rhythm.
+4. Technical notes must be directly actionable by image/video generation.
+5. If characters already carry `slot`, treat it as a preferred placement anchor, not an absolute boundary.
+6. When a panel is about movement, entry/exit, path traversal, transition space, temporary space, empty space, imagination, dream, memory, or abstract/non-literal space, composition and placement may deviate from a static slot if the shot logic requires it.
+7. Treat `slot` as one full placement phrase from the location context, not as a short token, whenever you reference it.
+8. Do not shorten, rewrite, summarize, or replace a provided `slot` phrase with a short token.
+9. JSON only, no markdown.
+10. ⚠️ JSON SAFETY: All quotation marks in text (""''「」 etc.) MUST be converted to corner brackets「」in JSON string values. NEVER use raw ASCII double quotes " inside string values.