@docyrus/animaguru 0.22.0 → 0.23.0

package/NOTICE.md

@@ -1473,7 +1473,7 @@ SOFTWARE.
 
 Video style sources and notices
 
-The executable studies and preview art are original AnimaGuru procedural 2D/2.5D work. Material/motion guidance was adapted from the pinned repositories below. No external creator video, sample music or demo font is bundled. Third-party demo assets retain their own licenses.
+The executable studies and preview art are original AnimaGuru procedural 2D/2.5D work. Material/motion guidance was adapted from the pinned repositories below. The Machine Anatomy geometry kit (src/kit/anatomy/iso-kit.ts) is a verbatim copy from anatomy; its MIT notice is also in src/kit/anatomy/LICENSE. No external creator video, sample music or demo font is bundled. Third-party demo assets retain their own licenses.
 
 lemo-opuscar
 MIT License
@@ -1527,6 +1527,30 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
 
+anatomy
+MIT License
+
+Copyright (c) 2026 Ryan
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
 ## Art Motion references
 
 English adaptations of Huashu Art Motion (https://github.com/alchaincyf/huashu-art-motion). Source revision and coverage are in skills/animaguru-art-motion/references/coverage.json.

package/README.md

@@ -41,9 +41,11 @@ CLI versions before 0.16.2 need one manual update to gain enforcement. Publish t
 
 ## Create an animation video project
 
+CLI 0.23.0 adds eight evidence styles, in which real data, imagery or scans carry the film: Satellite Briefing, Engineering Briefing Board, LiDAR Survey, White Model Projection, Data Physicalization, Exploded Teardown, Microscope Story and Archive Light Table. Their skills ask for the user's own data first, list licence-clean sources, keep `production/FACTS.md` and `production/CREDITS.md`, and never let a generated image stand in for evidence. Each has a runnable study (`npm run example -- satellite-briefing`).
+
 CLI 0.16.2 also installs `animaguru-art-motion` for Codex and Claude Code: one skill with 36 English art-treatment references and nine explainer motion grammars, plus AnimaGuru generation, timing, camera and review guidance. Request it explicitly for a custom film treatment; its references are separate from the gallery presets. Source coverage and the upstream MIT notice are included in the skill.
 
-CLI 0.5.2 includes a complete local PixiJS video workspace with 31 visual styles:
+CLI 0.5.2 includes a complete local PixiJS video workspace, now with 40 visual styles:
 
 ```sh
 animaguru templates
@@ -59,13 +61,15 @@ Open the generated folder in **Codex or Claude Code**, then describe the video y
 - Agent instructions that first ask **Explainer, Advertisement or General Video**, then offer the available visual styles and [the preview gallery](https://animaguru.com/animation-styles), then gather a short creative brief. Each choice is saved before continuing.
 - `film.config.json`, editable TypeScript scenes, localized copy, local asset/production folders, portable HTML5 ZIP export for iframe embedding, and `npm run export:mp4` with exact frame capture and output verification.
 
-New projects leave category and template unset in `animaguru.project.json`. `animaguru.templates.json` lists categories, styles and their installed skills. The 31 visual styles cover cutout, type, vector, technical, character, print, paper, material and cinematic treatments. Every style skill ships with the project, including its relevant visual interview and review criteria. Categories describe purpose and templates describe appearance and motion. The brief establishes audience, tone, message, story, duration and any CTA.
+New projects leave category and template unset in `animaguru.project.json`. `animaguru.templates.json` lists categories, styles and their installed skills. The 40 visual styles cover cutout, type, vector, technical, evidence, character, print, paper, material and cinematic treatments. Every style skill ships with the project, including its relevant visual interview and review criteria. Categories describe purpose and templates describe appearance and motion. The brief establishes audience, tone, message, story, duration and any CTA.
+
+CLI 0.23.0 also adds **Machine Anatomy** (`machine-anatomy`): an idea explained as a working isometric machine of many small shaded parts in a framed figure card with a live readout. Adapted from the MIT-licensed [Anatomy](https://github.com/wheresryan22/anatomy) skill, it bundles that skill's geometry kit in `src/kit/anatomy/` with a PixiJS adapter, and `npm run example -- machine-anatomy` installs its original study.
 
 Scaffolding requires no AnimaGuru sign-in and spends no generation credits; dependency installation requires npm access. `npm run dev` previews the project, and `npm run build` checks and bundles it. To export, run `npm run export:mp4`, open its local URL and wait for the verified MP4, or use HTML5 export for embedding. The starter demo is silent; the agent creates narration and music when in scope.
 
 The official PixiJS skills are vendored with their MIT license and a hashed provenance manifest. Skills and template files ship in both the npm package and macOS installer; `create` does not fetch agent instructions from a remote repository at runtime.
 
-CLI 0.16.1 also installs **AnimaGuru Cutcraft** in both agent skill folders. Ask your agent to use `$animaguru-cutcraft` for tactile paper-collage explainers with exact editorial lettering, one narrator and purposeful cutout motion. Its generation adapter checks the server's enabled models, tracks asynchronous jobs and supports controlled animation of generated transparent artwork when precise placement is needed or video providers are unavailable. Cutcraft is an additional skill; the gallery retains its 31 visual styles.
+CLI 0.16.1 also installs **AnimaGuru Cutcraft** in both agent skill folders. Ask your agent to use `$animaguru-cutcraft` for tactile paper-collage explainers with exact editorial lettering, one narrator and purposeful cutout motion. Its generation adapter checks the server's enabled models, tracks asynchronous jobs and supports controlled animation of generated transparent artwork when precise placement is needed or video providers are unavailable. Cutcraft is an additional skill, not a gallery style.
 
 ## Install the project skill
 

package/dist/animaguru.js

@@ -19761,7 +19761,7 @@ var require_ignore2 = __commonJS({
 // cli/package.json
 var package_default = {
   name: "@docyrus/animaguru",
-  version: "0.22.0",
+  version: "0.23.0",
   description: "Agent-friendly AnimaGuru CLI built with CrustJS",
   type: "module",
   bin: {
@@ -45644,6 +45644,23 @@ var animation_styles_default = {
       previewCaption: "A drafting point traces an AnimaGuru-generated cyanotype line by line, then dimensions, callouts and a title block are drawn in.",
       example: true
     },
+    "machine-anatomy": {
+      name: "Machine Anatomy",
+      description: "Ideas built as working isometric machines: dozens of small shaded parts in a framed figure, with a live readout driven by the mechanism.",
+      materials: [
+        "Four-tone isometric solids",
+        "Small, precise parts",
+        "Figure card and live readout"
+      ],
+      motion: [
+        "Mechanism-driven movement",
+        "Eased travel and springs",
+        "Exploded assemblies"
+      ],
+      family: "technical",
+      previewCaption: "One dispensing head on a gantry fills a sixteen-well tray in a serpentine pass while the readout counts wells and milliliters. Drawn in code with the bundled Anatomy kit.",
+      example: true
+    },
     "holographic-scan": {
       name: "Holographic Scan",
       description: "Luminous projected geometry, traveling scans and accurate part callouts with restrained depth and local explosions.",
@@ -45864,6 +45881,142 @@ var animation_styles_default = {
       family: "graphic",
       previewCaption: "Seeded light particles stream along braided ribbons, flaring as timed pulses pass. A seamless loop rendered in code.",
       example: true
+    },
+    "satellite-briefing": {
+      name: "Satellite Briefing",
+      description: "Satellite imagery graded to an analyst's grey, with thin measured hairlines, dated passes and one reading per screen in one continuous zoom.",
+      materials: [
+        "Georeferenced imagery plates",
+        "Analyst grey grade",
+        "Hairline measurements"
+      ],
+      motion: [
+        "Orbit-to-ground dive",
+        "Dated scan passes",
+        "Range lines that count up"
+      ],
+      previewCaption: "From orbit down to a drying lake: four satellite passes print their shorelines and a range line measures the retreat. Procedural terrain drawn in code, not a real place.",
+      family: "evidence",
+      example: true
+    },
+    "briefing-board": {
+      name: "Engineering Briefing Board",
+      description: "A filmed whiteboard wall where printed cards land with weight and marker ink in fixed colours measures every option against one limit.",
+      materials: [
+        "Enamel board with ghosts",
+        "Three-colour marker ink",
+        "Printed cards & magnets"
+      ],
+      motion: [
+        "Riding dimension lines",
+        "Weighted landings",
+        "Whole-wall reveal"
+      ],
+      previewCaption: "Three drones are measured against one reserve line, a stamp picks the winner and the camera pulls back to the whole wall. Drawn in code with illustrative values.",
+      family: "evidence",
+      example: true
+    },
+    "lidar-survey": {
+      name: "LiDAR Survey",
+      description: "Measured point clouds flown through in the dark, peeled by a cutting plane and condensed into a raking-lit surface with traced features.",
+      materials: [
+        "Point clouds coloured by height",
+        "Raking-lit relief",
+        "Amber traced features"
+      ],
+      motion: [
+        "Scan fronts",
+        "Canopy peel",
+        "Points condensing to ground"
+      ],
+      previewCaption: "A scan front paints a forest in points, a cutting plane peels the canopy and the ground condenses to reveal old field walls. A procedural cloud drawn in code, not a real survey.",
+      family: "evidence",
+      example: true
+    },
+    "white-model-projection": {
+      name: "White Model Projection",
+      description: "A white massing model in a dark room, where projected light paints data onto the buildings one layer at a time.",
+      materials: [
+        "Matte white massing",
+        "Projected data light",
+        "Pins & single readouts"
+      ],
+      motion: [
+        "Lights out, lamp on",
+        "Decade-by-decade switch-ons",
+        "A rising level of light"
+      ],
+      previewCaption: "The house lights cut, each decade lights the buildings it left, a level of light climbs every facade and the tallest tower is picked out. Rendered in code; an illustrative district.",
+      family: "evidence",
+      example: true
+    },
+    "data-physicalization": {
+      name: "Data Physicalization",
+      description: "Statistics built as countable objects on a crafted base, lit like a studio product shot and read at the edge of one unit.",
+      materials: [
+        "Countable unit plates",
+        "Metal, acrylic & walnut",
+        "Pinned paper readings"
+      ],
+      motion: [
+        "Pieces placed with weight",
+        "Tracked growth",
+        "Pull-back to the installation"
+      ],
+      previewCaption: "Ten years of two series become aluminium and acrylic plates on a walnut slab; the stacks cross in 2020 and the camera pulls back to the whole installation. Rendered in code with illustrative values.",
+      family: "evidence",
+      example: true
+    },
+    "exploded-teardown": {
+      name: "Exploded Teardown",
+      description: "A product taken apart on one axis under studio light, every part named with the numbers in its own files, then closed and dimensioned.",
+      materials: [
+        "Studio-lit product parts",
+        "Painted circuit boards",
+        "Leader labels & dimensions"
+      ],
+      motion: [
+        "Layer-by-layer separation",
+        "Lights on inside",
+        "Closing and measuring"
+      ],
+      previewCaption: "An original pad controller lifts apart in one orbit, its LEDs light the diffuser, labels land in a column and it closes to be dimensioned. Rendered in code from its own model.",
+      family: "evidence",
+      example: true
+    },
+    "microscope-story": {
+      name: "Microscope Story",
+      description: "One continuous dive from a slide on the bench to a single cell, with focus breaths, true scale bars and readings counted from the image.",
+      materials: [
+        "Stained specimen plates",
+        "Frosted instrument panels",
+        "Measured rings & counts"
+      ],
+      motion: [
+        "Log-zoom dive",
+        "Focus breaths & sweeps",
+        "Counting the colour"
+      ],
+      previewCaption: "A slide on the bench dives to 10\xD7, the blue inside one circle is counted pixel by pixel, then the camera goes on to a single nucleus. A procedural specimen drawn in code, not a real slide.",
+      family: "evidence",
+      example: true
+    },
+    "archive-light-table": {
+      name: "Archive Light Table",
+      description: "Archive photographs and documents on a backlit table, where a loupe turns a negative positive and catalogue records sit beside the objects.",
+      materials: [
+        "Backlit archive objects",
+        "Loupe optics",
+        "Catalogue tags & index"
+      ],
+      motion: [
+        "Table glides",
+        "Loupe landings & develop fronts",
+        "Into the photograph"
+      ],
+      previewCaption: "Three NASA Ames photographs of one airfield on a light table; under the loupe a 1933 negative turns positive and opens into the picture. Public-domain NASA scans; the negatives are simulated.",
+      family: "evidence",
+      example: true
     }
   },
   browseStyles: "Browse animation styles",
@@ -45877,7 +46030,8 @@ var animation_styles_default = {
     paper: "Paper & cutout",
     character: "Character & pixel",
     material: "Materials & depth",
-    cinematic: "Cinema & media"
+    cinematic: "Cinema & media",
+    evidence: "Evidence & data"
   },
   searchLabel: "Search visual styles",
   searchPlaceholder: "Try paper, product, typography\u2026",
@@ -45974,6 +46128,7 @@ var VIDEO_STYLE_IDS = [
   "silkscreen-poster",
   "art-deco-motion",
   "blueprint-drafting",
+  "machine-anatomy",
   "holographic-scan",
   "paper-popup",
   "shadow-theatre",
@@ -45986,7 +46141,15 @@ var VIDEO_STYLE_IDS = [
   "stop-motion-objects",
   "miniature-diorama",
   "sand-drawing",
-  "generative-light-signal"
+  "generative-light-signal",
+  "satellite-briefing",
+  "briefing-board",
+  "lidar-survey",
+  "white-model-projection",
+  "data-physicalization",
+  "exploded-teardown",
+  "microscope-story",
+  "archive-light-table"
 ];
 var VIDEO_WORKFLOW_IDS = [
   "product-proof",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@docyrus/animaguru",
-  "version": "0.22.0",
+  "version": "0.23.0",
   "description": "Agent-friendly AnimaGuru CLI built with CrustJS",
   "type": "module",
   "bin": {

package/skills/animaguru-archive-light-table/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: animaguru-archive-light-table
+description: Build Archive Light Table visuals and motion in an AnimaGuru PixiJS video workspace. Use when this visual style is chosen for an explainer, advertisement or general video.
+disable-model-invocation: true
+---
+
+# Archive Light Table
+
+Archive photographs and documents on a backlit table, where a loupe turns a negative positive and catalogue records sit beside the objects. It is an evidence style: real data, imagery or scans carry the film. Subject, audience, emotional tone and story come from the user's brief. This style supports Explainer, Advertisement and General Video.
+
+## Establish direction
+
+Follow sibling `animaguru-video` for purpose → style → compact interview before new production. Reuse explicit choices and completed briefs; honor a requested interview skip. Share [the style gallery](https://animaguru.com/animation-styles#archive-light-table). Fold missing visual questions into the shared interview:
+
+- Which archive objects, with catalogue numbers, and do you have rights to the brand's own archive?
+- Which object gets the loupe, and what should change inside the lens?
+
+## Use real evidence
+
+Ask the user for their own data, scans, files or rights first; otherwise find licence-clean sources (see the [production recipe](references/recipe.md)). Never stand a generated image in for the evidence, and never invent a number. Keep `production/FACTS.md` (each on-screen or spoken claim, its source URL and quoted wording, or the measurement method) and `production/CREDITS.md` (every asset's source, author and licence), and deliver both with the film. CC BY-SA, ODbL, "no known restrictions" or non-commercial terms are not CC0: name them to the user and ask before using them.
+
+## Build the look and movement
+
+Read `pixijs` and the relevant Graphics, Text, Container, Assets, Mesh or Filters skills. Read `animaguru` before generating assets: generation can supply music, narration or a title background, never the evidence itself. Discover current models and estimates, respect the user's budget, and reuse completed media. Essential text and exact numerical geometry belong in authored canvas content.
+
+- The objects are real scans at their true proportions with their real damage; every identifier, date and title comes from the holder's record, quoted when you can.
+- Light comes from below: film and glass transmit it and paper glows warm at its edges. The loupe is the camera's door, where a negative develops, a line lights up or a photograph opens into depth.
+- Use no vintage filter: the age is in the objects, not the grade. One signal colour marks anchors, readings and the verdict.
+
+Use the [production recipe](references/recipe.md) for sources, the bundled original study and port-specific decisions. It is a technique example, not a prescribed film. Keep motions a function of absolute seconds; separate drawing cadence from camera/light cadence when the material calls for it. Prepare assets locally, preserve async seeking and register actual resource/cue times. Keep essential type editable and localized.
+
+## Review and delivery
+
+Inspect the lens interior (under about 1.5 screen pixels per scan pixel), reading holds for labels on a moving table, shear in the photograph space and every identifier against its record. Check representative full-resolution frames, moving playback, desktop/mobile fit and cold seeks. Follow `animaguru-video` for production records, audio mixing and HTML5 delivery; export MP4 when requested. Describe the actual 2D/2.5D rendering method accurately. Physically rendered 3D remains deferred.

package/skills/animaguru-archive-light-table/references/recipe.md

@@ -0,0 +1,26 @@
+# Archive Light Table production recipe
+
+The workspace includes an executable original study in `src/studies/scenes.ts`, selected with `archive-light-table`. Its drawing commands are consumed by `src/studies/pixi-renderer.ts`; geometry and time sampling are shared with the gallery renderer. All copy lives in `shared/locales/en/style-studies.json`.
+
+In an untouched starter, run `npm run example -- archive-light-table`, then `npm run dev`. The command refuses to replace an authored film, retains starter backups in `production/example-backup/`, and writes an 8-second study with its own resource tracks. `npm run export:html` and `npm run export:mp4` use this installed film normally. To use the recipe inside an existing film, import `studyFrame()` and `StudyRenderer`, then compose the selected scene into the project's timeline instead of running the installer.
+
+## Evidence and sources
+
+The Library of Congress (check each item's rights statement), Smithsonian Open Access and the Rijksmuseum (CC0), NARA, the NASA Image and Video Library (generally not copyrighted) and Europeana (rights per item). "No known restrictions" and CC BY-SA are not CC0: name the terms and ask first. For brand history, ask for the user's scans, archive numbers and right to use them. Download into the film's `public/` or `production/` folders, log every request, and record each asset in `production/CREDITS.md` and each claim in `production/FACTS.md`. Burn a readable credit into the frame where the medium calls for one.
+
+## Adaptation decisions
+
+- Lay the objects as sprites at true size on one table `Container` over a near-white emissive backdrop; a negative is its positive scan through a transmission curve in a small filter.
+- The loupe renders a magnified copy of the table inside a circular mask, with a `DisplacementFilter` for the pincushion and slight per-channel offsets for fringes. The develop front is a growing radial mask between the negative and positive copies.
+- Into the photograph: grow the lens mask past the frame while the view inside widens to the whole picture, then give it depth with two or three cut layers and a small dolly, small enough that fills stay hidden.
+
+The study is silent, original procedural art with illustrative values, labelled as such; it demonstrates material, light, layout and motion, not evidence. Replace its stand-ins with the real data, imagery or scans described above, never with generated imagery. The gallery preview is three public-domain NASA Ames scans; their negatives are simulated from the positive scans, as the frame says. Configure the subject, palette, scene sequence, duration and soundtrack from the brief.
+
+Use `src/studies/timing.ts` for deterministic easing, seeded variation, measured stroke truncation and cue helpers. `window.animaguru.texts` exposes visible study text bounds for `npm run review`; text declarations alone do not count as visual proof. Inspect the actual frames as well.
+
+## Sources and attribution
+
+Inspired by the following pinned references; source-specific 3D/media dependencies are not bundled. New study art and scene geometry are original. The workspace's `VIDEO-STYLE-NOTICES.txt` preserves the repository notices and clarifies third-party asset scope.
+
+- [styles/archive-lighttable/STYLE.md](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/archive-lighttable/STYLE.md)
+- [styles/archive-lighttable/demo/film.js](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/archive-lighttable/demo/film.js)

package/skills/animaguru-briefing-board/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: animaguru-briefing-board
+description: Build Engineering Briefing Board visuals and motion in an AnimaGuru PixiJS video workspace. Use when this visual style is chosen for an explainer, advertisement or general video.
+disable-model-invocation: true
+---
+
+# Engineering Briefing Board
+
+A filmed whiteboard wall where printed cards land with weight and marker ink in fixed colours measures every option against one limit. It is an evidence style: real data, imagery or scans carry the film. Subject, audience, emotional tone and story come from the user's brief. This style supports Explainer, Advertisement and General Video.
+
+## Establish direction
+
+Follow sibling `animaguru-video` for purpose → style → compact interview before new production. Reuse explicit choices and completed briefs; honor a requested interview skip. Share [the style gallery](https://animaguru.com/animation-styles#briefing-board). Fold missing visual questions into the shared interview:
+
+- Which decision, options and limit should the wall test, and in what real units?
+- Do you have licensable photos of the real objects, or should they be marker sketches and printed cards?
+
+## Use real evidence
+
+Ask the user for their own data, scans, files or rights first; otherwise find licence-clean sources (see the [production recipe](references/recipe.md)). Never stand a generated image in for the evidence, and never invent a number. Keep `production/FACTS.md` (each on-screen or spoken claim, its source URL and quoted wording, or the measurement method) and `production/CREDITS.md` (every asset's source, author and licence), and deliver both with the film. CC BY-SA, ODbL, "no known restrictions" or non-commercial terms are not CC0: name them to the user and ask before using them.
+
+## Build the look and movement
+
+Read `pixijs` and the relevant Graphics, Text, Container, Assets, Mesh or Filters skills. Read `animaguru` before generating assets: generation can supply music, narration or a title background, never the evidence itself. Discover current models and estimates, respect the user's budget, and reuse completed media. Essential text and exact numerical geometry belong in authored canvas content.
+
+- Design the final wall as a poster first, then plan every shot as a crop of it; keep one zone (the verdict or a secondary layer) unseen until the long pull-back.
+- Ink means one thing per colour: graphite for names and rules, blue for measurement, red only for the decision. Draw at hand speed, letter glyph by glyph and erase rejected ideas to faint ghosts.
+- Real things land as cut-out photographs, licensed or the user's own, under one light vector and one grade. With no licensable photo, draw the object as a marker sketch instead of generating one.
+
+Use the [production recipe](references/recipe.md) for sources, the bundled original study and port-specific decisions. It is a technique example, not a prescribed film. Keep motions a function of absolute seconds; separate drawing cadence from camera/light cadence when the material calls for it. Prepare assets locally, preserve async seeking and register actual resource/cue times. Keep essential type editable and localized.
+
+## Review and delivery
+
+Inspect reading holds for every word the camera passes, judgement frames that show item, limit and verdict together, photo upsampling and the share of the wall visible before the reveal. Check representative full-resolution frames, moving playback, desktop/mobile fit and cold seeks. Follow `animaguru-video` for production records, audio mixing and HTML5 delivery; export MP4 when requested. Describe the actual 2D/2.5D rendering method accurately. Physically rendered 3D remains deferred.

package/skills/animaguru-briefing-board/references/recipe.md

@@ -0,0 +1,27 @@
+# Engineering Briefing Board production recipe
+
+The workspace includes an executable original study in `src/studies/scenes.ts`, selected with `briefing-board`. Its drawing commands are consumed by `src/studies/pixi-renderer.ts`; geometry and time sampling are shared with the gallery renderer. All copy lives in `shared/locales/en/style-studies.json`.
+
+In an untouched starter, run `npm run example -- briefing-board`, then `npm run dev`. The command refuses to replace an authored film, retains starter backups in `production/example-backup/`, and writes an 8-second study with its own resource tracks. `npm run export:html` and `npm run export:mp4` use this installed film normally. To use the recipe inside an existing film, import `studyFrame()` and `StudyRenderer`, then compose the selected scene into the project's timeline instead of running the installer.
+
+## Evidence and sources
+
+Wikimedia Commons (read each file page's licence and author), national libraries and archives (check each item's rights statement), agency media pages and Flickr Commons; for the user's own product, site or people, ask for their photos. Every number comes from a cited spec, a measurement or the user's documents. Download into the film's `public/` or `production/` folders, log every request, and record each asset in `production/CREDITS.md` and each claim in `production/FACTS.md`. Burn a readable credit into the frame where the medium calls for one.
+
+## Adaptation decisions
+
+- Build the wall as one large `Container` in board pixels with layers by height (board, prints, props, tray). A camera container moves, scales and rolls it; raised layers get a slightly larger scale, which gives parallax.
+- Bake the enamel, erased ghosts and frame into one texture. Draw ink with `Graphics` strokes revealed by measured length (`strokePoints`), lettering by slicing glyphs, and a slow reflection band as a blurred sprite.
+- Prints are sprites with a blurred shadow offset along one light vector; they land with an ease-out and one small bounce while the shadow tightens. Magnets pop, tags swing on damped springs, and the stamp scales down with a camera jolt.
+
+The study is silent, original procedural art with illustrative values, labelled as such; it demonstrates material, light, layout and motion, not evidence. Replace its stand-ins with the real data, imagery or scans described above, never with generated imagery. The gallery preview is drawn in code with marker sketches and illustrative values. Configure the subject, palette, scene sequence, duration and soundtrack from the brief.
+
+Use `src/studies/timing.ts` for deterministic easing, seeded variation, measured stroke truncation and cue helpers. `window.animaguru.texts` exposes visible study text bounds for `npm run review`; text declarations alone do not count as visual proof. Inspect the actual frames as well.
+
+## Sources and attribution
+
+Inspired by the following pinned references; source-specific 3D/media dependencies are not bundled. New study art and scene geometry are original. The workspace's `VIDEO-STYLE-NOTICES.txt` preserves the repository notices and clarifies third-party asset scope.
+
+- [styles/briefing-board/STYLE.md](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/briefing-board/STYLE.md)
+- [styles/briefing-board/demo/kit/board.js](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/briefing-board/demo/kit/board.js)
+- [styles/briefing-board/demo/kit/README.md](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/briefing-board/demo/kit/README.md)

package/skills/animaguru-data-physicalization/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: animaguru-data-physicalization
+description: Build Data Physicalization visuals and motion in an AnimaGuru PixiJS video workspace. Use when this visual style is chosen for an explainer, advertisement or general video.
+disable-model-invocation: true
+---
+
+# Data Physicalization
+
+Statistics built as countable objects on a crafted base, lit like a studio product shot and read at the edge of one unit. It is an evidence style: real data, imagery or scans carry the film. Subject, audience, emotional tone and story come from the user's brief. This style supports Explainer, Advertisement and General Video.
+
+## Establish direction
+
+Follow sibling `animaguru-video` for purpose → style → compact interview before new production. Reuse explicit choices and completed briefs; honor a requested interview skip. Share [the style gallery](https://animaguru.com/animation-styles#data-physicalization). Fold missing visual questions into the shared interview:
+
+- Which real series and unit (one piece equals how much), and which comparison or crossover should land?
+- Which materials and base suit the brand: metal, acrylic, wood, stone or coins?
+
+## Use real evidence
+
+Ask the user for their own data, scans, files or rights first; otherwise find licence-clean sources (see the [production recipe](references/recipe.md)). Never stand a generated image in for the evidence, and never invent a number. Keep `production/FACTS.md` (each on-screen or spoken claim, its source URL and quoted wording, or the measurement method) and `production/CREDITS.md` (every asset's source, author and licence), and deliver both with the film. CC BY-SA, ODbL, "no known restrictions" or non-commercial terms are not CC0: name them to the user and ask before using them.
+
+## Build the look and movement
+
+Read `pixijs` and the relevant Graphics, Text, Container, Assets, Mesh or Filters skills. Read `animaguru` before generating assets: generation can supply music, narration or a title background, never the evidence itself. Discover current models and estimates, respect the user's budget, and reuse completed media. Essential text and exact numerical geometry belong in authored canvas content.
+
+- The unit is an object: one plate, block or coin equals one stated quantity, said once on screen, and every tenth piece is a heavier ruler material. Heights are exact counts, rounded by one unit at most.
+- Growth is assembly: pieces land one by one with weight, an ease-out and an unwinding yaw, and counters roll with the landed pieces, never with time. Reveal the chart once as a made installation.
+- Use studio light and real matter: a warm low key, a cool rim and long soft shadows. Material, not paint, separates series, and one accent marks the reading or verdict that matters.
+
+Use the [production recipe](references/recipe.md) for sources, the bundled original study and port-specific decisions. It is a technique example, not a prescribed film. Keep motions a function of absolute seconds; separate drawing cadence from camera/light cadence when the material calls for it. Prepare assets locally, preserve async seeking and register actual resource/cue times. Keep essential type editable and localized.
+
+## Review and delivery
+
+Inspect counts against the data file, series separation at thumbnail size, readings kept inside the frame, a verdict that waits until its readings have been still, and the source line in frame. Check representative full-resolution frames, moving playback, desktop/mobile fit and cold seeks. Follow `animaguru-video` for production records, audio mixing and HTML5 delivery; export MP4 when requested. Describe the actual 2D/2.5D rendering method accurately. Physically rendered 3D remains deferred.

package/skills/animaguru-data-physicalization/references/recipe.md

@@ -0,0 +1,27 @@
+# Data Physicalization production recipe
+
+The workspace includes an executable original study in `src/studies/scenes.ts`, selected with `data-physicalization`. Its drawing commands are consumed by `src/studies/pixi-renderer.ts`; geometry and time sampling are shared with the gallery renderer. All copy lives in `shared/locales/en/style-studies.json`.
+
+In an untouched starter, run `npm run example -- data-physicalization`, then `npm run dev`. The command refuses to replace an authored film, retains starter backups in `production/example-backup/`, and writes an 8-second study with its own resource tracks. `npm run export:html` and `npm run export:mp4` use this installed film normally. To use the recipe inside an existing film, import `studyFrame()` and `StudyRenderer`, then compose the selected scene into the project's timeline instead of running the installer.
+
+## Evidence and sources
+
+Our World in Data (credit OWID and the original source), World Bank Open Data and Eurostat (CC BY 4.0), US Census, BLS and EIA (public domain), national statistics offices, or the user's own reports with the document they come from. Textures and HDRIs from Poly Haven or ambientCG (CC0). Download into the film's `public/` or `production/` folders, log every request, and record each asset in `production/CREDITS.md` and each claim in `production/FACTS.md`. Burn a readable credit into the frame where the medium calls for one.
+
+## Adaptation decisions
+
+- Lay out the stacks from one table of values and the unit. Draw each piece as a small shaded box (`Graphics` faces in painter's order, or one shaded piece sprite per material reused with per-piece tint and offset), back to front.
+- Bake the base (for example a walnut slab with inlaid ticks and labels) into a texture, cast shadows as blurred sprites along one light vector, and soften far layers with a `BlurFilter` for depth of field.
+- Pin readings to projected piece corners with a leader, a material swatch and a paper plate, and keep them inside a safe box while the camera tracks.
+
+The study is silent, original procedural art with illustrative values, labelled as such; it demonstrates material, light, layout and motion, not evidence. Replace its stand-ins with the real data, imagery or scans described above, never with generated imagery. The gallery preview is rendered in code with illustrative values. Configure the subject, palette, scene sequence, duration and soundtrack from the brief.
+
+Use `src/studies/timing.ts` for deterministic easing, seeded variation, measured stroke truncation and cue helpers. `window.animaguru.texts` exposes visible study text bounds for `npm run review`; text declarations alone do not count as visual proof. Inspect the actual frames as well.
+
+## Sources and attribution
+
+Inspired by the following pinned references; source-specific 3D/media dependencies are not bundled. New study art and scene geometry are original. The workspace's `VIDEO-STYLE-NOTICES.txt` preserves the repository notices and clarifies third-party asset scope.
+
+- [styles/data-physical/STYLE.md](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/data-physical/STYLE.md)
+- [styles/data-physical/demo/set.js](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/data-physical/demo/set.js)
+- [styles/data-physical/demo/film.js](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/data-physical/demo/film.js)

package/skills/animaguru-exploded-teardown/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: animaguru-exploded-teardown
+description: Build Exploded Teardown visuals and motion in an AnimaGuru PixiJS video workspace. Use when this visual style is chosen for an explainer, advertisement or general video.
+disable-model-invocation: true
+---
+
+# Exploded Teardown
+
+A product taken apart on one axis under studio light, every part named with the numbers in its own files, then closed and dimensioned. It is an evidence style: real data, imagery or scans carry the film. Subject, audience, emotional tone and story come from the user's brief. This style supports Explainer, Advertisement and General Video.
+
+## Establish direction
+
+Follow sibling `animaguru-video` for purpose → style → compact interview before new production. Reuse explicit choices and completed briefs; honor a requested interview skip. Share [the style gallery](https://animaguru.com/animation-styles#exploded-teardown). Fold missing visual questions into the shared interview:
+
+- Which product and revision, and do you have its CAD, PCB layout, bill of materials and spec sheet?
+- Which parts deserve a stop, and which real motion or light should it perform?
+
+## Use real evidence
+
+Ask the user for their own data, scans, files or rights first; otherwise find licence-clean sources (see the [production recipe](references/recipe.md)). Never stand a generated image in for the evidence, and never invent a number. Keep `production/FACTS.md` (each on-screen or spoken claim, its source URL and quoted wording, or the measurement method) and `production/CREDITS.md` (every asset's source, author and licence), and deliver both with the film. CC BY-SA, ODbL, "no known restrictions" or non-commercial terms are not CC0: name them to the user and ask before using them.
+
+## Build the look and movement
+
+Read `pixijs` and the relevant Graphics, Text, Container, Assets, Mesh or Filters skills. Read `animaguru` before generating assets: generation can supply music, narration or a title background, never the evidence itself. Discover current models and estimates, respect the user's budget, and reuse completed media. Essential text and exact numerical geometry belong in authored canvas content.
+
+- Geometry, positions and counts come from the product's own files. Without files, build only from published dimensions, say that it is a model, and show no number you could not source.
+- Separate layers on one axis, top first, with even gaps and a long settle; repeated parts lift in a wave. Labels sit in a fixed column (index, name, one spec line); close bottom first and draw dimensions in the object's own perspective.
+- Keep the frame dark and neutral so the product is the brightest thing, use one accent for measured lines and indices, and show plain package tops instead of brand marks.
+
+Use the [production recipe](references/recipe.md) for sources, the bundled original study and port-specific decisions. It is a technique example, not a prescribed film. Keep motions a function of absolute seconds; separate drawing cadence from camera/light cadence when the material calls for it. Prepare assets locally, preserve async seeking and register actual resource/cue times. Keep essential type editable and localized.
+
+## Review and delivery
+
+Inspect label reading time at each stop, leader anchors through the orbit, revision consistency between files, dark plastics against the ground and every number against `FACTS.md`. Check representative full-resolution frames, moving playback, desktop/mobile fit and cold seeks. Follow `animaguru-video` for production records, audio mixing and HTML5 delivery; export MP4 when requested. Describe the actual 2D/2.5D rendering method accurately. Physically rendered 3D remains deferred.

package/skills/animaguru-exploded-teardown/references/recipe.md

@@ -0,0 +1,27 @@
+# Exploded Teardown production recipe
+
+The workspace includes an executable original study in `src/studies/scenes.ts`, selected with `exploded-teardown`. Its drawing commands are consumed by `src/studies/pixi-renderer.ts`; geometry and time sampling are shared with the gallery renderer. All copy lives in `shared/locales/en/style-studies.json`.
+
+In an untouched starter, run `npm run example -- exploded-teardown`, then `npm run dev`. The command refuses to replace an authored film, retains starter backups in `production/example-backup/`, and writes an 8-second study with its own resource tracks. `npm run export:html` and `npm run export:mp4` use this installed film normally. To use the recipe inside an existing film, import `studyFrame()` and `StudyRenderer`, then compose the selected scene into the project's timeline instead of running the installer.
+
+## Evidence and sources
+
+The user's own CAD, layout files and BOM first. For a public product, open hardware (GitHub, the OSHWA list, Hackaday.io) with its original CAD, and component datasheets from the maker. CC0, public domain, CC BY and MIT are fine with credit; CERN-OHL, CC BY-SA and GPL hardware: name the terms and ask first. Download into the film's `public/` or `production/` folders, log every request, and record each asset in `production/CREDITS.md` and each claim in `production/FACTS.md`. Burn a readable credit into the frame where the medium calls for one.
+
+## Adaptation decisions
+
+- Convert the CAD offline to simple extruded outlines per layer (outline, holes, heights). Draw each layer's faces with `Graphics` from one camera, layer by layer along the lift axis, and map the board artwork onto the board's top face with a `PerspectiveMesh`.
+- Paint the board texture once from the layout (copper, pads, silkscreen). Emitters are additive sprites that switch on while the layers are apart.
+- Project labels and dimension lines with `Graphics` and `Text` every frame, and interpolate camera keys monotonically so a macro hold really holds.
+
+The study is silent, original procedural art with illustrative values, labelled as such; it demonstrates material, light, layout and motion, not evidence. Replace its stand-ins with the real data, imagery or scans described above, never with generated imagery. The gallery preview is rendered in code from an original model whose dimensions it labels. Configure the subject, palette, scene sequence, duration and soundtrack from the brief.
+
+Use `src/studies/timing.ts` for deterministic easing, seeded variation, measured stroke truncation and cue helpers. `window.animaguru.texts` exposes visible study text bounds for `npm run review`; text declarations alone do not count as visual proof. Inspect the actual frames as well.
+
+## Sources and attribution
+
+Inspired by the following pinned references; source-specific 3D/media dependencies are not bundled. New study art and scene geometry are original. The workspace's `VIDEO-STYLE-NOTICES.txt` preserves the repository notices and clarifies third-party asset scope.
+
+- [styles/teardown/STYLE.md](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/teardown/STYLE.md)
+- [styles/teardown/demo/src/main.js](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/teardown/demo/src/main.js)
+- [styles/teardown/demo/src/overlay.js](https://github.com/lemomo-ai/lemo-opuscar/blob/b5e8ef93930b6d828f352055a689320f138237b1/styles/teardown/demo/src/overlay.js)

package/skills/animaguru-lidar-survey/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: animaguru-lidar-survey
+description: Build LiDAR Survey visuals and motion in an AnimaGuru PixiJS video workspace. Use when this visual style is chosen for an explainer, advertisement or general video.
+disable-model-invocation: true
+---
+
+# LiDAR Survey
+
+Measured point clouds flown through in the dark, peeled by a cutting plane and condensed into a raking-lit surface with traced features. It is an evidence style: real data, imagery or scans carry the film. Subject, audience, emotional tone and story come from the user's brief. This style supports Explainer, Advertisement and General Video.
+
+## Establish direction
+
+Follow sibling `animaguru-video` for purpose → style → compact interview before new production. Reuse explicit choices and completed briefs; honor a requested interview skip. Share [the style gallery](https://animaguru.com/animation-styles#lidar-survey). Fold missing visual questions into the shared interview:
+
+- Which place and dataset (or the user's own scan), and which feature should the survey reveal?
+- Which classes should be peeled or kept, and which one reading should land?
+
+## Use real evidence
+
+Ask the user for their own data, scans, files or rights first; otherwise find licence-clean sources (see the [production recipe](references/recipe.md)). Never stand a generated image in for the evidence, and never invent a number. Keep `production/FACTS.md` (each on-screen or spoken claim, its source URL and quoted wording, or the measurement method) and `production/CREDITS.md` (every asset's source, author and licence), and deliver both with the film. CC BY-SA, ODbL, "no known restrictions" or non-commercial terms are not CC0: name them to the user and ask before using them.
+
+## Build the look and movement
+
+Read `pixijs` and the relevant Graphics, Text, Container, Assets, Mesh or Filters skills. Read `animaguru` before generating assets: generation can supply music, narration or a title background, never the evidence itself. Discover current models and estimates, respect the user's budget, and reuse completed media. Essential text and exact numerical geometry belong in authored canvas content.
+
+- Every point is a real return at its measured position: colour by height above ground or by class, value by intensity, never moved into a shape. Points appear behind a front or by height, never by a random fade.
+- Peel with a cutting plane by height above ground, then condense the remaining ground into a raking-lit surface. Exaggerate micro relief only with an on-screen note, and measure on undistorted data.
+- Keep the background near black, fronts a cool near-white and one amber accent for traced features and the reading. Traced features are interpretation: say "traced".
+
+Use the [production recipe](references/recipe.md) for sources, the bundled original study and port-specific decisions. It is a technique example, not a prescribed film. Keep motions a function of absolute seconds; separate drawing cadence from camera/light cadence when the material calls for it. Prepare assets locally, preserve async seeking and register actual resource/cue times. Keep essential type editable and localized.
+
+## Review and delivery
+
+Inspect point sizes and fog at distance, registration between points and surface at the front, the exaggeration note, privacy cropping and the reading against `FACTS.md`. Check representative full-resolution frames, moving playback, desktop/mobile fit and cold seeks. Follow `animaguru-video` for production records, audio mixing and HTML5 delivery; export MP4 when requested. Describe the actual 2D/2.5D rendering method accurately. Physically rendered 3D remains deferred.