@starreel/mcp 0.1.20 → 0.1.21

package/SKILL.md

@@ -49,6 +49,26 @@ big-ticket image/video stages (portraits, storyboards, frames, videos,
 scene-images) carry a `quote_*`; the other metered steps have no quote and bill
 by usage — 402 mid-run if the balance can't cover them (never overdraft).
 
+## Execution tiers — when to just do it vs. when to ask
+
+Don't ask the user at every step. Sort work into three tiers:
+
+1. **Project settings — free; do them first; don't ask.** `project_type`,
+   `setting_brief` (worldview / ERA LOCK), `ethnicity`, aspect & resolution, and
+   the consistency anchors (`cinematography_prompt`, `art_bible`, `visual_lock`,
+   `video_style_prompt`) are all free and the foundation that steers every later
+   generation. Set them up front via `create_drama` / `update_project_settings`
+   — don't build an empty shell, or all downstream generation drifts.
+2. **Pipeline backbone — metered; in order; quote-then-confirm.** portraits →
+   frames → videos → TTS → compose. Spending stages follow the normal
+   quote → show the user → confirm flow (discipline 2).
+3. **Optional boosts — metered; proactively offer them.** world concept,
+   art-bible generation, scene images, scene groups, lipsync, posters/covers,
+   SFX, BGM, subtitle translation. These lift consistency/quality but aren't
+   required to finish an episode. **Proactively tell the user they're available
+   and show a quote, then run on their OK** — neither silently skip them nor
+   auto-charge.
+
 ## The ten disciplines (hard rules)
 
 These are not suggestions. Violating them wastes the user's money or produces

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@starreel/mcp",
-  "version": "0.1.20",
+  "version": "0.1.21",
   "mcpName": "ai.starreel/starreel",
   "description": "StarReel MCP server — drive the AI short-drama production pipeline (script → storyboards → frames → video → final cut) from Claude, Cursor, or any MCP client",
   "license": "MIT",