Use the Designer motion-recipe catalog to find a kind-compatible worked motion example, bind it to real page element IDs, apply its native motion/interaction specs in order, and verify the result in the correct page type.
Where: Designer agent tools → list_motion_recipes → get_motion_recipe → set_motion / set_interactions.
Key ideas
- Recipes are validated starting points: A recipe is a compact native motion/interaction specification with required target roles, constraints, and QA prompts—not a finished visual that can be applied without inspecting the page.
- Targets must be real document elements: Each required role must map to an existing element ID from the current Designer document. Recipe tools validate the chosen targets against the active page and type.
- Page type gates availability: The catalog filters recipes by focus and Designer page kind. Fixed-stage video, motion, and ad sequences use recipes such as kinetic-lockup and product-reveal; scroll-bound recipes are refused on decks, video, motion, and ads.
Steps
- Read the active Designer document and identify the actual elements that can serve as the recipe’s required roles.
- Call list_motion_recipes with the intended brief or focus, page kind, and known target IDs. Read the returned summary, required target roles, constraints, and QA notes.
- Choose a compatible recipe. Fixed-stage examples include kinetic-lockup (background, subject, accent, headline, supporting, endcard) and product-reveal (background, halo, product, headline, detail, cta).
- Call get_motion_recipe with the exact returned recipe_id and a targets_json mapping every required role to a real element ID.
- Review the returned native specs and apply them in the returned order. When both are present, apply set_motion before set_interactions.
- Run check_motion and review_page after application; fix compiler or target errors before adding extra motion.
- Preview and scrub forward/backward, inspect the final/rest frame, test narrow layouts where relevant, and confirm reduced-motion/readability behavior.
- Adjust timing, distance, and emphasis to the page’s actual composition instead of layering multiple complete recipes blindly.
Catalog discovery
- list_motion_recipes accepts a brief, focus, and target IDs, then returns a bounded set of recipes supported by the current Designer page kind.
- Each card includes focus/tags, a summary, required target roles, implementation constraints, and QA checks.
- If no recipe fits, use ordinary native set_motion beats rather than forcing a recipe for another page kind.
Resolve and apply
- get_motion_recipe requires a recipe ID returned from the live list and one existing document element ID per required role.
- The result contains validated set_motion and/or set_interactions payloads but does not apply them by itself.
- For a recipe containing both payloads, apply motion first, interactions second, then run check_motion and review_page.
- Recipe validation confirms structure and target identity; it does not prove the visual composition is good. Inspect the actual stage and adjust.
Fixed-stage recipes
- kinetic-lockup sequences environment, subject, accent, headline, supporting text, and a final endcard across one shot.
- product-reveal gives the product a distinct lead, establishes a real halo/graphic, resolves headline and detail, then leaves the CTA as the end state.
- These are Designer fixed-stage recipes and are separate from motion recipes or playbooks in f0 video/Flowgen.
Tips
- Start with a small set of semantically distinct layers; role mapping is easier to validate than targeting one monolithic group.
- Treat recipe constraints and QA notes as required review criteria, not optional decoration.
Limitations and important notes
- Recipes are limited to the active page kind and supported native motion vocabulary.
- A recipe result is only a proposed payload until native write tools apply it.
- Scroll-bound recipes are not offered for decks, video, motion pieces, or ads.
Troubleshooting
The recipe list is empty or a recipe is refused.
Check the active page kind/focus and choose only a recipe returned by the current list. Scroll recipes are excluded for several fixed-stage kinds.
get_motion_recipe says a target is missing or invalid.
Read the current document and use exact existing element IDs for every required role; do not pass labels or invented identifiers.
The tools returned a recipe but the stage still looks wrong.
The recipe is a validated starting payload, not visual certification. Review the stage, run check_motion/review_page, and adjust target geometry, timings, and hierarchy.