MuseVideoPromptChecklist

v1.0.0·Updated 2026-08-07

A practical shot, motion, continuity, and audio planning checklist for Content Warning video concepts.

About this mod Author’s original text

Muse Video Prompt Checklist

Content Warning clips often combine fast subject movement, a moving camera, abrupt lighting changes, and noisy audio. This planning kit helps creators turn a rough clip concept into a constrained shot brief before generating supporting video material or preparing an edit.

Separate subject motion from camera motion

Describe the main subject first: its starting position, one primary action, direction of travel, and ending state. Then describe the camera independently. State whether the camera is fixed, handheld, following, panning, tilting, or moving on a defined path.

Avoid asking for several major actions in one short interval. If a concept needs a reveal, a chase, and a reaction, split it into separate shots. This makes continuity easier to review and gives each prompt a clear outcome.

Preserve recognizable anchors

List the details that must remain stable:

  • Character identity, clothing, and carried props.
  • Environment layout and important landmarks.
  • Time of day, practical light sources, and dominant palette.
  • Opening and ending frame composition.
  • Any object that must remain readable during motion.

The included shot-brief-template.json provides structured fields for these anchors, along with expected failure modes and a post-generation review.

Plan audio deliberately

Treat dialogue, ambience, effects, music, and silence as separate decisions. Give important dialogue enough space, and avoid stacking several loud effects at the same moment. When audio is not required, request silence explicitly instead of leaving the result ambiguous.

For teams exploring prompt-led subject, camera, visual, and audio direction in one browser workflow, Muse Video is an independent option. Its underlying model is presented as preview-stage, so this kit does not assume confirmed public access, pricing, limits, or performance.

Pre-publish review

  • Confirm that the main action is physically coherent.
  • Check that camera motion supports rather than obscures the action.
  • Compare the opening and ending frames for continuity.
  • Inspect faces, hands, text, props, reflections, and fast motion.
  • Verify that audio timing agrees with visible events.
  • Replace any generated mockup that could be mistaken for actual gameplay evidence.

Generated material still requires human review for accuracy, rights, accessibility, brand fit, and final publishing quality.

Install & use Install: BepInEx plugin

  1. The archive from playbuff is the mod itself — usually a BepInEx plugin (a .dll or a plugin folder once unzipped).
  2. Recommended: use a community mod manager (such as r2modman) — pick this game, import the mod, and the manager sets up BepInEx and its dependencies for you.
  3. Manual route: install the BepInEx loader in the game folder, then drop the unzipped .dll or plugin folder into BepInEx/plugins/.
  4. Launch the game — the BepInEx console logs every plugin it loads; seeing this mod in the log means it is installed.

Mods with listed dependencies need those installed too, or they will not load. Options are usually changed in-game or in the plugin's config file.

File & checksum

Filename
MuseVideoPromptChecklist-1.0.0.zip
File size
9.6 KiB
SHA-256
83c3c93dfc5e3e7980748e469e88a4fab142dc24471facf572785c067527ee09
Stored at
2026-10-10 06:18