@docyrus/animaguru 0.14.0 → 0.15.0
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 +15 -0
- package/dist/animaguru.js +452 -309
- package/package.json +1 -1
- package/skills/animaguru/SKILL.md +4 -0
- package/skills/animaguru-video/SKILL.md +4 -0
package/package.json
CHANGED
|
@@ -87,6 +87,10 @@ For hosting, run `animaguru submit animations/NAME --yes`, or `animaguru submit
|
|
|
87
87
|
|
|
88
88
|
`animaguru motion search DESCRIPTION [--category ID] [--labels a,b] [--code]` finds ready-made PixiJS motion examples (kinetic typography, app UI and more) built on the video film kit; `animaguru motion get ID --write src/scenes` installs one into a film. See the `animaguru-video` skill. Searching is free.
|
|
89
89
|
|
|
90
|
+
## Asset library
|
|
91
|
+
|
|
92
|
+
Pro and Team accounts: `animaguru library search DESCRIPTION [--type sprite|image|video|music|speech|sfx] [--labels a,b]` finds ready-made assets; `animaguru library import ID --project PROJECT_ID` copies one into a project and `animaguru library download ID --output DIR` saves its files. Search it before generating common assets (whooshes, background music, stock clips, characters); importing spends no credits.
|
|
93
|
+
|
|
90
94
|
## On demand
|
|
91
95
|
|
|
92
96
|
Read these only when the task needs them:
|
|
@@ -75,6 +75,10 @@ Keep `src/film.ts` to setup and the scene list, and put each scene in `src/scene
|
|
|
75
75
|
|
|
76
76
|
Before choreographing a scene from scratch, search the AnimaGuru motion library for a finished example to start from: `animaguru motion search DESCRIPTION [--category ID] [--labels mobile,dark]` (natural language and keywords both work; `animaguru motion categories` lists the categories, such as `kinetic-typography` and `application-ui`). Each result describes what it looks like, its labels, techniques and duration. `animaguru motion get ID` prints its timed beats, options and code; `animaguru motion get ID --write src/scenes` (or `animations/NAME/src/scenes` in a workspace, where the kit import is rewritten for `runtime/kit`) writes the scene and its shared modules. Call its entry function from `build()` with `{ at }`, an area (`x, y, width, height`) and your copy, colors and fonts, then adapt the choreography to the brief rather than shipping the sample copy. The MCP tools `search_motion_examples` and `get_motion_example` return the same data. Search needs `animaguru auth login`; it spends no credits.
|
|
77
77
|
|
|
78
|
+
## Asset library
|
|
79
|
+
|
|
80
|
+
Pro and Team accounts can take ready-made music, sound effects, voice-overs, clips, images and sprites from the AnimaGuru asset library instead of generating them: `animaguru library search DESCRIPTION --type music|sfx|speech|video|image|sprite` (natural language and keywords). `animaguru library download ID --output public/assets/` saves a file into the film (sprites save their sheets with `animation.json` frame rectangles and timing); `animaguru library import ID --project PROJECT_ID` adds it to a cloud project instead. Prefer a library whoosh or background track over generating one; it spends no credits.
|
|
81
|
+
|
|
78
82
|
## Voiceover, music and captions
|
|
79
83
|
|
|
80
84
|
1. Generate the lines in one call: a batch file with shared speech defaults and one `{ name, prompt }` per segment, `animaguru assets batch PROJECT_ID --file production/generation/vo-lines.json --dry-run`, then `--yes --download production/audio/vo/`. Generate music with `assets generate … --type music --yes --download production/audio/music/`. See the `animaguru` skill for authorization.
|