reframe-video 0.6.23 → 0.6.24

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "reframe",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "Create and iterate motion-graphics videos as addressable data: deterministic mp4 renders, human edits that survive AI regeneration, label-anchored audio, data-driven batch rendering.",
   "author": {
     "name": "Kiyeon Jeon",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "reframe-video",
-  "version": "0.6.23",
+  "version": "0.6.24",
   "description": "Declarative motion graphics that AI can write and humans can tweak — human edits survive AI regeneration. Deterministic mp4 renders from a plain-data scene format.",
   "keywords": [
     "motion-graphics",

package/skills/reframe/SKILL.md

@@ -11,9 +11,12 @@ runtime needs ffmpeg on PATH and a one-time `npx playwright install chromium`
 
 ## Creating a scene
 
-1. **Read the guide first** — it is the complete, current syntax (~1,700
-   tokens) and one read is enough to write valid scenes:
-   `npx -y reframe-video guide`
+1. **Read the guide first** — `npx -y reframe-video guide` is the complete,
+   current syntax. It's sectioned and sizable: read the core (Nodes, States,
+   Timeline) closely, and **skim the specialized sections by heading**
+   (perspective, track mattes, group effects, video, montage, character rig,
+   device frames, cursor, audio) — read one in full only when your scene uses
+   it. You don't need to re-read it for follow-up edits; it's already in context.
 2. Write a single self-contained `<name>.ts` in the user's directory
    (`npx -y reframe-video new <name>` scaffolds a documented starter).
    Scenes must be pure functions of time: no `Math.random()`/`Date` — use