← Files ChatCutARCHIVED FILE
skills/create-motion-graphics/references/overlay-composition.md
3.44 KB · Oct 4, 2026 · 12:31 UTC
# Use visual references for overlays For a new or substantially redesigned overlay, start by finding a good visual reference. The aim is to give the design a concrete visual basis instead of inventing another generic card from a vague adjective. ## Find and inspect a reference Search from the user's content and visual direction. Use a form tag when it is already clear or helps narrow the results; do not require a separate form classification before browsing. Compare the covers, then inspect the chosen instance's hero and summary. Follow collection members when related examples are useful. If none exists or fits, search all instances by content/form without style filters, then inspect a chosen effect image. Keep the fixed project style while borrowing another style's layout. Load motion only when borrowing animation. A pack cover or source frame may show several independent cards. Borrow the selected individual unit, not the showcase grid. A cropped hero establishes its design; consult source context if its relationship with footage is unclear. A standalone card preview still needs placement against the current footage. A reference's photo can represent the current A-roll underneath the graphics. Evaluate that layout against the target shot; the example photo itself need not be imported, and its subject position does not establish the current framing. ## Make the reference guide the actual design Carry the chosen layout, type hierarchy, line lengths, alignment, spacing, proportions, colors and relevant motion into the current content. Borrowing only an accent color or writing "modern editorial card" is insufficient. Avoid replacing the reference with a generic rounded panel or adding unreferenced shadows, gradients and decoration as polish. Cards are welcome when the chosen reference uses them; the goal is to execute the reference well. For direct authoring, inspect the real reference images before writing JSX. For a generation brief, pass the selected instance through `referenceExamples` as described in the main skill, plus a short account of what to retain and what changes for this task. An ID, URL or text description alone does not replace the visual input. If no suitable reference exists, report the gap and follow the user's direction without claiming that a reference was used. Use each instance's own font/effect guidance; membership in one pack does not prove that all examples use the same font. Adapt Chinese or longer copy by reworking line breaks and width while preserving the visual hierarchy. Avoid squeezing the English layout or shrinking all text. Keep supplied quotations accurate; do not copy example faces, logos, facts or attribution into the output. ## Check it in the actual shot Keep footage, production backgrounds and MG graphics in separate items as specified in the main skill. Then inspect the composed timeline at entrance, the settled frame with the most content, and exit. Compare the result with the chosen instance: does it retain the useful hierarchy, spacing and proportions, with readable text and enough reading time? For a cross-style instance, compare structure against that instance and appearance against the fixed project style. Check the subject and subtitles at the intended viewing scale. Fix placement when the composition is the problem, and revise the graphic when it has drifted from the reference. A successful tool call or a transparent thumbnail does not demonstrate visual quality; report unavailable visual checks.
SHA-256: 86172d3830e02b1b1f45d787d9d9ef1ae15087aaa34c13183010d5d55f88e0cd