greenlight-motion 0.2.2 → 0.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -9
- package/dist/greenlight-motion.js +291 -291
- package/dist/greenlight-motion.mjs +11899 -11881
- package/package.json +1 -1
- package/skill/SKILL.md +10 -10
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "greenlight-motion",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.3",
|
|
4
4
|
"description": "GreenLight Motion Engine: AI agents make motion-design videos (3D, camera, effects, transitions, text animation, particles, motion blur) with the GreenLight Dash Video Editor's own engine, in the user's browser.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"video",
|
package/skill/SKILL.md
CHANGED
|
@@ -18,7 +18,7 @@ You never write UI or animation code. If something is not in the format, it is n
|
|
|
18
18
|
## Setup (once per machine)
|
|
19
19
|
|
|
20
20
|
```
|
|
21
|
-
npx greenlight-motion@0.2.
|
|
21
|
+
npx greenlight-motion@0.2.3 doctor
|
|
22
22
|
```
|
|
23
23
|
|
|
24
24
|
It checks Node 18+, Chrome or Edge, WebGPU and H.264 encoding, and prints a fix for anything missing. Do not install
|
|
@@ -39,7 +39,7 @@ animation presets (the same converter the GreenLight Motion connector uses in Cl
|
|
|
39
39
|
keyframes rarely look as good. The format, the design rules and the catalogues: `skill/references/scene-script.md`.
|
|
40
40
|
|
|
41
41
|
```
|
|
42
|
-
npx greenlight-motion@0.2.
|
|
42
|
+
npx greenlight-motion@0.2.3 script <folder> --from scenes.json # or write <folder>/script.json, then: script <folder>
|
|
43
43
|
```
|
|
44
44
|
|
|
45
45
|
Then `check` and `stills` (below), fix the SCRIPT and run `script` again — it rewrites `project.json`. A scene's
|
|
@@ -82,14 +82,14 @@ What the engine does there, so you don't learn it from a broken frame:
|
|
|
82
82
|
|
|
83
83
|
## Workflow
|
|
84
84
|
|
|
85
|
-
1. `npx greenlight-motion@0.2.
|
|
85
|
+
1. `npx greenlight-motion@0.2.3 init <folder>` — starts from a working example (title, subtitle, accent line, four
|
|
86
86
|
options). `--from file.json` starts from a project you have (for example one exported from GreenLight Dash).
|
|
87
87
|
2. Edit `<folder>/project.json` — for changes to an EXISTING project prefer `apply` (below): it checks every edit and
|
|
88
88
|
applies all or nothing. Put pictures, video, sound and fonts in `<folder>/assets/` and refer to them as
|
|
89
89
|
`"asset:<file>"` (e.g. `"url": "asset:product.png"`).
|
|
90
|
-
3. `npx greenlight-motion@0.2.
|
|
90
|
+
3. `npx greenlight-motion@0.2.3 check <folder>` — fix everything it lists (missing files, template mistakes, blank
|
|
91
91
|
frames, page errors). `--json` for machine output.
|
|
92
|
-
4. `npx greenlight-motion@0.2.
|
|
92
|
+
4. `npx greenlight-motion@0.2.3 stills <folder>` — renders frames and **a labelled contact sheet**. Open and look at
|
|
93
93
|
it before you go on: layout, readability, timing. Fix and repeat. `--at 0.5,1.2,3` for exact times.
|
|
94
94
|
5. Hand it over: tell the user to open `<folder>/index.html` (Chrome or Edge), or `pack` it into one file, or
|
|
95
95
|
`render` the MP4 yourself (`--fps 60 --motion-blur` for fast motion).
|
|
@@ -154,7 +154,7 @@ editor's own normalizer), so write only what you mean.
|
|
|
154
154
|
Full references (generated from the editor's own docs; ignore the `/api/` routes they mention):
|
|
155
155
|
`skill/references/` — video-design, scene-script, video-projects, video-text, video-text-kinetic, video-text-presets, video-shapes, video-keyframes,
|
|
156
156
|
video-camera, video-3d, video-effects, video-transitions, video-particles, video-paths, video-backgrounds, video-grid.
|
|
157
|
-
Machine-readable lists: `npx greenlight-motion@0.2.
|
|
157
|
+
Machine-readable lists: `npx greenlight-motion@0.2.3 schema effects | transitions | easings | paths | expressions`.
|
|
158
158
|
|
|
159
159
|
## Template
|
|
160
160
|
|
|
@@ -201,7 +201,7 @@ an absolute moment; `align` `sync` (default) / `start` / `end`; `offset` seconds
|
|
|
201
201
|
|
|
202
202
|
The library is 77 hand-picked sounds in categories (whooshes and swooshes, transitions, clicks, pop-ups and
|
|
203
203
|
notifications, data blips, typing and writing, foley, bubbles, impacts and bass drops, camera, gears, voice clips).
|
|
204
|
-
`npx greenlight-motion@0.2.
|
|
204
|
+
`npx greenlight-motion@0.2.3 schema sounds` lists every one with its `category`, `use` (what it is for), `duration`
|
|
205
205
|
and `sync`. Pick by `category` and `use`, then by name.
|
|
206
206
|
|
|
207
207
|
- **Where the files come from:** the GreenLight sound CDN. `build` downloads each sound a cue uses into
|
|
@@ -217,7 +217,7 @@ The page has **Notes**: the user marks what should change right on the frame (a
|
|
|
217
217
|
and writes a note for each mark. Every note carries the moment (seconds and frame), the mark in composition pixels
|
|
218
218
|
and the layers under it (item ids in project.json), so you change exactly that and nothing else.
|
|
219
219
|
|
|
220
|
-
- **They review on this computer:** run `npx greenlight-motion@0.2.
|
|
220
|
+
- **They review on this computer:** run `npx greenlight-motion@0.2.3 review <folder>` and give them the URL it prints
|
|
221
221
|
(it keeps running; `--open` opens their browser, only when they ask). Their notes land in `<folder>/review/`: read
|
|
222
222
|
`review/NOTES.md`, look at the `at-<t>s.png` pictures (the marks are numbered), make the changes (`apply`), `build`
|
|
223
223
|
again and tell them to reload the page.
|
|
@@ -246,11 +246,11 @@ that fails (`plugin`); look at `stills` for the look. A package that carries its
|
|
|
246
246
|
|
|
247
247
|
The same project opens in GreenLight Dash (the desktop editor this engine comes from) for full editing: the page's
|
|
248
248
|
edit note offers **Open in GreenLight Dash** (it imports the folder as a new project on the open board; a page with
|
|
249
|
-
changes saves a `.glvideo`). `npx greenlight-motion@0.2.
|
|
249
|
+
changes saves a `.glvideo`). `npx greenlight-motion@0.2.3 pack <folder> --glvideo` writes that file yourself: ONE
|
|
250
250
|
`.glvideo` (the project + its files) that opens in GreenLight Dash on a double-click, or dropped on its board. Hand it
|
|
251
251
|
over when the user wants to keep editing in the app. A
|
|
252
252
|
GreenLight Dash project comes the other way through the app's **Export for agents** — a ready folder like the one
|
|
253
|
-
`init` makes, with the options the author ticked. `npx greenlight-motion@0.2.
|
|
253
|
+
`init` makes, with the options the author ticked. `npx greenlight-motion@0.2.3 init <folder> --from <its project.json>`
|
|
254
254
|
starts from one too. Never tell the user they must install it: the page plays, changes options and renders on its own.
|
|
255
255
|
|
|
256
256
|
## Files
|