@vibeframe/cli 0.95.0 → 0.95.2

package/dist/index.js

@@ -26237,10 +26237,14 @@ _2\u20133 colours max. Declare explicit hex values; never name colours abstractl
 - _anti-pattern 3_`;
   return `# ${name} \u2014 Design
 
-> **Hard-gate.** This file defines the visual identity of every scene.
-> Author it before generating any HTML, backdrop image, or motion.
-> The Hyperframes \`hyperframes\` skill enforces this: scenes that
-> contradict DESIGN.md are rejected.
+> **Hard-gate (BUILD flow only).** This file is the visual contract for
+> the scene-project flow (\`vibe build\`, \`vibe scene ...\`, composition
+> HTML, backdrop image-gen). Author it before authoring scene HTML; the
+> Hyperframes \`hyperframes\` skill enforces it at composition time.
+>
+> **Single-asset requests (\`vibe generate image|video|speech|...\`) do
+> NOT consult this file.** Run the generate command directly with the
+> user's prompt. See AGENTS.md \u2192 "Route by the user's actual request".
 
 ${intro}
 
@@ -26333,12 +26337,35 @@ This project is **bilingual**: it works with both VibeFrame (\`vibe\`) and
 HeyGen Hyperframes (\`hyperframes\`). You can run either CLI inside this
 directory.
 
-## Visual identity hard-gate
+## Route the request first
 
-**Author \`DESIGN.md\` before any scene HTML.** It defines palette,
-typography, motion, and transition rules. Both the agent-driven path and
-the fallback emit reference it; scenes that contradict DESIGN.md are
-rejected by the Hyperframes \`hyperframes\` skill.
+Before opening DESIGN.md, loading the hyperframes skill, or planning
+scenes, decide which flow the user actually wants:
+
+- **ASSET (default for ambiguous prompts).** Single image, single video
+  clip, single TTS line. Even a verb-less paste of a visual brief lands
+  here. Just run \`vibe generate image|video|speech "<paste>" -o assets/<name>\`.
+  Skip DESIGN.md, skip the hyperframes skill.
+- **BUILD.** Multi-scene / storyboard / composed video. Triggered when
+  the user explicitly asks for "a video built from scenes", "a
+  storyboard", "a multi-scene composition", or names \`vibe build\` /
+  \`vibe scene ...\`. Only here does the hard-gate below apply.
+- **REMIX.** Transform a media file already on disk: \`vibe remix\`,
+  \`vibe edit\`, \`vibe audio\`.
+
+If you can't tell, ask: *"single asset or multi-scene project?"* before
+authoring DESIGN.md or invoking a skill.
+
+## Visual identity hard-gate (BUILD flow only)
+
+**Within the BUILD flow,** author \`DESIGN.md\` before any scene HTML.
+It defines palette, typography, motion, and transition rules. Both the
+agent-driven path and the fallback emit reference it; scenes that
+contradict DESIGN.md are rejected by the Hyperframes \`hyperframes\`
+skill.
+
+Single-asset requests (\`vibe generate image|video|speech|...\`) do NOT
+consult this file \u2014 run the generate command directly.
 
 Browse named styles: \`vibe scene list-styles\`. Re-seed from one with
 \`vibe scene init . --visual-style "Swiss Pulse"\` (idempotent).
@@ -63456,7 +63483,7 @@ init_source();
 // package.json
 var package_default = {
   name: "@vibeframe/cli",
-  version: "0.95.0",
+  version: "0.95.2",
   description: "VibeFrame CLI - natural language video editing from the terminal",
   private: false,
   license: "MIT",
@@ -71702,16 +71729,25 @@ vibe walkthrough pipeline      # step-by-step authoring guide (pipeline)
 Routing the user's request correctly is the most important judgement call
 you'll make. Do not force everything into a scene project.
 
-**ASSET \u2014 create one generated asset.**
+**ASSET \u2014 default for any single-asset request OR ambiguous prompt.**
 If the user asks for a single image, single video clip, sound effect, music
-bed, or narration file, use \`vibe generate ...\` directly. Do **not** edit
-\`DESIGN.md\`, \`STORYBOARD.md\`, or run \`vibe scene ...\` unless the user
-explicitly asks to build a storyboard/scene/composed video.
+bed, or narration file \u2014 **OR pastes a visual/audio brief without explicit
+storyboard / scene / multi-scene language** \u2014 treat it as ASSET. Use
+\`vibe generate ...\` directly. Do **not** edit \`DESIGN.md\`,
+\`STORYBOARD.md\`, run \`vibe scene ...\`, or auto-load the hyperframes
+skill until BUILD intent is explicit. The visual-identity hard-gate
+applies to BUILD only.
 
 Examples:
 - "make this image" \u2192 \`vibe generate image "..." -o assets/name.png\`
 - "use this image to make a video" \u2192 \`vibe generate video "..." -i image.png -o renders/name.mp4\`
+- "add a lower-third/title/animated overlay/grain/vignette to this clip" \u2192 prefer \`vibe generate motion "..." --video clip.mp4 --render -o out.mp4\` when the request asks for designed or animated motion graphics.
 - "please add visuals using OpenAI image gen" \u2192 \`vibe generate image "..." -p openai ...\`
+- *(verb-less paste)* "aerial view of a misty mountain peak at sunrise..." \u2192 \`vibe generate image "<paste>" -o assets/mountain-peak.png\`. **Don't** read it as a brief for DESIGN.md.
+
+If genuinely uncertain, ask one short question: *"single asset or
+multi-scene project?"* before authoring DESIGN.md or loading the
+hyperframes skill.
 
 **BUILD \u2014 create new video from text intent.**
 Use \`vibe build\` with a STORYBOARD.md + DESIGN.md. The
@@ -71722,6 +71758,10 @@ bundle, then renders to MP4. Idempotent re-runs reuse cached assets.
 **REMIX \u2014 transform existing video / audio.**
 Use \`vibe remix\`, \`vibe edit\`, or \`vibe audio\`. One-shot,
 batch-oriented operations on a file the user already has on disk.
+\`vibe edit text-overlay\` is the free deterministic path for simple static
+text burn-in. If the user asks for motion design, animated lower-thirds,
+designed titles, grain/vignette as part of a graphic treatment, or says
+"motion graphics", use \`vibe generate motion --video ... --render\` instead.
 
 Decision rule: if the user asks for one asset, it's ASSET. If the user asks
 for a multi-scene/storyboard/composed video, it's BUILD. If the user is
@@ -71747,6 +71787,7 @@ starting from a media file and wants it transformed, it's REMIX.
 | Extract highlights from a long video | \`vibe remix highlights file.mp4 -d 60\` |
 | Long video \u2192 vertical shorts | \`vibe remix auto-shorts file.mp4 -n 3 --add-captions\` |
 | Add animated word-by-word captions | \`vibe remix animated-caption file.mp4 -s karaoke-sweep\` |
+| Add designed motion graphics overlay | \`vibe generate motion "lower-third..." --video file.mp4 --render -o out.mp4\` |
 | Remove silence | \`vibe edit silence-cut in.mp4 -o out.mp4\` |
 | Add static captions | \`vibe edit caption in.mp4 -o out.mp4\` |
 | Translate audio (transcribe \u2192 TTS) | \`vibe audio dub file.mp4 -t ko\` |
@@ -71850,7 +71891,10 @@ overview content moved into AGENTS.md above):
 Claude-specific routing note: follow the ASSET / BUILD / REMIX decision
 rules in \`AGENTS.md\`. In particular, a request for one generated image or
 one generated video clip is an ASSET request: use \`vibe generate image\` or
-\`vibe generate video\` directly. Do not invoke \`/vibe-scene\`, edit
+\`vibe generate video\` directly. A request for designed/animated overlays
+on an existing clip is usually \`vibe generate motion --video ... --render\`,
+not \`vibe edit text-overlay\`, unless the user explicitly asks for a simple
+static text burn-in. Do not invoke \`/vibe-scene\`, edit
 \`DESIGN.md\`, or edit \`STORYBOARD.md\` unless the user explicitly asks for a
 scene, storyboard, or composed video.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibeframe/cli",
-  "version": "0.95.0",
+  "version": "0.95.2",
   "description": "VibeFrame CLI - natural language video editing from the terminal",
   "private": false,
   "license": "MIT",
@@ -183,8 +183,8 @@
     "tsx": "^4.21.0",
     "typescript": "^5.3.3",
     "vitest": "^1.2.2",
-    "@vibeframe/ai-providers": "0.95.0",
-    "@vibeframe/core": "0.95.0"
+    "@vibeframe/core": "0.95.2",
+    "@vibeframe/ai-providers": "0.95.2"
   },
   "engines": {
     "node": ">=20"