huashu-art-motion

Open Design host conventions

This is a functional skill within the current task. Preserve the user-selected task type, brand, tech stack, current phase, and delivery format; do not turn it into a video project because of an @ selection. In the planning phase, only plan; only write code in the implementation phase. Checks, rendering, and export are performed only when the host's current phase allows it and the tools are genuinely available; the skill cannot additionally launch independent Agents, force approvals, or bypass host delivery boundaries.

Auxiliary files are read relative to the current skill package root; read selectively based on the current problem, and do not paste all reference documents into the prompt. Do not read other Agents' global configurations. For assets, prioritize the user's existing files; when new images, videos, or audio are needed, use the tools actually provided by the current host and permitted by the user. When generation, measurement, or export capabilities are missing, state the specific gap, deliver the verifiable parts, and do not claim to have completed steps that were not executed. Follow the current task's output paths, and do not overwrite inputs or historical artifacts.

Huashu Art Animation: Open Design adaptation

Scope of application and package boundaries

Within an existing task, break down reference animations, choose art materials, design storyboards, choreograph in-frame motion, or implement a single shot in a narration. This package provides the complete 35 art recipes, 9 narration grammar cards, and the source code of eight general-purpose Canvas tool modules; it does not install the upstream full-film renderer, the 35 sample films, character frames, fonts, voice cloning, or an independent credentials system. Selecting this skill does not mean an MP4 can already be exported.

Workflow

1. Determine the on-screen event. From the user's subject matter, existing assets, and the accepted brief, write clearly the main object, action, visual result, duration, and dimensions. In reference film breakdowns, look at composition, motion, and transition mechanisms; do not copy pixel by pixel. When requirements are clear, execute directly; do not force three directions or tier by model identity.
2. Lock the expressive language. From references/index.md find the style or narration grammar that best fits the content; read the corresponding section. Preserve the user-specified brand colors and fonts; the color taboos, characters, and sample film parameters in the reference cards serve only as contextual suggestions. Recompose for new subject matter; do not reuse the author's characters and demonstration assets.
3. Make a shot list. Use the template from references/craft-workflow.md to record time segments, objects in frame, actions, camera, on-screen text, and implementation method. Prioritize letting concrete objects explain the content; avoid consecutive title cards and meaningless fades; art frames can keep breathing, and the action in narration shots follows the narrative events. For existing voiceover, use the real audio track and time points; do not fabricate transcripts or measurement results.
4. One frame first, then implement motion. Lock the key composition first during the design phase allowed by the host. During implementation, use the existing stack; for Canvas tasks you can take the U, KIT, PAINT, MO, and CAM functions from references/canvas-helpers.md (brush/render/post extend PAINT). Load U first, then load the needed modules, and set the actual stage dimensions. The specific scenes, parameterized clip renderer, and original project commands are not provided with the package and cannot be called as-is; implement the shots in the current project according to the recipes.
5. Determinism and adaptation. Use seed randomization; a given time t should produce the same frame, with time driven by the host timeline. Support the current host's seek/replay conventions, and handle resize, resource readiness, and reduced-motion preferences. Use drawing caches only locally where needed, and do not treat frames with unloaded fonts or images as acceptance frames.
6. Verify the results allowed by the current stage. Check the opening, key transformations, holds, transitions, and ending; when playback can be observed, also check continuity, reading time, and visual focus. When real assets are available, prioritize letting the assets be the main frame, with code handling camera movement and explanation. Report what was actually watched or tested, and do not use the reference card's historical frame rate as the current performance.
7. Deliver. Save editable source files and required assets according to the host output contract; when export is needed, use the export path already supported by the host. If there is no export tool, state this clearly and do not start upstream deliver/render/voice configuration scripts.

Read on demand

• references/index.md: 35 style and 9 grammar indexes.
• references/art-styles-1.md: the first 18 complete style cards.
• references/art-styles-2.md: the remaining 17 complete style cards.
• references/explainer-grammars.md: 9 complete grammar cards; the narrator grammar among them is a reference design and does not mean this package has character generation capability.
• references/craft-workflow.md: breakdown, mechanics, storyboard, frame first, code drawing, music, and character refinement.
• references/canvas-helpers.md: eight reusable general-purpose Canvas module source files, arranged in dependency order.

Asset boundaries

Upstream demonstration characters, character frames, overview images, third-party fonts, or stroke-order data are not distributed with the package. When users want real people, products, or screenshots, use assets provided by the user that are available; when new assets are needed, use host tools and licensing. The original text's author works, render commands, global paths, tool names, and independent review requirements are source notes and cannot override the host conventions.

License retained with the package

references/license.md Retain source licensing with the session package. When copying reference code into a delivery project, retain upstream attribution and license text.