Read authoring scripts, art direction and motion fundamentals for every authoring task. Write the art-direction choice (verb, geometry, palette, scale, words) before authoring a node.
Load only the additional references the brief needs:
- Composition or text hierarchy: composition and typography
- Product feedback, states, or reduced motion: product microinteractions
- Cursor, hover, press, drag, or bound inputs: pointer interaction
- Product surfaces, application chrome, or shared-element morphs: product UI craft
- Seamless or intentionally cut loops: loop design
- Camera orbit, depth, parallax, or 2.5D: orbit camera
- Glass or backdrop refraction: glass and refraction
- Duotone palettes or ordered dithering: duotone and dither
- Custom SkSL: custom shaders
- Tiled backdrops, lattices, stripes, pixel chains, dot rings, or any repeated unit: pattern systems
- Fills that flood, wipe, drain, or open from a point or edge, clip paths, mattes: reveals and masks
- Entrance and exit timing, staggers, pops, overshoots, or the beat structure of a piece: motion recipes
- Any text node, titles, numerals, placeholder copy, or a font that must match a reference: text and fonts
- Soundtracks, sound effects or any audio node: the Audio section of authoring scripts
- Logos, wordmarks, badges, pictograms, or shapes built from primitives: shape construction
- Recreating or verifying against a video, mockup, or existing motion: matching a reference
- A brief with no reference at all — start from case studies and pick the five roles before any shape.
For every effect edit, also read effect parameters. After meaningful changes, read previewing work. Before completion, read self-review and review the exact revision being delivered.
Use clayzo commands. Do not use repository-only commands, private APIs, or obsolete package entrypoints.