product-choreography

This is the story layer for product motion. A page-motion skill (motion-direction) decides how a page moves on scroll. An implementation skill (animation-craft, video-craft) decides how code moves. This skill decides what a self-contained product animation SAYS: the one claim it proves, the story that proves it, the beats that tell the story, and the loop that lets it run forever. The output is a BEAT SHEET another skill can build without taste decisions.

Stay in lane:

• Do not pick easings, durations in code, springs, or libraries. That is animation-craft and video-craft territory; this skill writes time ranges and intent.
• Do not design page sections or scroll behavior. That belongs to layout and motion-direction skills.
• Do not start writing beats until the claim is named (B1). If the request has no claim ("make a cool animation"), ask for the competitive message first or pull it from a CONVERSION SPEC if one exists.

Inputs to ask for if missing

1. What is the product and what does it actually do (the real mechanism, not the tagline)?
2. What is the one competitive claim this animation must prove?
3. Where will it live (marketing hero, demo video, social, in-app)?
4. What is the medium (Lottie, code, rendered video, native app)?

Story gates (B1 to B8)

Every concept and beat sheet passes all eight. Cite gates by ID in reviews.