@indreamai/openclaw-plugin 0.1.0

package/skills/indream-editor-json/references/keyframes.md

@@ -0,0 +1,102 @@
+# Adding Keyframes
+
+## Mental model
+
+Animated number tracks always use:
+
+```json
+{
+  "value": 120,
+  "keyframes": []
+}
+```
+
+- `value` is the base value the item rests on
+- `keyframes` inject time-based overrides
+
+## Single-keyframe rule of thumb
+
+If the item should end at one stable value but begin from another value, a single keyframe is often enough.
+
+Example:
+
+```json
+{
+  "left": {
+    "value": 120,
+    "keyframes": [
+      { "timeTicks": 0, "value": -220 }
+    ]
+  }
+}
+```
+
+Interpretation:
+
+- at the start of the clip, the item begins off-screen at `-220`
+- it settles to the base `value` of `120`
+
+This is the cleanest way to add one entrance keyframe without redesigning the whole item.
+
+## Common single-keyframe patterns
+
+### One entrance move
+
+```json
+{
+  "top": {
+    "value": 280,
+    "keyframes": [
+      { "timeTicks": 0, "value": 360 }
+    ]
+  }
+}
+```
+
+### One entrance scale pop
+
+```json
+{
+  "scaleX": {
+    "value": 1,
+    "keyframes": [
+      { "timeTicks": 0, "value": 0.7 }
+    ]
+  },
+  "scaleY": {
+    "value": 1,
+    "keyframes": [
+      { "timeTicks": 0, "value": 0.7 }
+    ]
+  }
+}
+```
+
+### One fade-out target
+
+```json
+{
+  "opacity": {
+    "value": 0,
+    "keyframes": [
+      { "timeTicks": 0, "value": 1 }
+    ]
+  }
+}
+```
+
+## When to use two or more keyframes instead
+
+Use more than one keyframe when the item needs:
+
+- a hold before movement starts
+- multiple motion phases
+- a bounce or overshoot
+- a mid-clip change instead of a simple start-to-rest interpolation
+
+## Keyframe authoring rules
+
+- keep `timeTicks` inside the item duration
+- add keyframes to only the properties that need motion
+- prefer one property change at a time when debugging
+- if the motion is just a simple entry or exit, compare whether a clip animation would be cleaner than custom keyframes

package/skills/indream-editor-json/references/material-libraries.md

@@ -0,0 +1,97 @@
+# Material Libraries and Sticker Compatibility
+
+## Hand-drawn vector material library
+
+The safest Open API representation for the hand-drawn vector material library is the `illustration` item.
+
+Use it when the user wants:
+
+- playful SVG-like artwork
+- decorative vector accents
+- product-friendly hand-drawn scenes
+- explainer or infographic support art
+
+Required fields:
+
+- `type: "illustration"`
+- `illustrationName`
+- `color`
+- `keepAspectRatio`
+- `rotation`
+- full base geometry fields
+
+Always choose `illustrationName` from `indream_editor_capabilities`.
+
+## Useful illustration categories
+
+The live illustration library is large.
+Use a small curated subset unless the user explicitly asks for a specific name.
+
+Good examples from the live capability set:
+
+- Greeting and welcome:
+  - `IHello`
+  - `IWelcome`
+  - `IWelcomeAboard`
+- Product and launch:
+  - `IProductDemo`
+  - `IProductExplainer`
+  - `ILaunchDay`
+  - `ILaunchEvent`
+- Charts and analytics:
+  - `ICharts`
+  - `IGrowthChart`
+  - `IDataAnalysis`
+  - `IAnalytics`
+- Content and media:
+  - `IContentCreator`
+  - `IVideoTutorial`
+  - `IOnlineVideo`
+
+## Sticker support in the current Open API
+
+Sticker support exists, but it is not fully symmetrical across the editor runtime and the open API schema.
+
+Current compatibility facts:
+
+- the current open API schema exposes `stickerId` and `stickerVersion` on `image` items
+- the editor runtime also carries sticker metadata on `lottie` items in some internal flows
+- the current open API capabilities payload does not expose a sticker catalog or importable sticker definitions
+
+That means you should not invent sticker identifiers.
+
+## Safe sticker authoring rules
+
+Only add `stickerId` and `stickerVersion` when one of these is true:
+
+- the values come from an existing editor draft
+- the values come from an internal sticker import flow
+- the user explicitly supplied known-good sticker metadata
+
+If none of that is available, use one of these safe fallbacks instead:
+
+- a normal `image` item for a static sticker-like badge
+- a `lottie` item for an animated badge
+- an `illustration` item for a curated vector decoration
+
+## Open API-safe fallback patterns
+
+### Static sticker-like badge
+
+Use an `image` item backed by a transparent PNG asset.
+Do not attach fake sticker metadata.
+
+### Animated sticker-like badge
+
+Use a `lottie` item backed by a real lottie asset.
+Do not attach sticker metadata unless it came from a trusted source.
+
+### Library illustration
+
+Use an `illustration` item when the user wants decorative hand-drawn art and no specific sticker catalog entry is required.
+
+## Practical guidance for the skill
+
+- Prefer `illustration` for reusable hand-drawn vector art.
+- Prefer uploaded image overlays for portable sticker-like decorations.
+- Treat real sticker metadata as compatibility-sensitive and source-dependent.

package/skills/indream-editor-json/references/minimal-editor-state.json

@@ -0,0 +1,36 @@
+{
+  "compositionWidth": 1920,
+  "compositionHeight": 1080,
+  "timebaseTicksPerSecond": 240000,
+  "tracks": [
+    {
+      "id": "track-1",
+      "hidden": false,
+      "muted": false,
+      "items": ["item-solid-1"]
+    }
+  ],
+  "assets": {},
+  "items": {
+    "item-solid-1": {
+      "id": "item-solid-1",
+      "type": "solid",
+      "color": "#111827",
+      "shape": "rectangle",
+      "startTicks": 0,
+      "durationTicks": 240000,
+      "top": { "value": 0, "keyframes": [] },
+      "left": { "value": 0, "keyframes": [] },
+      "width": { "value": 1920, "keyframes": [] },
+      "height": { "value": 1080, "keyframes": [] },
+      "scaleX": { "value": 1, "keyframes": [] },
+      "scaleY": { "value": 1, "keyframes": [] },
+      "opacity": { "value": 1, "keyframes": [] },
+      "isDraggingInTimeline": false,
+      "borderRadius": { "value": 0, "keyframes": [] },
+      "rotation": { "value": 0, "keyframes": [] },
+      "keepAspectRatio": false
+    }
+  },
+  "transitions": {}
+}

package/skills/indream-editor-json/references/motion-effects-and-transitions.md

@@ -0,0 +1,235 @@
+# Motion, Effects, Filters, and Transitions
+
+## Clip animations
+
+Many visual items can use clip-level `animations` with `in` and `out` keys.
+
+Supported animation types:
+
+- `fade`
+- `slide-up`
+- `slide-down`
+- `slide-left`
+- `slide-right`
+- `zoom-in`
+- `zoom-out`
+
+Animation shape:
+
+```json
+{
+  "type": "fade",
+  "durationTicks": 24,
+  "easing": "ease-in-out"
+}
+```
+
+Supported easing values:
+
+- `linear`
+- `ease-in`
+- `ease-out`
+- `ease-in-out`
+
+Use clip animations for:
+
+- scene entrance or exit
+- lower-third fly-ins
+- logo pop-ins
+- image or product zooms
+
+## Keyframed motion
+
+Use animated number tracks when the user needs motion that clip animations cannot express cleanly, such as:
+
+- moving an item across the screen
+- scaling over time
+- opacity ramps
+- subtle rotation
+
+Example:
+
+```json
+{
+  "left": {
+    "value": 120,
+    "keyframes": [
+      { "timeTicks": 0, "value": -160 },
+      { "timeTicks": 24, "value": 120 }
+    ]
+  }
+}
+```
+
+Practical rules:
+
+- Keep keyframe times within the item's duration window.
+- Use a small number of keyframes unless the motion genuinely needs more.
+- Prefer clip animations for simple in or out motion, and keyframes for custom paths or multi-stage motion.
+
+## Caption animations
+
+`text` and `captions` items support `captionAnimations` with `in`, `out`, and `loop`.
+
+Supported animation names:
+
+- `converge`
+- `elastic-pop`
+- `typewriter`
+- `lay-down`
+- `center-type-out`
+- `curtain-close`
+- `jitter`
+- `rainbow`
+- `sweep-shine`
+
+Suggested usage:
+
+- `in` for entry emphasis
+- `loop` for ongoing energy on short social clips
+- `out` for final subtitle departure
+- For `captions` items, use one short `in` animation as the production-safe default, then add `loop` or `out` only after a real export probe.
+
+Avoid long looping animations on dense subtitle tracks unless the user explicitly wants a high-energy style.
+
+## Effects
+
+Effect items are time-ranged overlays.
+
+Supported schema effect types:
+
+- `flash-to-black`
+- `blur`
+- `blurred-opening`
+- `fade-in`
+- `fade-out`
+
+Use effects for:
+
+- opening blur reveals
+- emphasis moments
+- flash punctuation
+- brief visual bridges between scenes
+
+## Filters
+
+Filter items are time-ranged look treatments.
+
+Supported schema filter types:
+
+- `verdant-glow`
+- `cyberpunk-neon`
+- `vaporwave-blue`
+- `sunset-orange`
+- `lemon-cyan`
+- `absolute-red`
+- `sakura-pink`
+- `twilight-dusk`
+
+Use filters for:
+
+- full-scene color treatment
+- short stylized moments
+- look changes that should not affect the whole timeline
+
+`params.blend` is a common example for partial application, but only use additional params that the product actually supports.
+
+## Transitions
+
+Transitions connect two adjacent clips on the same track.
+
+Required fields:
+
+- `id`
+- `trackId`
+- `fromClipId`
+- `toClipId`
+- `type`
+- `durationTicks`
+
+Supported transition types:
+
+- `fade`
+- `slide`
+- `wipe`
+- `flip`
+- `clock-wipe`
+- `iris`
+
+Useful live parameter patterns:
+
+- `slide` with `params.direction`:
+  - `from-left`
+  - `from-right`
+  - `from-top`
+  - `from-bottom`
+- `wipe` with `params.direction`:
+  - `from-left`
+  - `from-top-left`
+  - `from-top`
+  - `from-top-right`
+  - `from-right`
+  - `from-bottom-right`
+  - `from-bottom`
+  - `from-bottom-left`
+- `flip` with `params.direction`:
+  - `from-left`
+  - `from-right`
+  - `from-top`
+  - `from-bottom`
+
+Common optional fields:
+
+- `easing`
+- `params`
+
+Transition rules:
+
+- only use transitions between neighboring clips in one `track.items[]`
+- do not span clips on different tracks
+- do not use transitions as a replacement for effect items
+- do not add transitions when the edit is a hard cut unless the user asked for a transition
+
+## Motion design guidelines
+
+### Conservative commercial style
+
+Use:
+
+- one transition family
+- light fade or slide-in clip animations
+- no more than one persistent filter style
+- limited caption animation
+
+### Flashy social short
+
+Use:
+
+- stronger caption animation
+- punchy transition choices
+- selective filters on highlight moments
+- fast but readable motion on text and stickers
+
+### Tutorial or explainer
+
+Use:
+
+- minimal transitions
+- consistent lower-third motion
+- stable subtitles
+- clear chart or annotation animation
+
+## Live defaults worth reusing
+
+Real capability responses currently expose useful defaults that are safe to mirror:
+
+- `blurred-opening` effect often uses `params.maxBlurPx: 24`
+- `flash-to-black` effect may use:
+  - `brightFrames`
+  - `darkFrames`
+  - `maxOpacity`
+  - `tailDarkFrames`
+- filters commonly expose a `blend` value in `params`
+
+Use these only when they match the user's intent.
+Do not add extra params blindly when a simpler default gets the job done.

package/skills/indream-editor-json/references/recipes.md

@@ -0,0 +1,122 @@
+# Practical Recipes
+
+Use these as planning patterns, not as rigid templates.
+
+## Recipe: sequential slideshow with transitions
+
+Use when the user wants:
+
+- multiple still images
+- one after another
+- gentle scene changes
+
+Recommended structure:
+
+- one visual track with back-to-back image or solid items
+- transitions between each adjacent pair
+- optional text overlay track for titles
+
+Recommended motion:
+
+- subtle `fade` or `zoom-in` clip animation
+- `fade` transition unless the user wants a stronger effect
+
+## Recipe: talking-head short with subtitles
+
+Use when the user wants:
+
+- primary video
+- styled subtitles
+- optional title and CTA overlays
+
+Recommended structure:
+
+- one track for the main `video` item
+- one track for a `captions` item
+- optional overlay track for title card or end card
+- optional `audio` item for background music
+
+Recommended motion:
+
+- minimal clip animation on the main video
+- one readable subtitle style
+- optional `captionAnimations.in` for energy
+
+## Recipe: product promo with layered visuals
+
+Use when the user wants:
+
+- a hero image or video
+- decorative shapes
+- motion callouts
+- logo or feature badges
+
+Recommended structure:
+
+- main media track
+- one overlay track for `solid` and `illustration` items
+- one overlay track for `text` items
+- optional filter or effect items for emphasis windows
+
+Recommended motion:
+
+- slide or zoom clip animations on text and badges
+- keyframed movement for callout entrances
+- transitions only between major scene changes
+
+## Recipe: text-only kinetic promo
+
+Use when the user wants:
+
+- no footage
+- bold text-driven storytelling
+- heavy subtitle-like motion
+
+Recommended structure:
+
+- `solid` background item or `globalBackground`
+- multiple `text` items on one or more tracks
+- optional `illustration` or `chart` items
+
+Recommended motion:
+
+- `captionAnimations` on headline text
+- keyframed position and opacity for custom pacing
+- occasional effect windows for emphasis
+
+## Recipe: clean data slide
+
+Use when the user wants:
+
+- business metrics
+- clean title and body copy
+- consistent visual colors
+
+Recommended structure:
+
+- background `solid` or `globalBackground`
+- one `chart` item
+- one or more `text` items
+- optional `illustration` item
+
+Recommended motion:
+
+- modest clip animation on chart and title
+- avoid flashy caption animation unless the visual tone allows it
+
+## Recipe: template-driven cover
+
+Use when the user wants:
+
+- a known reusable template
+- exact template-driven nodes
+
+Recommended structure:
+
+- one `text-template` item with validated `nodes`
+- optional supporting tracks for extra text or stickers if the product supports them
+
+Important:
+
+- only use this recipe when the template contract is known
+- otherwise fall back to standard `text`, `image`, and `solid` items