renku-write-prompts

Renku Write Prompts

Write prompts for the selected producer contract and model workflow. Do not write generic cinematic fluff before identifying the workflow.

Prompt Workflow

1. Confirm the active producer contract and model from renku-pick-workflow or the blueprint/input file.
2. Load the matching model prompt reference if available.
3. Identify the workflow mode: text-to-video, image-to-video, start/end, reference-to-video, multi-shot, image edit/compose, TTS, native audio, or talking head.
4. Write prompts that describe the controllable dimensions the producer actually exposes.
5. Keep recurring anchors stable across segments.
6. Keep spoken text within duration limits; use separate high-fidelity TTS when native dialogue quality is not the main fit.
7. Use renku-author-director when the prompts are generated by a director prompt producer rather than written directly into inputs.

Prompt Quality Rules

• State visible action, camera behavior, temporal progression, and sound when relevant.
• For image-to-video, let the image carry identity/layout; prompt motion and camera evolution.
• For start/end-frame clips, describe the transition from A to B, not two unrelated images.
• For reference workflows, assign each reference a role only if the producer exposes that reference.
• For multi-shot prompts, label shots explicitly and keep each shot to one primary action.
• For visual prompts, avoid text, labels, titles, logos, and watermarks unless explicitly desired.

References

• Read references/seedance-2-0.md for Seedance 2.0 prompting.
• Read references/kling-3.md for Kling 3 prompting.
• Read references/model-prompt-selection.md to choose the right guide.
• Read references/failure-fixes.md when improving weak generations.

Maintenance

Use renku-update-prompt-guides when adding or refreshing model prompt guide references. Do not load source-map or template maintenance docs during normal prompt-writing unless the task is to update the guide library.