@autoaiai/aicut 0.1.11 → 0.1.13

package/skills/erduo-broll-loop-engineering/references/runtime/remotion-hyperframes-map.md

@@ -1,76 +0,0 @@
-# Remotion and HyperFrames concern map
-
-Read this file only when designing or reviewing a runtime adapter. This map
-does not install either runtime, provide porting code, or claim that matching
-renders exist.
-
-## Mapping boundary
-
-Map a validated semantic recipe independently into each runtime. Do not use
-Remotion source as the canonical representation and do not treat a mechanical
-TSX-to-HyperFrames rewrite as the compatibility layer.
-
-```text
-validated semantic recipe
-├── Remotion adapter        -> Remotion-owned source and evidence
-└── HyperFrames adapter      -> HyperFrames-owned source and evidence
-```
-
-New production projects default to HyperFrames. Remotion is explicit opt-in or
-canary, and auto planning is experimental until both runtimes have the same
-creative viewing-and-revision loop. Both branches are independent production concerns. The Parent's deterministic planning script
-assigns a shot only from exact capability or pattern/backend evidence;
-targeted readiness then verifies the required dependencies, licenses, source
-path, and witnesses.
-
-## Concern mapping
-
-| Concern | Runtime-neutral recipe | Remotion adapter responsibility | HyperFrames adapter responsibility |
-| --- | --- | --- | --- |
-| Time truth | absolute integer milliseconds | convert milliseconds to frame evaluation with a declared rounding policy | convert milliseconds to the runtime timeline without changing shot boundaries |
-| Shot window | inclusive `startMs`, exclusive `endMs` | place runtime-owned composition or sequence inside the exact window | place runtime-owned composition or track inside the exact window |
-| Visual state | initial state, result state, focus order | reconstruct every state from requested time | make every state deterministic and seekable from requested time |
-| Motion | semantic phases and visible change | choose runtime-native interpolation or composition logic | choose a supported seek-safe timeline or keyframe implementation |
-| Readability | absolute hold window and readable items | preserve stable readable output through the declared window | preserve stable readable output through the declared window |
-| Material | semantic role and acceptable kinds | resolve a frozen local asset through runtime-owned source | resolve the same frozen local asset through runtime-owned source |
-| Text and fonts | selective copy plus font role | load project-local licensed fonts in the runtime project | load project-local licensed fonts in the HyperFrames project |
-| Composition reuse | capability ID and semantic requirements | select a verified Remotion-owned implementation | select a verified HyperFrames-owned implementation |
-| Runtime state | none in canonical recipe | avoid ambient state that cannot be reconstructed from time | avoid hidden mutable state that breaks deterministic seek |
-| Output evidence | expected semantics and time windows | Builder owns check, frozen-unit render, and media facts | Builder owns official check, frozen-unit render, and media facts |
-
-## Non-mechanical mappings
-
-Treat the following as design reviews, not syntax substitutions:
-
-- frame evaluation versus integer-millisecond timeline conversion;
-- React component composition versus HyperFrames composition and track
-  structure;
-- hooks, effects, context, or mutable state versus deterministic state at an
-  arbitrary seek time;
-- runtime-specific media loaders, font loaders, package assets, and browser
-  assumptions;
-- physics, easing, random values, masks, filters, shaders, and third-party UI
-  libraries;
-- runtime-specific audio timing, metadata discovery, and asynchronous work.
-
-If semantic behavior cannot be preserved independently, classify the required
-capability as `native-remotion`, `native-hyperframes`, `interop`, or
-`unsupported`. Do not label a lossy translation `portable`.
-
-## Future witness review
-
-For a future capability to advance beyond `contract-only`, preserve evidence
-for each runtime independently:
-
-- exact recipe and capability-matrix versions;
-- runtime, adapter, dependency, and browser versions;
-- dependency license and asset provenance review;
-- declared millisecond-to-runtime conversion and rounding policy;
-- deterministic start, action, result, readable-hold, and end observations;
-- arbitrary seek checks, not only linear playback;
-- actual check and render results with objective media facts;
-- known visual or timing differences.
-
-Only after both witnesses exist may a comparison run. Similarity evidence may
-support a narrow documented claim; it must not be generalized into automatic
-Remotion/HyperFrames render parity.

package/skills/erduo-broll-loop-engineering/references/runtime/runtime-contract.md

@@ -1,174 +0,0 @@
-# Runtime-neutral shot, planning, and frozen-media contract
-
-## Production boundary
-
-- New projects default to HyperFrames. Remotion is explicit opt-in or canary;
-  `auto` and `hybrid` are experimental explicit routes in v1.0.1.
-- Director finishes runtime-neutral Recipes before deterministic backend
-  planning.
-- Explicit/detected HyperFrames or Remotion forces the whole film and remains
-  compatible with existing single-backend runs.
-- Explicit experimental auto may result in HyperFrames, Remotion, or hybrid.
-  Explicit hybrid permits both but never forces an evidence-free split.
-- Legacy hybrid means backend-native block construction followed by frozen-media
-  exchange. Never translate generated source, import one runtime into the
-  other, or nest live previews/renderers.
-- Remotion selection/planning is not readiness. Require exact matching local
-  `remotion` and `@remotion/cli` plus real project-local CLI evidence.
-- Do not claim visual, timing, or render parity. Each backend proves its own
-  implementation; hybrid proves only the frozen-media seam and delivery path.
-- Grandfathered schema-1 single-runtime runs continue unchanged and are not
-  retroactively routed.
-
-## Shared direction and runtime-neutral Recipe v2
-
-Director writes the whole-film context once in `narrative-envelope.json` and
-the visual world once in `visual-system.json`. The latter owns palette and
-typography roles, material/depth logic, composition families, motif semantics,
-rhythm, safe areas, and global prohibitions.
-
-The canonical compact Recipe v2 contains only the shot delta: communication
-goal/focus, composition family, hero-frame relationship, visible
-`microBeats[]`, shot-specific material need, optional craft/pattern locators,
-neighbor handoff, and readability hold. Do not repeat shared system rules. It
-contains no React/TSX/hooks/frames, HyperFrames markup/selectors/CLI, runtime
-paths, dependency versions, or copied implementation source. Schema-1 runs
-remain readable and are not retroactively migrated.
-
-Use parsed SRT integer milliseconds as the sole time truth. Shot windows are
-`[startMs,endMs)`. Phases and readability windows remain absolute integers
-inside their shot. Runtime adapters record their deterministic frame/tick
-rounding outside the Recipe.
-
-`requiredCapabilities` must name the most specific observable needs registered
-in `capability-matrix.json`. Director does not add capabilities merely to steer
-a backend. Unknown and unsupported IDs stop before planning/build.
-
-## Shotcraft evidence
-
-One Recipe may contain zero or one `patternRef`: stable card ID, exact style,
-pinned upstream commit, semantic reason, and runtime-neutral fallback. Catalog
-knowledge is progressively queried. Never bulk-load it.
-
-The pinned Remotion source index is exact backend-native source evidence for a
-selected card. It is not a registered component, dependency closure, render
-witness, or cross-runtime comparison. The deterministic planning script may
-use it as lower priority Remotion preference evidence and must surface
-`reference-source-unverified`. A Builder reads only the selected card/source
-closure and replaces every demo asset with Assets-stage material.
-
-## Deterministic backend planning
-
-After Recipe validation, the Parent runs `scripts/plan-runtime.mjs` with
-`--recipes`, `--selection`, `--narrative-envelope`, `--visual-system`, and an
-unused `--production-root`. A normal v1 call also supplies the validated
-`--representative-scenes` artifact; omitting it retains the legacy v2 planning
-path. Before that call, it runs
-`scripts/create-production-profile.mjs` with the user's width, height, fps,
-audio, and supported output-format constraints, then passes the generated file
-through `--production-profile`. With no explicit constraints the generator
-locks 3840×2160, 30 fps, silent H.264 MP4. The script validates inputs and
-atomically writes the hash-bound profile into the plan plus every minimal
-Builder assignment. Do not dispatch a Runtime Planner Agent or hand-author its
-JSON.
-
-Evidence order is deterministic:
-
-1. explicit/existing-project forced single backend, subject to native conflicts;
-2. native-only capability classification;
-3. strongest capability preference from the matrix;
-4. exact selected-pattern backend reference evidence;
-5. matrix portable default.
-
-No semantic keyword, directory name, agent taste, or signal count participates.
-Equal-priority backend conflicts stop. Decisions are made per shot, then
-adjacent same-backend shots merge into contiguous blocks. Inside each block,
-the planner creates ordered whole-shot `authoringUnits` independently from shot
-duration. Ordinary short-shot units commonly contain 5–8 adjacent shots; for an
-ordinary single-backend film around 180 seconds, target 2–3 production Builders.
-These are deterministic targets, not hard caps. Runtime changes, complex 3D or
-material work, exclusive state, and declared `authoring.continuityGroup`
-boundaries override them. The planner never crosses backends or non-contiguous
-time, splits a shot, or breaks a live transition merely to hit a count.
-Every plan records evidence, unverified
-preferences, warnings, blocks, authoring units, required backends, integration
-mode, and a canonical identity.
-
-## Backend obligations
-
-Every Builder must validate its role/phase assignment, Recipes, and plan
-identity; read only those Recipes, adjacent seam summaries, shared-system locators,
-frozen assets/fonts, and 0–2 selected references; preserve semantic intent and
-exact windows, resolve capabilities, use local materials
-and fonts, produce deterministic seekable source, and record runtime/version,
-time conversion, source identity, pattern/fallback decisions, and honest
-variance. It never reroutes after failure.
-
-For every v1 production assignment, each Builder also freezes exactly one local lossless or
-visually-lossless mezzanine for its assigned authoring unit and writes a
-schema-valid `block-media.json`. Editable runtime-native source remains beside
-the unit; frozen media is the deterministic assembly boundary, not a
-replacement for source. A live effect that must cross a boundary belongs in
-one authoring unit; otherwise use the declared readable seam.
-
-Before production fan-out, each required backend uses one existing Builder in
-Lead mode to create its assigned representative moving scenes and importable
-runtime-native visual source. Hybrid shares runtime-neutral visual tokens, not
-source. `04-visual-lock/visual-lock.json` binds those scenes, source identities,
-assets/fonts, the original Director's concrete witness, and the user's
-`approved` or explicit `skipped` decision. A deterministic assignment gate
-rejects production packets before that contract validates.
-
-The contract binds:
-
-- block/runtime/shot/window identity;
-- uniform raster, fps rational, pixel format, color space, mezzanine class,
-  and audio policy;
-- relative local media path and actual SHA-256;
-- objective container/codec/duration/frame/audio facts;
-- backend source identity for the owning authoring unit;
-- for runtime plan v3, the validated visual-lock identity and the owning
-  backend's runtime-native shared-source identity;
-- FFprobe and full decode;
-- `noRealtimeNesting: true`.
-
-`scripts/validate-frozen-blocks.mjs` checks actual media hashes, profile/audio
-closure, plan closure, v3 visual-lock/shared-source identity, and duration within one frame. A bad unit returns to its
-owning Builder; assembly never transcodes a defect into compliance.
-
-## Scripted assembly, approval, and delivery
-
-After every planned unit passes, the Parent runs
-`scripts/assemble-frozen-production.mjs preview` with the plan, narrative
-envelope, visual system, representative scenes, visual lock, every unit contract, a new preview path, and a new
-identity path. The script resolves contracts against the plan and assembles in
-plan order; CLI contract arguments may be supplied in any order. Missing,
-duplicate, unplanned, or changed contracts fail closed.
-
-The preview identity binds the plan, shared artifacts, plan-ordered contract
-hashes, frozen media hashes, v3 visual-lock identity, profile/audio policy, and preview bytes. User
-approval binds that exact identity. After approval, the Parent runs
-`scripts/assemble-frozen-production.mjs deliver` with the same evidence. It
-revalidates the visual lock, shared-source identities, and everything else,
-then encodes a new full-spec master from frozen unit
-media. It never copies the preview, opens an animation runtime, or dispatches
-an Integrator or Render Agent.
-
-## Evidence gates
-
-Keep these claims separate:
-
-1. **Intent:** initial selector records auto/hybrid/forced-single intent.
-2. **Plan:** deterministic Parent script assigns shots, blocks, and Builder packets.
-3. **Readiness:** targeted dependencies, CLI, browser, media tools, permissions,
-   licensing, and paths pass for exactly the required backends.
-4. **Backend:** each assigned runtime owns deterministic source; Remotion
-   installs once per dependency identity and retains unit-specific
-   typecheck/geometry receipts.
-5. **Frozen unit:** every Builder unit's schema, actual hash, probe/decode, and
-   boundary evidence pass.
-6. **Assembly:** plan-ordered frozen-media assembly closes one final moving preview.
-7. **Approval:** the user approves the unchanged integration identity.
-8. **Delivery:** final master passes FFprobe, full decode, duration/audio, and hash.
-9. **Comparison:** only an explicit separate study may claim cross-runtime
-   differences or parity.

package/skills/erduo-broll-loop-engineering/references/runtime/runtime-selection.md

@@ -1,135 +0,0 @@
-# Runtime selection and post-Director planning
-
-Runtime routing has two distinct decisions. The initial selector records user
-intent or existing-project ownership. The post-Director planner assigns each
-validated Shot Recipe to a backend from declared capability and exact pattern
-evidence, then merges adjacent same-backend shots into contiguous blocks and
-partitions focused whole-shot authoring units within them.
-
-## Initial selector
-
-Decision order:
-
-1. Honor explicit `auto`, `hybrid`, `hyperframes`, or `remotion`.
-2. Otherwise inspect exact existing-project package, config, and composition
-   source signals.
-3. Unambiguous existing-project evidence selects that single backend.
-4. Mixed evidence or an existing package project with no runtime evidence is
-   `action-required`; do not infer ownership from counts or names.
-5. A genuinely new project defaults to production `hyperframes`.
-
-Run:
-
-```text
-node <skill-root>/scripts/detect-runtime.mjs --project <project-root> --json
-```
-
-Add `--runtime <choice>` only for an explicit choice. Preserve stdout as
-`broll-production/00-onboarding/runtime-selection.json` and validate it against
-`runtime-selection.schema.json`. Default detection is bounded, read-only,
-skips symlinks/dependencies/build outputs, never uses a shell, and never runs
-project-local code.
-
-Explicit `auto` and `hybrid` have `readiness: planning-required`. `auto` is an
-experimental canary mode, not the production default. They permit cached
-common preflight and runtime-neutral Direction, not backend installation. Explicit or
-detected `hyperframes`/`remotion` forces the whole film and preserves the 0.4.x
-single-route workflow. Existing schema-1 single-backend artifacts are
-grandfathered and must not be retroactively replanned.
-
-Only an authorized Remotion diagnostic/repair after failed cached preflight may use `--probe-cli`.
-It directly runs the project-local CLI with a minimal sanitized environment.
-Selection never downloads a CLI or substitutes a global executable.
-
-## Deterministic planning script
-
-After Director recipes validate, the Parent runs the bundled script directly.
-Do not dispatch `broll-runtime-plan` in a normal v1 production:
-
-```text
-node <skill-root>/scripts/create-production-profile.mjs \
-  --output <broll-production/production-profile.json> \
-  --width <width> --height <height> --fps <fps> \
-  --audio <silent-or-preserve-source> --master-format h264-mp4
-```
-
-Use no optional flags for the 3840×2160, 30 fps, silent default. Do not write
-the profile JSON manually. Then run:
-
-```text
-node <skill-root>/scripts/plan-runtime.mjs \
-  --recipes <shot-recipes> \
-  --selection <runtime-selection.json> \
-  --narrative-envelope <narrative-envelope.json> \
-  --visual-system <visual-system.json> \
-  --representative-scenes <representative-scenes.json> \
-  --motion-map <motion-map.json> \
-  --original-srt <complete-original.srt> \
-  --original-design <complete-original-design.md> \
-  --hyperframes-executable <verified-absolute-hyperframes-cli> \
-  --production-profile <broll-production/production-profile.json> \
-  --production-root <broll-production>
-```
-
-The normal command atomically writes schema-4
-`broll-production/01-runtime-plan/runtime-plan.json`, minimal Lead packets, and
-minimal Chapter Builder packets under `01-runtime-plan/assignments/`. Recipe v4
-requires the representative set, motion map, complete original SRT, and complete
-original design and the selected backend's verified executable together; use
-`--remotion-executable` for explicit Remotion. Omitting the representative set
-preserves only the legacy planning path. Original-input, executable, and production-profile identities are
-hash-bound into the plan and packets. Never redirect stdout into the plan and
-never edit either output by hand. The script uses only:
-
-- exact `requiredCapabilities` and their matrix classification/preference;
-- exact selected `patternRef` and the pinned backend source index;
-- explicit or existing-project single-runtime force;
-- the matrix portable default after stronger evidence is exhausted.
-
-It never scans semantic prose for keywords. Native capability requirements
-outrank preferences. Capability preferences outrank exact pattern reference
-sources, and both outrank the portable default. Equal-priority conflicting
-evidence is `action-required`.
-
-A pinned Shotcraft Remotion TSX locator is native reference-source evidence,
-not a component or render witness. The plan records it under
-`unverifiedPreferences`. Operator-confirmed production observations support a
-preference but do not claim controlled comparison or visual parity.
-
-Planning occurs per shot, then adjacent same-backend shots merge into
-contiguous blocks and chapter authoring units. Explicit experimental `auto`
-may resolve to HyperFrames, Remotion, or hybrid.
-Explicit `hybrid` must naturally produce both backends; do not split work
-artificially when evidence resolves to one.
-
-## Readiness and Builder dispatch
-
-The installer caches stable machine/tool readiness. Common preflight checks
-the cache plus run-specific input/output facts; after planning, targeted
-preflight selects exactly `requiredBackends`. Missing Pexels does not block
-until Assets reaches a real need. Dispatch Onboarding only when preflight
-reports missing or changed stable backend evidence; never prepare both blindly.
-
-The Parent dispatches each generated assignment packet to its named backend
-Builder only after `gate-builder-assignment.mjs` accepts it. Lead packets create
-the three final samples first. Chapter Builders then render only their assigned
-five-shot canary subset until the identity-bound canary technical gate and the
-user's per-shot choice both pass; no legacy gate state may bypass this
-decision. Every Chapter Builder returns editable source, one direct runtime entry
-per shot, and a bound `accepted|revised` viewing receipt. After canary approval,
-the remaining shots render directly and the Parent assembles the final preview
-only from validated shot files. The user approves that complete moving preview
-before optional Master delivery. No Integrator or Render Agent is dispatched,
-and generated source is never translated, nested, or executed across the
-runtime boundary.
-
-Installed Planner, Integrator, and Render stage Skills are legacy readers for
-older production records only. They are not fallback stages for v1.
-
-## Remotion readiness gate
-
-When a plan requires Remotion, require direct declarations and local
-installations of matching `remotion` and `@remotion/cli`, plus a successful
-project-local `remotion versions` probe. A failed/disabled probe makes targeted
-readiness `action-required`; it does not change the planned backend. A backend
-failure returns to its owning stage and never triggers silent rerouting.

package/skills/erduo-broll-loop-engineering/references/shotcraft/remotion-sources/SOURCE.md

@@ -1,7 +0,0 @@
-# Pinned Remotion reference source
-
-Source: `https://github.com/Vincentwei1021/video-shotcraft@41ee360d82f4c491ba9d88a24a4add7d8ff1cf8b`
-
-License: Apache-2.0. The complete license is shipped at `third_party/licenses/video-shotcraft-APACHE-2.0.txt`.
-
-This directory contains byte-identical TS/TSX reference implementations, shared fixtures, and non-media layout JSON from the pinned source. It intentionally excludes screenshots, textures, audio, fonts, preview videos, and other media. A Remotion Builder may inspect only the selected card's indexed source and its recursively required local imports, then adapt it to frozen production assets. These files are reference source, not automatically registered project components or render witnesses.

package/skills/erduo-broll-loop-engineering/references/shotcraft/upstream-attribution.md

@@ -1,65 +0,0 @@
-# 镜头卡来源与授权说明（2026-08 新增 48 张）
-
-本批 48 张镜头卡的动效手法研究自公开发布的产品宣传片与开源项目主页。
-**所有实现均为从零重写**（re-implemented from scratch）：仓库不包含任何
-原片片段、截图、美术资产或品牌元素；实现中的文案、配色、UI 内容均为
-中性占位模板。原作者未参与本项目，卡片标注来源仅为致敬与研究溯源
-（"仅参考、重新实现"）。
-
-## 法律边界（重要）
-
-- 抽象的动效**手法/技法**（时序结构、缓动思路、编排逻辑）一般属于
-  方法与创意范畴；但**具体表达**（原片的画面、美术、文案、品牌元素、
-  可辨识的整体视听呈现）受版权与商标等权利保护。本项目只研究前者，
-  并通过全部重写、去品牌化、占位化来避免复制后者。
-- 来源作品"公开发布"**不等于**授予复刻或衍生的许可。本表记录的是研究
-  溯源，不是授权凭证；对未获明确许可的来源，我们依赖的是"手法参考 +
-  独立重写、无原素材"这一实践，而非任何来自权利人的授权。
-- 若任何权利人认为某张卡的实现仍构成对其具体表达的复制，请提 issue，
-  我们将及时调整或移除相应内容与标注。
-
-## 来源清单
-
-注：下表按**研究批次**记录来源（一个批次对应一支参考片或一个参考站点，
-覆盖该批次衍生的若干张卡）；卡片文件本身不携带来源标注，逐卡归属见文末
-「逐卡来源映射」附表。
-
-| 研究批次 | 来源 | 类型 | 状态 |
-|---|---|---|---|
-| anime.js | https://animejs.com/ 官网演示（GitHub: juliangarnier/anime） | 开源项目主页（MIT 项目；官网演示的美术呈现版权归作者） | 手法参考，重新实现；未使用其代码或美术 |
-| remotion-bits.dev | https://remotion-bits.dev/ | 开源示例集 | 手法参考，重新实现；未使用其代码 |
-| x.com/amirdzm | X 公开发布的 motion 作品两支（约 13s "Storyboard → Result" 等） | 个人作品（公开发布，未获复刻许可） | 手法参考，重新实现；无原素材 |
-| x.com/1amanly | X 公开发布的 motion 作品 | 同上 | 同上 |
-| x.com/Jerrythe2d | X 公开发布的 motion 作品（约 84s） | 同上 | 同上 |
-| x.com/bohdanmotion | X 公开发布的 motion 作品（约 26s） | 同上 | 同上 |
-| x.com/thiswillblossom | X 公开发布的 SaaS 概念广告（约 2.1s 四宫格） | 同上 | 同上 |
-| x.com/tvnxty | Firecrawl 品牌/产品宣传片（约 66s，公开发布） | 商业宣传片（公开发布，未获复刻许可） | 手法参考，重新实现；无原素材 |
-| x.com/shapelayer | X 公开发布的 motion 作品（约 11.6s） | 同上 | 同上 |
-| x.com/aizal_mp4（个别卡） | Willow Voice 产品宣传片（动效设计师 aizal 作品，约 41s） | 商业宣传片（公开发布，未获复刻许可） | 手法参考，重新实现；无原素材 |
-| 抖音 观机社（dy09） | 抖音账号"观机社"发布的荣耀 AI 概念片剪辑（约 22.6s） | 转载剪辑；底层为品牌向概念内容（涉及荣耀/Honor 品牌元素） | 手法参考，重新实现；品牌字标已替换为中性占位词 |
-| 抖音 江经怜（dy08，个别卡） | 抖音账号"江经怜"公开发布的作品（约 19.4s 竖屏） | 个人作品（公开发布，未获复刻许可） | 手法参考，重新实现；无原素材 |
-| reference/brand-scan | 用户提供的参考图定制 | 内部需求 | 原创实现 |
-
-> 已知精确度限制：X / 抖音来源当时以账号主页为单位记录，未逐条留存
-> 具体帖子 URL（原片仅在研究期间本地留存，未入库）。表中已尽量补充
-> 可辨识作品的时长与内容描述；如需逐条溯源可据此在对应账号检索。
-
-## 逐卡来源映射
-
-48 张卡与研究批次的对应关系（来自研究期的原片时段映射记录）：
-
-| 来源 | 卡片 |
-|---|---|
-| anime.js 官网演示 | `radial-wave`、`scramble`、`svg-shape-morph`、`value-stagger-gradient` |
-| remotion-bits.dev | `basic-3d-scene`、`blur-slide`、`card-stack`、`carousel-3d`、`counter-confetti`、`cube-navigation`、`cursor-flyover`、`flying-words`、`fracture`、`glitch-cycle`、`gradient-transition`、`list-reveal`、`mosaic-reframe`、`terminal-3d`、`typing-code-block` |
-| x.com/1amanly | `avatar-bracket-carousel`、`countdown-arc-scatter`、`floating-glossy-label-pills`、`pill-chip-slot-cycle-handled`、`radial-ripple-phone-chips` |
-| x.com/Jerrythe2d | `avatar-grid-radial-build-colorize`、`bezier-source-converge-merge`、`chip-grid-single-select-blackout`、`chip-lift-to-user-pill`、`doc-park-left-pill-deal`、`picker-carousel-feature-cycle`、`scan-bracket-sweep`、`vertical-word-roll-blur-cycle` |
-| x.com/aizal_mp4（Willow Voice） | `aurora-bloom-bg-flip`、`glass-pill-dictation-typing` |
-| x.com/amirdzm（作品 a） | `brace-expand`、`grain-dissolve` |
-| x.com/amirdzm（作品 b） | `hatch-depth` |
-| x.com/bohdanmotion | `outline-word-fill`、`word-relay-geometry` |
-| x.com/shapelayer | `dashboard-glow-highlight-pill` |
-| x.com/thiswillblossom | `quad-split-parallel-scenes` |
-| x.com/tvnxty（Firecrawl 宣传片） | `product-card-progressive-assemble`、`research-card-stack-scroll` |
-| 抖音 观机社 | `logo-shrink-wordmark-lockup`、`white-flash-logo-simplify-cut` |
-| 用户参考图定制（brand-scan） | `assemble-then-type-flyin`、`scanline-annotate-focus`、`scanline-assemble-flyin` |

package/skills/explainer-assets/SKILL.md

@@ -1,98 +0,0 @@
----
-name: explainer-assets
-description: "Generate crafted SVG/CSS components, props, characters, and environments for animated explainer videos — the build order, light rules, factory patterns, and engineering contracts that make assets read as illustrated objects AND survive choreography. Use when creating or upgrading any visual asset: a prop, mascot, component system, or background world. Runs in AICUT: the film is film.html, a page per shot, drawn by `aicut look` and `aicut render`."
-license: MIT
-source: "BusyBee3333/animated-explainer-skills"
----
-
-# Explainer assets — generating components and source art properly
-
-## Running it in AICUT
-
-AICUT's film is `film.html`: it cuts pages, footage, pictures and sound together on tracks. A page is a web page that
-sets `window.film = { frame(t) }` and draws that moment — no framework, no build step, no composition object, no
-`registerRoot`. Five shots are five pages cut together, not one page that changes scene, so each shot stays trimmable
-and replaceable in Studio.
-
-```sh
-npx -y @autoaiai/aicut@latest          # the manual: the format and the commands, always current
-npx -y @autoaiai/aicut@latest open .   # make this folder a film and print Studio's address
-npx -y @autoaiai/aicut@latest look     # a contact sheet of the whole film, its sound, and a determinism check
-npx -y @autoaiai/aicut@latest look 4.5 # one frame, full size — look at the PNG, not at the code
-npx -y @autoaiai/aicut@latest render   # the MP4, beside film.html
-```
-
-Run the manual before the first film: it is authoritative for the format, and this skill is about the method above it.
-
-Where the words below name another program's part, it becomes this:
-
-| elsewhere | in AICUT |
-|---|---|
-| composition, timeline, project file | `film.html`; tracks and clips inside it |
-| a scene, a sequence, a slide | a page (`pages/<name>.html`) cut onto a track |
-| `useCurrentFrame()`, `interpolate()` | `frame(t)` — the picture depends only on `t`, never on state or `Date.now()` |
-| a still, a screengrab | `aicut look <t>` |
-| `render` / `build` / `export` | `aicut render` (the person can also export from Studio) |
-| a dev server, a preview window | `aicut open` and the Studio address it prints |
-
-Hard rules that hold whatever the method says: the picture depends only on `t`; every value in the person's prompt is
-binding; look at the frames `look` writes before saying a film is done.
-
-
-Every asset in an explainer is either a **component** (chips, bars, cards, stamps — styled DOM), a **prop** (vessels, pages, cabinets, gauges — inline SVG), a **character** (host mascot, population minions — SVG factories), or an **environment layer** (parallax worlds — data-URI or inline SVG). Each has its own build discipline. The difference between "styled div" and "crafted object" is a fixed sequence of cheap moves — never skill, always order.
-
-## The universal build order (any prop, every time)
-
-1. **Silhouette first.** Flat single-fill shape at the FINAL footprint (left/top/width/height and viewBox locked before any detail). Get the read at thumbnail size — if the silhouette doesn't say "bucket," no amount of detail will.
-2. **One light source, top-left, film-wide.** Then: 2-tone via `linear-gradient(180deg, lighter, base)` on the body, top gloss (`inset 0 2px 0 rgba(255,255,255,.3-.5)` or a highlight path), bottom shade (`inset 0 -3px 0 rgba(0,0,0,.1)`).
-3. **Depth cues — the 3 that sell 3D:** a DARKER inner-opening ellipse for any mouth/rim (this single ellipse is what makes an opening read as 3D); a soft base-contact shadow ellipse; inter-unit shadow lines between stacked parts (drawers, sheets).
-4. **Detail pass — 3 to 5 accents max:** bands/hoops with a 1px white highlight edge, label plates, grain lines, corner ticks, a specular curve. Stop before it gets busy; Kurzgesagt props are simple shapes with perfect light.
-5. **Motion hooks LAST, planned not patched:** the class the timeline will target, a wrapper `<g>` for any transform the animation will own, and the pivot decided NOW (see svgOrigin below). An asset built without motion hooks gets rebuilt.
-
-## Component systems before one-offs
-
-Never style one chip. Build the SYSTEM in CSS once — every variant inherits:
-- **The sticker recipe:** hard down-right ink drop (`3px 3px 0 var(--ink)`) + top gloss inset + bottom shade inset + `inset 0 0 0 1-2px rgba(255,255,255,.14)` die-cut rim. Translucent insets ride ANY background color, light or dark — one rule elevates every variant.
-- One radius scale (sm 10 / base 13 / lg 16), one shadow angle, one light direction.
-- **Text-safe rule:** on components carrying animated text (SplitText chars), gloss must be inset box-shadows (paint UNDER text) — never a positioned `::before` overlay (paints OVER the glyphs and dims them).
-- Stamps get ink-bleed: same-hue soft `text-shadow` (glyphs) or shared `drop-shadow` filter (SVG marks).
-- Drawn line-art (arrows, boxes): ONE selector — `filter: drop-shadow(0 1.5px .5px rgba(0,0,0,.17))` on all `.drw` strokes gives every arrow a 2-tone underside and reveals WITH DrawSVG (filters are independent of dashoffset).
-
-## Character factories
-
-Characters are **JS functions returning SVG strings**, not static markup — one edit upgrades every instance.
-- **Singleton host** (one instance, e.g. the flying mascot): MAY carry `uid`-suffixed `<defs>` gradients (`'bwg'+uid`) for iridescent wings, radial antenna balls, body sheen. Expose a **faces API** (`host('aha'|'sad'|'happy', size)`) — swap eyes/brows/mouth blocks, keep everything else.
-- **Multi-instance minions** (inlined 10-50×): must be **id-FREE** — plain fills only (wing vein stroke, top highlight ellipse, stripe highlight lines, cheek dot) or gradient ids duplicate across the document and break rendering.
-- **Class-hook contract:** wrapper classes the CSS animates (`hwrap` bob, `hwl/hwr` wing flutter, `heyes` blink) are API — never rename during an asset pass without updating CSS + JS + docs together. New decorative transforms go on INNER wrapper `<g>`s so they compose with (never fight) the CSS animation on the outer hook.
-- Ground-contact shadow under every character; badges/accessories as optional factory args.
-- **Props characters hold get full prop treatment** (the pencil: gradient hex body + facet lines + specular, crimped ferrule, eraser cap with darker rim, wood taper with grain, graphite cone — same anchor/axis as the arm rotation expects).
-
-## Environments (parallax worlds)
-
-- Three layers with fixed roles: **far** (sky gradient, sun/moon, haze band, 2-tone volumetric clouds = tinted base ellipse + 3 white circles + bright top ellipse, far hills), **mid** (hero landmarks — hive/buildings with real detail, layered-petal flowers), **near** (blurred foreground foliage, CORNERS ONLY so it never covers captions, leaf midribs + side veins).
-- Every layer needs a variant per scene mood (warm/paper/cold/dark) — same shapes, recolored; dark gets moon + fireflies.
-- Ambient characters (drifting minions, dust motes) live in **margins and the top strip only** — their full drift path must never cross a text band.
-
-## SVG engineering contracts (each one has broken production)
-
-- **Pivot planning:** a px `transformOrigin` on an SVG group is BBOX-relative — rebuilding the group's geometry silently moves the pivot (a gauge needle swung off-stage for a full scene this way). For fixed pivots in SVG user-space always use GSAP's `svgOrigin:'x y'`, decided when the asset is built.
-- **Selector inventory before touching anything:** grep the script for every class/positional selector; `.bkt3 path` means the FIRST `<path>` must remain the tweened body — lead with `<ellipse>` shadows, never a decorative path.
-- **Footprint freeze:** re-crafting keeps left/top/width/height/viewBox identical; `overflow:visible` lets back-sheets/stacks peek without moving the box. Placement changes are a separate, deliberate pass.
-- **Decorate timeline-driven props with pseudo-elements** (`::before` ruled lines, tape, cracks, meniscus) — they ride the transform with zero new choreography. Track which pseudos are "taken" per class; collisions are silent.
-- **Hide with autoAlpha** (visibility:hidden), not bare opacity/scale — invisible elements must not leave phantom boxes that fool overlap audits.
-- Files need `<meta charset="utf-8">`; HTML entities in DOM text, `\u` escapes in JS strings.
-
-## Quality gates for any new/changed asset
-
-1. Reads correctly at 100% AND at thumbnail scale (the silhouette test).
-2. One light direction across the whole frame — a new prop lit differently is a defect.
-3. No flat fills on anything bigger than an accent.
-4. `node --check` the script block + full selector-survival checklist after any DOM surgery.
-5. Overlap audit (0.5s steps) after placing it — an asset isn't done until it coexists with everything else on stage.
-
-## Source
-
-Rewritten for AICUT from [`BusyBee3333/animated-explainer-skills`](https://github.com/BusyBee3333/animated-explainer-skills)
-(MIT), skills/explainer-assets/SKILL.md. The method is that skill's own; the way it runs is AICUT's.
-
-The repository holds 4 skills; this is the one its entry stands for.