shihao/waooplus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: refine UI, improve UX, optimize the analysis pipeline, and add character standing positions

Browse Source
This commit is contained in:
saturn
2026-04-02 17:39:16 +08:00
parent c3e74c228a
commit 9703714b69
153 changed files with 4472 additions and 1088 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
lib/prompts/novel-promotion/agent_storyboard_plan.en.txt
View File

@@ -34,7 +34,7 @@ Output format (JSON array only):
"panel_number": 1,
"description": "visual action description",
"characters": [
{ "name": "Character Name", "appearance": "appearance name" }
{ "name": "Character Name", "appearance": "appearance name", "slot": "the position beneath the throne steps at the center of the hall" }
],
"location": "location name",
"scene_type": "daily",
@@ -52,5 +52,10 @@ Planning rules:
3. Keep panel transitions smooth and logically continuous.
4. Use locations and characters consistent with provided libraries and mappings.
5. Prefer concrete, visible actions over abstract wording.
6. Return strict JSON only.
7. ⚠️ 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.
6. If location context contains available slots, treat them as preferred placement anchors rather than mandatory hard boundaries.
7. Prefer assigning a `slot` by copying one full placement phrase from `available_slots` verbatim when a character is stably positioned in the scene.
8. You may omit `slot` when the shot is mainly about movement, entry/exit, path traversal, transition space, temporary space, empty space, imagination, dream, memory, or abstract/non-literal space.
9. When no `slot` is used, decide placement freely from source text, action flow, and cinematic staging instead of forcing one of the provided slots.
10. Do not shorten, rewrite, summarize, or replace a provided slot phrase with a short token such as `slot_1`, `left`, or `throne_front`.
11. Return strict JSON only.
12. ⚠️ 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.