[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DME7KMZ4K4BF8PYZJ2P964":3,"skill-same:01M7DME7KMZ4K4BF8PYZJ2P964":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M7DME7KMZ4K4BF8PYZJ2P964","motion-design",null,"Apply motion craft to an active task: refine a brief, beat map, visual continuity, typography, pacing, and timeline implementation. Use when planning or improving motion graphics; the host task owns artifact creation, output format, and export.","andremolnar\u002Fopen-open-design","andremolnar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F919644?v=4","01M7DHE1X4QH6SJBHR92VG5N84","01M7DHE1XRHK1WQV34AM9M328E",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fmotion-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: motion-design\ndescription: \"Apply motion craft to an active task: refine a brief, beat map, visual continuity, typography, pacing, and timeline implementation. Use when planning or improving motion graphics; the host task owns artifact creation, output format, and export.\"\ntriggers:\n  - motion design\n  - motion graphics\n  - 视频动效\n  - 动态设计\n  - MG动画\n  - kinetic typography\n  - animated explainer\nod:\n  mode: utility\n  category: animation-motion\n  featured: -100\n  example_prompt: Create a 15-second motion film for a focus timer. Show scattered thoughts converging into one clear task, with expressive typography, a continuous visual motif, and a confident closing frame.\n---\n\n# Motion Design\n\nUse this functional helper to refine the user's brief or work in progress with\none clear idea expressed through composition, transformation, rhythm, and appropriate sound unless the user requires silence. Apply the relevant craft guidance within the current task; this\nskill is not a rendering template and does not create a project or choose an\noutput format. The Motion Design creation route owns those decisions. Quality\nmeans viewers understand and remember the idea while wanting to watch it move.\n\n## Execution context\n\nFollow the active host's task route, stage, capability, and delivery contract.\nThis skill supplies motion craft; it does not create tool access or change the\nhost's workflow. In OD Next, retain its Core, general orchestration, V2 machine\ncontracts, route and stage boundaries, and ship-on-write policy. Include the\nmotion brief and beat map in the existing plan; author during Build only.\nUse the host's existing Plan Contract and Runtime State when required, without\ninventing a separate motion protocol or an extra planning gate. Only actual\nuser-requested video-motion production, when the host Core authorizes it,\npermits the bounded video check below. For a video brief (a timed\nfilm, promo, explainer or showreel), declare BOTH editable HTML source and MP4\nas required deliverables. Rendering the MP4 is Build production and must finish\nbefore delivery. For pointer\u002Fscroll-driven interaction or UI micro-animation,\ndeliver runnable HTML\u002Fcode instead; do not flatten the requested interaction\ninto video. Never describe an unrendered video file as complete.\n\nWhere the active host permits visual checking, stay within its authorized scope\nand limits. For OD Next video-motion production, use only the bounded check\nbelow; this paragraph does not authorize any additional review or iteration.\nA runnable file alone is not proof of successful motion. Distinguish what was\nobserved from what was only specified; never invent quality measurements.\n\n## Resolve the brief without stalling\n\nUse the user's assets, references, script and previous decisions first. Resolve:\nmessage and audience; destination\u002Faspect; duration; exact copy; must-show assets;\nvisual direction; audio; and required output. Ask only when missing information\nwould change the story or make the result misleading. Otherwise choose a coherent\ndirection and state the meaningful assumption briefly. Do not impose three\nstyle options or an approval round on a user who asked you to make the piece.\n\nFor an unconstrained short film, a useful starting point is 12–18 seconds,\n16:9, 1920×1080, 30fps, no invented voiceover, and a replayable source. A portrait\nsocial brief calls for 9:16. Existing brand, timing, platform and copy override\nthese defaults. Do not invent product claims, metrics, testimonials or assets.\n\nCreate a compact beat map as part of the existing plan, not a second document:\n`time → viewer takeaway → focal object → transformation → copy\u002Faudio → exit`.\nTime budget includes entrances, reading holds and exits. Choose a recurring\nobject, shape, line or typographic motif that connects the beats.\n\nExample mechanism for a focus product (adapt, do not copy as a universal style):\nscattered words orbit → one word attracts the others → orbit becomes a timer →\ntimer completes and becomes the wordmark. Each movement changes the meaning;\nfour unrelated title cards would lose the mechanism.\n\n## Art direction before adding movement\n\nResolve one strong representative frame in the composition before expanding\nall scenes. Choose the actual hierarchy, crop, type, palette, texture and focal\nobject. A weak still will not be rescued by particles, camera shake or effects.\nWhen planning-only, describe this frame; do not create an artifact early.\n\n- Use a specific visual premise tied to the subject. \"Premium\", \"cinematic\"\n  and \"modern\" alone are not art directions. Define what fills the frame,\n  where attention rests, the material language and the contrast structure.\n- Typography is a graphic object. Compose with scale, alignment, line breaks,\n  negative space and font character. Choose fonts that cover the actual\n  language; use tested fallbacks and wait for font readiness before capture.\n- Prefer a small palette with intentional contrast. No default neon gradient,\n  glass cards, glowing orb or beige background independent of the brief.\n- Choose one material\u002Fworld logic: editorial ink, precise instrument, folded\n  paper, tactile collage, vector geometry, painterly field, or another justified\n  system. Carry its lighting, edges and textures through the film.\n- A scene may be asymmetric, full-bleed or sparse. Avoid repeatedly centering\n  a headline above three cards. Keep subtitles and platform chrome out of the\n  focal area; use destination-specific safe margins, not one universal ratio.\n- Supplied product screens and logos retain their proportions and content.\n  Crop deliberately rather than stretching. Keep data axes, units and values\n  correct through their entire animation.\n\n## Choreograph attention\n\nChoose the lead action and let supporting motion answer it. Offset independent\nobjects when that clarifies reading; move them together when collective motion\nis the idea. Do not mechanically stagger every word or enforce a fixed moving\nfraction of the screen.\n\nUse three possible layers, not three mandatory effects:\n1. Primary action carries the idea.\n2. Secondary action conveys weight or causality: a trailing label, a shadow\n   settling, an elastic edge, a reaction in a connected object.\n3. Ambient motion provides life only when the scene needs it. Quiet scenes\n   and reading holds may be genuinely still.\n\nTiming and spacing have different jobs: timing places story beats; spacing\ncontrols acceleration and weight between them. Suggested starting ranges:\n\n| Job | Starting range | Shape |\n| --- | --- | --- |\n| Small accent \u002F punctuation | 120–220ms | decisive snap, then settle |\n| Main element arrival | 350–650ms | quick travel, controlled landing |\n| Meaningful shape transformation | 600–1200ms | readable setup and resolution |\n| Large reveal \u002F camera move | 900–1800ms | sustained trajectory, clear destination |\n\nThese are film heuristics, not UI response-time limits. Fit distance, mass,\nemotion and soundtrack. Use ease-out for an arrival, ease-in for a motivated\nexit, and smooth acceleration\u002Fdeceleration for a camera. Constant-speed travel\nis appropriate for conveyors, clocks, scans and intentional mechanical motion.\nPlayful material can overshoot; precise instruments should not bounce by default.\n\n- Give fast actions preparation and recovery. Anticipation may be tiny, but\n  there should be a legible cause rather than an unexplained teleport.\n- Change position on arcs when physical motion calls for it. Use straight\n  paths for precision, direction or mechanical intent.\n- Match-cut across shared shapes, track a moving object into the next scene,\n  reveal through a meaningful mask, or use a clean cut. Choose transitions\n  because of the relationship between beats, not a desire for variety.\n- Preserve velocity and direction at hand-offs. Avoid accidental jumps in\n  scale, lighting or object identity. Morph only where topology supports it;\n  a designed match-cut is better than an unreadable mesh distortion.\n- Alternate action and rest. Reserve the strongest transformation for the\n  central idea; endless maximum intensity makes everything feel equal.\n- Close intentionally: resolve the motif and hold the final message. Loops\n  need matching start\u002Fend state AND velocity, without a duplicated pause.\n\n## Choose a visual grammar\n\n**Product \u002F brand film:** build around a real benefit and a concrete action.\nUse actual screens where available, isolate what changes, and carry the brand\nmotif into the closing frame. A slow camera move over a static page is supporting\nfootage, not the entire demonstration.\n\n**Kinetic typography:** let words act out meaning through weight, tracking,\ndirection and transformation. Keep a stable reading window; do not rotate,\nblur or scatter every line. Animate a phrase as a unit when word-by-word entry\nwould obstruct comprehension. Reveal timing is not reading time.\n\n**Explainer \u002F data:** choose spatial metaphors that preserve the causal model.\nShow the object before transforming it; maintain labels while relationships\nchange. Reveal axes before values when the scale matters. If narrated, align\nbeats to actual supplied or generated audio timing, not guessed timestamps.\nDo not add unrelated decoration to cover a weak explanation.\n\n**Art \u002F procedural scene:** distinguish a style's structure from surface noise.\nDefine marks, material, palette, composition and one characteristic movement.\nExamples: a woodcut uses cut-line direction and layered ink; a painted night\nuses coherent curved strokes and moving light; paper cutouts use plane depth,\nedge shadows and hinged motion. Seed texture once and move it coherently;\nregenerating every mark each frame causes flicker. Animate elements inside the\nworld, not only the camera between static paintings. Human identity and complex\nanatomy should use suitable supplied\u002Fgenerated assets when tools allow; keep\nsilhouette, palette and lighting consistent. Never pretend those assets exist.\n\n**3D \u002F professional-tool task:** retain the user's existing AE, Blender or\nRemotion project if specified and available. Read its state, edit the smallest\nrelevant scene, and retain editable layers\u002Fkeyframes. A tool-specific pipeline\nis justified by the desired result, not by the name of this skill. Do not make\ninstallation of AE, Blender, a paid provider or a new framework the default.\n\n## Author reliable editable motion\n\nFor a new Open Design film, use timeline-driven HTML with GSAP and optional\nSVG\u002FCanvas. HTML\u002FSVG suit typography, crisp diagrams and UI; Canvas suits dense\nmarks, fields and procedural worlds. Combine them when useful. Preserve an\nexisting supported renderer instead of rebuilding it just to fit this default.\n\nKeep duration, frame size, palette, type scale, easing and scene timings in one\nsmall configuration. Group each scene's elements and motion together. Separate\ncontent\u002Fdata from drawing. Reuse geometry and cached textures; cap offscreen\nwork and particle counts. Keep a scene stable at any requested timestamp.\n\nThe Open Design video composition contract:\n\n```html\n\u003Cdiv id=\"main\" data-composition-id=\"main\" data-start=\"0\"\n     data-duration=\"15\" data-width=\"1920\" data-height=\"1080\" data-poster-time=\"13.5\">\n  \u003C!-- Real scene elements, sized for this stage. -->\n\u003C\u002Fdiv>\n\u003Cscript>\n\u002F\u002F Load GSAP before this block; retain the host's pinned dependency when supplied.\nconst duration = 15;\nconst tl = gsap.timeline({ paused: true });\n\u002F\u002F Define initial states explicitly, then animate scene objects at absolute times.\n\u002F\u002F tl.fromTo(...); tl.to(...); Reading holds occupy real time in the timeline.\nconst clock = { t: 0 };\ntl.to(clock, { t: duration, duration, ease: 'none' }, 0);\nwindow.__timelines = { main: tl };\n\u002F\u002F A procedural layer must draw from clock.t, not increment state each frame.\n\u002F\u002F Video export seeks with timeline callbacks suppressed, so draw from a\n\u002F\u002F per-frame loop rather than from onUpdate alone:\n\u002F\u002F (function render() { drawWorld(clock.t); requestAnimationFrame(render); })();\n\u003C\u002Fscript>\n```\n\nThis is a protocol skeleton, not a finished visual template. Author the real\ncomposition. Root duration, timeline duration, aspect and the brief must agree.\nUse real seconds: the master timeline must keep `timeScale(1)`, no repeat or\nstart delay, and its actual `duration()` must equal `data-duration`. The setter\n`tl.duration(seconds)` changes playback speed; it does NOT add a reading hold.\nUse the full-length clock tween above, and keep all tracks within its duration.\nThe player and renderer reject inconsistent video clocks before export.\n\nFor SVG pop\u002Fscale entrances, establish a shared origin BEFORE the from state.\nAnimate a common group for related shapes (a disk and its shading), or set the\nsame `svgOrigin` in both states. Do not set it only in the destination: GSAP\nsmooth-origin compensation can offset shapes with different bounding boxes.\n\n```js\nfunction popShape(tl, node, cx, cy, at, duration = 0.45) {\n  const svgOrigin = cx + ' ' + cy;\n  tl.fromTo(node, { scale: 0, svgOrigin },\n    { scale: 1, svgOrigin, duration, ease: 'back.out(2)' }, at);\n}\n```\nUse the actual composition id consistently. Register timelines before signalling\nreadiness; all image\u002Ffont dependencies need a known ready state. Keep assets\nlocal when possible and avoid relying on inaccessible remote URLs.\n\nDeterministic motion must survive forward\u002Fbackward seeking: no Date.now-based\nscene state, unseeded randomness, simulation that only works after playing from\nzero, or independent CSS animation competing with the master timeline. Define\npositions and reveals as functions of time, or as seekable timeline tracks.\nNever make visible content depend on timeline callbacks (onUpdate, onComplete);\nthe MP4 exporter seeks with them suppressed.\nAudio-reactive motion needs a precomputed envelope or known beat map when exact\nreplay matters. Never imply that an arbitrary pulse is analysis of the music.\n\nOpen Design scaffolds and embeds shared source playback: open the HTML to\nautomatically loop the film, with no separate player bar. Click the picture to\npause\u002Fresume or unlock audio blocked by browser autoplay. The internal\n`window.__odMotionPlayer` interface retains play\u002Fpause, seek and replay. Preserve its `script[data-od-motion-source-player]`. Do not create\ncompeting controls or start a second playback clock. The renderer sets\n`window.__odMotionRender` before author scripts to disable preview chrome and\nscaling during capture. The scaffold includes pinned GSAP 3.14.2 at\n`.\u002Fgsap.min.js`; preserve and reference that local file. No download is needed. Prefer installed\u002Fsystem fonts with Chinese coverage; an unrequested font\nmust not block delivery. If an optional download fails, use an available font\ninstead of probing more mirrors, installing font tools or creating environments.\nFor an existing standalone source without the host player, put controls outside the\ncomposition and connect them to the same master timeline. Scale the whole stage\nuniformly to fit; do not reflow scene layout when the viewport changes. Controls\nmust not appear in the exported frames. Keep a useful poster when reduced motion\nis requested and let the user explicitly start playback.\n\n## Plan and produce sound for video\n\nFor a video motion brief, decide voice, music and effects separately in the\nexisting Design Spec and beat map. If the film benefits from music or sound\naccents and the user has not requested silence, add suitable sound proactively.\n“No voiceover” disables speech only; it does not mean no music or effects.\nAn explicit silent\u002Fmuted\u002Fno-sound request wins. Choose silence when justified\nby the destination (for example a silent ambient loop), and state that choice.\nThis policy belongs to video motion; do not add sound to ordinary prototypes,\ndocuments, slides or interactive motion unless their brief calls for it.\n\nRecord the audio decision in the ordinary plan. Declare\n`\u003Cmeta name=\"od-motion-audio\" content=\"required\">` for an audible film or\n`content=\"silent\"` for intentional silence. This is composition metadata for\nthe actual exporter, not a model-output planning contract.\nFor `required`, author real local audio assets inside the composition directory:\nuse supplied\u002Flicensed media, the host audio-generation tool when available, or\nan original synthesized instrumental\u002Feffect WAV. Do not invent an asset URL,\ninstall an unrelated audio environment, or substitute a pulsing visual for sound.\nIf required audio production fails, report the blocker instead of delivering\nsilence as complete.\n\nDeclare every track with the renderer's supported timing, for example:\n`\u003Caudio src=\"assets\u002Fmusic.wav\" data-start=\"0\" data-duration=\"15\" data-volume=\"0.3\" preload=\"auto\">\u003C\u002Faudio>`.\nEffects use the same contract with their own start and duration. Keep sources\nlocal and relative, pre-trim tracks, and avoid loop, playback-rate and media-start\nattributes. Keep music below speech and align accents to the actual beat map.\nPreserve the shared source player: it automatically loops picture and sound, and synchronizes audio to play,\npause, seek and replay. Do not start a second audio clock or use Web Audio alone, which is\nnot an exportable track. The renderer mixes these tracks into the MP4.\n\nIn the existing bounded video check, verify source audio follows those controls,\nthat downloaded MP4 contains an audible audio track, and that key sounds occur\nat the authored times. A file extension or an audio tag alone does not prove\nsound. Silent films remain valid; never require audio for other task types.\n\n## Video production and dual delivery\n\nFor video briefs, use Open Design's existing local HyperFrames renderer during\nBuild. It needs no video-generation API key. Do not ask the user to render it\nmanually or run a second renderer. Plan declares `hyperframes-html` as the\nproduction route, editable source as canonical, and MP4 as a required derived\noutput. For interactive briefs use `html` and source only.\n\nUse only the host's `media scaffold`, `media generate`, and `media wait` entry\npoints for this workflow. Do not invoke the HyperFrames CLI directly for init,\npreview, rendering, or skill installation, including through npx. The host\nkeeps scaffolding and preview local and disables HyperFrames CLI telemetry on\nits render subprocess. Do not enable telemetry or bypass that wrapper.\nMotion MP4 export requires the desktop frame renderer for authored-clock\nvalidation; a headless browser override is not a supported substitute.\n\nKeep source and MP4 paths in the existing plan and in the composition's MP4\nlink. On OD Next, declare them through the host's existing required-deliverable\ncontract and preserve its normal planning-to-production continuation. The\nexporter separately checks the actual output path and declared audio policy.\nDo not invent new machine blocks, contract fields, or a motion-specific gate.\n\nApply this delivery guidance only to the user's actual current video-motion\nrequest within the host's authorized task type and scope. Follow the host's\nexisting task-type change rules for a request in another project. A selected\nscenario or loaded helper alone does not authorize creating a film.\nPlan-only requests end with the plan; interactive motion and hover\u002Fscroll\nanimation in a prototype remain runnable HTML. Follow-ups may directly edit an\nexisting film; re-render only when the requested change affects the video.\n\n1. Scaffold a visible source directory with the native shell tool:\n   `\"$OD_NODE_BIN\" \"$OD_BIN\" media scaffold --project \"$OD_PROJECT_ID\" --composition-dir \"motion-source\u002Ffilm\"`.\n   Use a new descriptive directory for a new film; edit the existing source on\n   revisions. Keep `hyperframes.json`, `meta.json`, HTML and local assets there.\n2. Author `motion-source\u002Ffilm\u002Findex.html`. Its composition root must have\n   `data-composition-id=\"main\"`, `data-start=\"0\"`, `data-duration`, `data-width`,\n   `data-height` and `data-fps`. Register the seekable master timeline at\n   `window.__timelines.main`. Use actual GSAP animations, not a placeholder\n   timeline. Keep assets\u002Ffonts local and relative to this source directory.\n   Include `\u003Cmeta name=\"od-motion-output\" content=\"video\">` and\n   `\u003Clink rel=\"alternate\" type=\"video\u002Fmp4\" href=\"..\u002F..\u002Ffilm.mp4\">` in the head.\n   The href must identify the actual planned MP4 inside the project. The\n   interactive equivalent declares `content=\"interactive\"` and needs no MP4.\n   For video, choose a stable, representative moment in your actual timeline\n   and declare its time in seconds as `data-poster-time` on that root. It must\n   satisfy `0 \u003C= time \u003C data-duration`; avoid an empty opening or a transition.\n   Prefer a frame that communicates the product or main idea at thumbnail size.\n   The host validates the source\u002Fvideo clock and dimensions and extracts this\n   exact frame from the finished MP4. Do not generate a separate invented cover,\n   change the video's opening for the cover, or bake preview containers into it.\n3. Render through the host:\n   `\"$OD_NODE_BIN\" \"$OD_BIN\" media generate --project \"$OD_PROJECT_ID\" --surface video --model hyperframes-html --composition-dir \"motion-source\u002Ffilm\" --output \"film.mp4\"`.\n   If it returns a task ID, use `\"$OD_NODE_BIN\" \"$OD_BIN\" media wait \u003Cid>` and wait for success.\n   A queued task, HTML preview or failed command is not a completed film.\n4. Preserve the source and assets, and link BOTH the actual MP4 and the source\n   HTML in the final response using project-relative Markdown links. The file\n   viewer provides preview\u002Fdownload. On later video edits re-render the same\n   linked MP4 so the download matches the current source.\n\nIf the host reports a renderer failure, preserve the editable source and report\nthat blocker truthfully. Never fabricate a download or label HTML-only output\nas a finished video. Only actual user-requested video-motion production, and\nonly when the host Core authorizes it, permits this bounded check:\n\n- During planning, retain factual invariants and exact required copy in the\n  existing Design Spec\u002Fbeat map. An explainer must preserve the causal mechanism\n  and exceptions when shortening subtitles; decorative metaphors are not facts.\n- After the first render, perform one review of the actual source and exported\n  video: check the clock\u002Fdimensions, compare captions against those invariants,\n  and inspect at most three representative frames (opening, key explanation,\n  ending). Check related SVG shapes stay aligned. Use available host\u002Fbrowser\u002F\n  frame tools and actually view the images; source reading alone is not visual\n  evidence. Do not claim a check that tool access did not allow.\n- If that review or the renderer identifies a concrete defect, make at most one\n  targeted repair and re-render; recheck only the affected facts\u002Fframes. If still\n  incorrect or unverifiable, report the limitation instead of certifying it.\n- Do not spawn acceptance agents, score aesthetics, add a separate pipeline\n  stage, or repeat an open-ended polish loop. Interactive motion, prototypes,\n  slides, documents and other tasks keep their existing ship-on-write policy.\n\n## Quality while composing\n\nFor each beat, account for focal point, motion cause, reading time and exit.\nAt a transition, account for both outgoing and incoming states and their overlap.\nAt the end, account for resolution, holding time and replay behavior.\n\nUse these concrete defect-to-decision pairs while building:\n\n| Defect | Better decision |\n| --- | --- |\n| Feels like a slideshow | Carry one object through a meaningful transformation |\n| Everything competes | Choose the lead action; reduce or delay support |\n| No sense of weight | Adjust travel time, acceleration, anticipation and settle |\n| Text is unreadable | Shorten copy only if allowed; increase hold and contrast |\n| Looks generic | Strengthen type, composition and the subject-specific motif |\n| Painterly texture flickers | Seed and cache marks; move a coherent field |\n| Sequence feels monotonous | Vary shot scale and action\u002Fhold rhythm with purpose |\n| Looks busy but says little | Remove decorative motion and show the causal action |\n\nDo not invent a numeric score to certify aesthetics. Report the usable artifact,\nits duration\u002Faspect, and any missing asset, audio or export capability succinctly.\n","# Motion Design\n\nUse this functional helper to refine the user's brief or work in progress with\none clear idea expressed through composition, transformation, rhythm, and appropriate sound unless the user requires silence. Apply the relevant craft guidance within the current task; this\nskill is not a rendering template and does not create a project or choose an\noutput format. The Motion Design creation route owns those decisions. Quality\nmeans viewers understand and remember the idea while wanting to watch it move.\n\n## Execution context\n\nFollow the active host's task route, stage, capability, and delivery contract.\nThis skill supplies motion craft; it does not create tool access or change the\nhost's workflow. In OD Next, retain its Core, general orchestration, V2 machine\ncontracts, route and stage boundaries, and ship-on-write policy. Include the\nmotion brief and beat map in the existing plan; author during Build only.\nUse the host's existing Plan Contract and Runtime State when required, without\ninventing a separate motion protocol or an extra planning gate. Only actual\nuser-requested video-motion production, when the host Core authorizes it,\npermits the bounded video check below. For a video brief (a timed\nfilm, promo, explainer or showreel), declare BOTH editable HTML source and MP4\nas required deliverables. Rendering the MP4 is Build production and must finish\nbefore delivery. For pointer\u002Fscroll-driven interaction or UI micro-animation,\ndeliver runnable HTML\u002Fcode instead; do not flatten the requested interaction\ninto video. Never describe an unrendered video file as complete.\n\nWhere the active host permits visual checking, stay within its authorized scope\nand limits. For OD Next video-motion production, use only the bounded check\nbelow; this paragraph does not authorize any additional review or iteration.\nA runnable file alone is not proof of successful motion. Distinguish what was\nobserved from what was only specified; never invent quality measurements.\n\n## Resolve the brief without stalling\n\nUse the user's assets, references, script and previous decisions first. Resolve:\nmessage and audience; destination\u002Faspect; duration; exact copy; must-show assets;\nvisual direction; audio; and required output. Ask only when missing information\nwould change the story or make the result misleading. Otherwise choose a coherent\ndirection and state the meaningful assumption briefly. Do not impose three\nstyle options or an approval round on a user who asked you to make the piece.\n\nFor an unconstrained short film, a useful starting point is 12–18 seconds,\n16:9, 1920×1080, 30fps, no invented voiceover, and a replayable source. A portrait\nsocial brief calls for 9:16. Existing brand, timing, platform and copy override\nthese defaults. Do not invent product claims, metrics, testimonials or assets.\n\nCreate a compact beat map as part of the existing plan, not a second document:\n`time → viewer takeaway → focal object → transformation → copy\u002Faudio → exit`.\nTime budget includes entrances, reading holds and exits. Choose a recurring\nobject, shape, line or typographic motif that connects the beats.\n\nExample mechanism for a focus product (adapt, do not copy as a universal style):\nscattered words orbit → one word attracts the others → orbit becomes a timer →\ntimer completes and becomes the wordmark. Each movement changes the meaning;\nfour unrelated title cards would lose the mechanism.\n\n## Art direction before adding movement\n\nResolve one strong representative frame in the composition before expanding\nall scenes. Choose the actual hierarchy, crop, type, palette, texture and focal\nobject. A weak still will not be rescued by particles, camera shake or effects.\nWhen planning-only, describe this frame; do not create an artifact early.\n\n- Use a specific visual premise tied to the subject. \"Premium\", \"cinematic\"\n  and \"modern\" alone are not art directions. Define what fills the frame,\n  where attention rests, the material language and the contrast structure.\n- Typography is a graphic object. Compose with scale, alignment, line breaks,\n  negative space and font character. Choose fonts that cover the actual\n  language; use tested fallbacks and wait for font readiness before capture.\n- Prefer a small palette with intentional contrast. No default neon gradient,\n  glass cards, glowing orb or beige background independent of the brief.\n- Choose one material\u002Fworld logic: editorial ink, precise instrument, folded\n  paper, tactile collage, vector geometry, painterly field, or another justified\n  system. Carry its lighting, edges and textures through the film.\n- A scene may be asymmetric, full-bleed or sparse. Avoid repeatedly centering\n  a headline above three cards. Keep subtitles and platform chrome out of the\n  focal area; use destination-specific safe margins, not one universal ratio.\n- Supplied product screens and logos retain their proportions and content.\n  Crop deliberately rather than stretching. Keep data axes, units and values\n  correct through their entire animation.\n\n## Choreograph attention\n\nChoose the lead action and let supporting motion answer it. Offset independent\nobjects when that clarifies reading; move them together when collective motion\nis the idea. Do not mechanically stagger every word or enforce a fixed moving\nfraction of the screen.\n\nUse three possible layers, not three mandatory effects:\n1. Primary action carries the idea.\n2. Secondary action conveys weight or causality: a trailing label, a shadow\n   settling, an elastic edge, a reaction in a connected object.\n3. Ambient motion provides life only when the scene needs it. Quiet scenes\n   and reading holds may be genuinely still.\n\nTiming and spacing have different jobs: timing places story beats; spacing\ncontrols acceleration and weight between them. Suggested starting ranges:\n\n| Job | Starting range | Shape |\n| --- | --- | --- |\n| Small accent \u002F punctuation | 120–220ms | decisive snap, then settle |\n| Main element arrival | 350–650ms | quick travel, controlled landing |\n| Meaningful shape transformation | 600–1200ms | readable setup and resolution |\n| Large reveal \u002F camera move | 900–1800ms | sustained trajectory, clear destination |\n\nThese are film heuristics, not UI response-time limits. Fit distance, mass,\nemotion and soundtrack. Use ease-out for an arrival, ease-in for a motivated\nexit, and smooth acceleration\u002Fdeceleration for a camera. Constant-speed travel\nis appropriate for conveyors, clocks, scans and intentional mechanical motion.\nPlayful material can overshoot; precise instruments should not bounce by default.\n\n- Give fast actions preparation and recovery. Anticipation may be tiny, but\n  there should be a legible cause rather than an unexplained teleport.\n- Change position on arcs when physical motion calls for it. Use straight\n  paths for precision, direction or mechanical intent.\n- Match-cut across shared shapes, track a moving object into the next scene,\n  reveal through a meaningful mask, or use a clean cut. Choose transitions\n  because of the relationship between beats, not a desire for variety.\n- Preserve velocity and direction at hand-offs. Avoid accidental jumps in\n  scale, lighting or object identity. Morph only where topology supports it;\n  a designed match-cut is better than an unreadable mesh distortion.\n- Alternate action and rest. Reserve the strongest transformation for the\n  central idea; endless maximum intensity makes everything feel equal.\n- Close intentionally: resolve the motif and hold the final message. Loops\n  need matching start\u002Fend state AND velocity, without a duplicated pause.\n\n## Choose a visual grammar\n\n**Product \u002F brand film:** build around a real benefit and a concrete action.\nUse actual screens where available, isolate what changes, and carry the brand\nmotif into the closing frame. A slow camera move over a static page is supporting\nfootage, not the entire demonstration.\n\n**Kinetic typography:** let words act out meaning through weight, tracking,\ndirection and transformation. Keep a stable reading window; do not rotate,\nblur or scatter every line. Animate a phrase as a unit when word-by-word entry\nwould obstruct comprehension. Reveal timing is not reading time.\n\n**Explainer \u002F data:** choose spatial metaphors that preserve the causal model.\nShow the object before transforming it; maintain labels while relationships\nchange. Reveal axes before values when the scale matters. If narrated, align\nbeats to actual supplied or generated audio timing, not guessed timestamps.\nDo not add unrelated decoration to cover a weak explanation.\n\n**Art \u002F procedural scene:** distinguish a style's structure from surface noise.\nDefine marks, material, palette, composition and one characteristic movement.\nExamples: a woodcut uses cut-line direction and layered ink; a painted night\nuses coherent curved strokes and moving light; paper cutouts use plane depth,\nedge shadows and hinged motion. Seed texture once and move it coherently;\nregenerating every mark each frame causes flicker. Animate elements inside the\nworld, not only the camera between static paintings. Human identity and complex\nanatomy should use suitable supplied\u002Fgenerated assets when tools allow; keep\nsilhouette, palette and lighting consistent. Never pretend those assets exist.\n\n**3D \u002F professional-tool task:** retain the user's existing AE, Blender or\nRemotion project if specified and available. Read its state, edit the smallest\nrelevant scene, and retain editable layers\u002Fkeyframes. A tool-specific pipeline\nis justified by the desired result, not by the name of this skill. Do not make\ninstallation of AE, Blender, a paid provider or a new framework the default.\n\n## Author reliable editable motion\n\nFor a new Open Design film, use timeline-driven HTML with GSAP and optional\nSVG\u002FCanvas. HTML\u002FSVG suit typography, crisp diagrams and UI; Canvas suits dense\nmarks, fields and procedural worlds. Combine them when useful. Preserve an\nexisting supported renderer instead of rebuilding it just to fit this default.\n\nKeep duration, frame size, palette, type scale, easing and scene timings in one\nsmall configuration. Group each scene's elements and motion together. Separate\ncontent\u002Fdata from drawing. Reuse geometry and cached textures; cap offscreen\nwork and particle counts. Keep a scene stable at any requested timestamp.\n\nThe Open Design video composition contract:\n\n```html\n\u003Cdiv id=\"main\" data-composition-id=\"main\" data-start=\"0\"\n     data-duration=\"15\" data-width=\"1920\" data-height=\"1080\" data-poster-time=\"13.5\">\n  \u003C!-- Real scene elements, sized for this stage. -->\n\u003C\u002Fdiv>\n\u003Cscript>\n\u002F\u002F Load GSAP before this block; retain the host's pinned dependency when supplied.\nconst duration = 15;\nconst tl = gsap.timeline({ paused: true });\n\u002F\u002F Define initial states explicitly, then animate scene objects at absolute times.\n\u002F\u002F tl.fromTo(...); tl.to(...); Reading holds occupy real time in the timeline.\nconst clock = { t: 0 };\ntl.to(clock, { t: duration, duration, ease: 'none' }, 0);\nwindow.__timelines = { main: tl };\n\u002F\u002F A procedural layer must draw from clock.t, not increment state each frame.\n\u002F\u002F Video export seeks with timeline callbacks suppressed, so draw from a\n\u002F\u002F per-frame loop rather than from onUpdate alone:\n\u002F\u002F (function render() { drawWorld(clock.t); requestAnimationFrame(render); })();\n\u003C\u002Fscript>\n```\n\nThis is a protocol skeleton, not a finished visual template. Author the real\ncomposition. Root duration, timeline duration, aspect and the brief must agree.\nUse real seconds: the master timeline must keep `timeScale(1)`, no repeat or\nstart delay, and its actual `duration()` must equal `data-duration`. The setter\n`tl.duration(seconds)` changes playback speed; it does NOT add a reading hold.\nUse the full-length clock tween above, and keep all tracks within its duration.\nThe player and renderer reject inconsistent video clocks before export.\n\nFor SVG pop\u002Fscale entrances, establish a shared origin BEFORE the from state.\nAnimate a common group for related shapes (a disk and its shading), or set the\nsame `svgOrigin` in both states. Do not set it only in the destination: GSAP\nsmooth-origin compensation can offset shapes with different bounding boxes.\n\n```js\nfunction popShape(tl, node, cx, cy, at, duration = 0.45) {\n  const svgOrigin = cx + ' ' + cy;\n  tl.fromTo(node, { scale: 0, svgOrigin },\n    { scale: 1, svgOrigin, duration, ease: 'back.out(2)' }, at);\n}\n```\nUse the actual composition id consistently. Register timelines before signalling\nreadiness; all image\u002Ffont dependencies need a known ready state. Keep assets\nlocal when possible and avoid relying on inaccessible remote URLs.\n\nDeterministic motion must survive forward\u002Fbackward seeking: no Date.now-based\nscene state, unseeded randomness, simulation that only works after playing from\nzero, or independent CSS animation competing with the master timeline. Define\npositions and reveals as functions of time, or as seekable timeline tracks.\nNever make visible content depend on timeline callbacks (onUpdate, onComplete);\nthe MP4 exporter seeks with them suppressed.\nAudio-reactive motion needs a precomputed envelope or known beat map when exact\nreplay matters. Never imply that an arbitrary pulse is analysis of the music.\n\nOpen Design scaffolds and embeds shared source playback: open the HTML to\nautomatically loop the film, with no separate player bar. Click the picture to\npause\u002Fresume or unlock audio blocked by browser autoplay. The internal\n`window.__odMotionPlayer` interface retains play\u002Fpause, seek and replay. Preserve its `script[data-od-motion-source-player]`. Do not create\ncompeting controls or start a second playback clock. The renderer sets\n`window.__odMotionRender` before author scripts to disable preview chrome and\nscaling during capture. The scaffold includes pinned GSAP 3.14.2 at\n`.\u002Fgsap.min.js`; preserve and reference that local file. No download is needed. Prefer installed\u002Fsystem fonts with Chinese coverage; an unrequested font\nmust not block delivery. If an optional download fails, use an available font\ninstead of probing more mirrors, installing font tools or creating environments.\nFor an existing standalone source without the host player, put controls outside the\ncomposition and connect them to the same master timeline. Scale the whole stage\nuniformly to fit; do not reflow scene layout when the viewport changes. Controls\nmust not appear in the exported frames. Keep a useful poster when reduced motion\nis requested and let the user explicitly start playback.\n\n## Plan and produce sound for video\n\nFor a video motion brief, decide voice, music and effects separately in the\nexisting Design Spec and beat map. If the film benefits from music or sound\naccents and the user has not requested silence, add suitable sound proactively.\n“No voiceover” disables speech only; it does not mean no music or effects.\nAn explicit silent\u002Fmuted\u002Fno-sound request wins. Choose silence when justified\nby the destination (for example a silent ambient loop), and state that choice.\nThis policy belongs to video motion; do not add sound to ordinary prototypes,\ndocuments, slides or interactive motion unless their brief calls for it.\n\nRecord the audio decision in the ordinary plan. Declare\n`\u003Cmeta name=\"od-motion-audio\" content=\"required\">` for an audible film or\n`content=\"silent\"` for intentional silence. This is composition metadata for\nthe actual exporter, not a model-output planning contract.\nFor `required`, author real local audio assets inside the composition directory:\nuse supplied\u002Flicensed media, the host audio-generation tool when available, or\nan original synthesized instrumental\u002Feffect WAV. Do not invent an asset URL,\ninstall an unrelated audio environment, or substitute a pulsing visual for sound.\nIf required audio production fails, report the blocker instead of delivering\nsilence as complete.\n\nDeclare every track with the renderer's supported timing, for example:\n`\u003Caudio src=\"assets\u002Fmusic.wav\" data-start=\"0\" data-duration=\"15\" data-volume=\"0.3\" preload=\"auto\">\u003C\u002Faudio>`.\nEffects use the same contract with their own start and duration. Keep sources\nlocal and relative, pre-trim tracks, and avoid loop, playback-rate and media-start\nattributes. Keep music below speech and align accents to the actual beat map.\nPreserve the shared source player: it automatically loops picture and sound, and synchronizes audio to play,\npause, seek and replay. Do not start a second audio clock or use Web Audio alone, which is\nnot an exportable track. The renderer mixes these tracks into the MP4.\n\nIn the existing bounded video check, verify source audio follows those controls,\nthat downloaded MP4 contains an audible audio track, and that key sounds occur\nat the authored times. A file extension or an audio tag alone does not prove\nsound. Silent films remain valid; never require audio for other task types.\n\n## Video production and dual delivery\n\nFor video briefs, use Open Design's existing local HyperFrames renderer during\nBuild. It needs no video-generation API key. Do not ask the user to render it\nmanually or run a second renderer. Plan declares `hyperframes-html` as the\nproduction route, editable source as canonical, and MP4 as a required derived\noutput. For interactive briefs use `html` and source only.\n\nUse only the host's `media scaffold`, `media generate`, and `media wait` entry\npoints for this workflow. Do not invoke the HyperFrames CLI directly for init,\npreview, rendering, or skill installation, including through npx. The host\nkeeps scaffolding and preview local and disables HyperFrames CLI telemetry on\nits render subprocess. Do not enable telemetry or bypass that wrapper.\nMotion MP4 export requires the desktop frame renderer for authored-clock\nvalidation; a headless browser override is not a supported substitute.\n\nKeep source and MP4 paths in the existing plan and in the composition's MP4\nlink. On OD Next, declare them through the host's existing required-deliverable\ncontract and preserve its normal planning-to-production continuation. The\nexporter separately checks the actual output path and declared audio policy.\nDo not invent new machine blocks, contract fields, or a motion-specific gate.\n\nApply this delivery guidance only to the user's actual current video-motion\nrequest within the host's authorized task type and scope. Follow the host's\nexisting task-type change rules for a request in another project. A selected\nscenario or loaded helper alone does not authorize creating a film.\nPlan-only requests end with the plan; interactive motion and hover\u002Fscroll\nanimation in a prototype remain runnable HTML. Follow-ups may directly edit an\nexisting film; re-render only when the requested change affects the video.\n\n1. Scaffold a visible source directory with the native shell tool:\n   `\"$OD_NODE_BIN\" \"$OD_BIN\" media scaffold --project \"$OD_PROJECT_ID\" --composition-dir \"motion-source\u002Ffilm\"`.\n   Use a new descriptive directory for a new film; edit the existing source on\n   revisions. Keep `hyperframes.json`, `meta.json`, HTML and local assets there.\n2. Author `motion-source\u002Ffilm\u002Findex.html`. Its composition root must have\n   `data-composition-id=\"main\"`, `data-start=\"0\"`, `data-duration`, `data-width`,\n   `data-height` and `data-fps`. Register the seekable master timeline at\n   `window.__timelines.main`. Use actual GSAP animations, not a placeholder\n   timeline. Keep assets\u002Ffonts local and relative to this source directory.\n   Include `\u003Cmeta name=\"od-motion-output\" content=\"video\">` and\n   `\u003Clink rel=\"alternate\" type=\"video\u002Fmp4\" href=\"..\u002F..\u002Ffilm.mp4\">` in the head.\n   The href must identify the actual planned MP4 inside the project. The\n   interactive equivalent declares `content=\"interactive\"` and needs no MP4.\n   For video, choose a stable, representative moment in your actual timeline\n   and declare its time in seconds as `data-poster-time` on that root. It must\n   satisfy `0 \u003C= time \u003C data-duration`; avoid an empty opening or a transition.\n   Prefer a frame that communicates the product or main idea at thumbnail size.\n   The host validates the source\u002Fvideo clock and dimensions and extracts this\n   exact frame from the finished MP4. Do not generate a separate invented cover,\n   change the video's opening for the cover, or bake preview containers into it.\n3. Render through the host:\n   `\"$OD_NODE_BIN\" \"$OD_BIN\" media generate --project \"$OD_PROJECT_ID\" --surface video --model hyperframes-html --composition-dir \"motion-source\u002Ffilm\" --output \"film.mp4\"`.\n   If it returns a task ID, use `\"$OD_NODE_BIN\" \"$OD_BIN\" media wait \u003Cid>` and wait for success.\n   A queued task, HTML preview or failed command is not a completed film.\n4. Preserve the source and assets, and link BOTH the actual MP4 and the source\n   HTML in the final response using project-relative Markdown links. The file\n   viewer provides preview\u002Fdownload. On later video edits re-render the same\n   linked MP4 so the download matches the current source.\n\nIf the host reports a renderer failure, preserve the editable source and report\nthat blocker truthfully. Never fabricate a download or label HTML-only output\nas a finished video. Only actual user-requested video-motion production, and\nonly when the host Core authorizes it, permits this bounded check:\n\n- During planning, retain factual invariants and exact required copy in the\n  existing Design Spec\u002Fbeat map. An explainer must preserve the causal mechanism\n  and exceptions when shortening subtitles; decorative metaphors are not facts.\n- After the first render, perform one review of the actual source and exported\n  video: check the clock\u002Fdimensions, compare captions against those invariants,\n  and inspect at most three representative frames (opening, key explanation,\n  ending). Check related SVG shapes stay aligned. Use available host\u002Fbrowser\u002F\n  frame tools and actually view the images; source reading alone is not visual\n  evidence. Do not claim a check that tool access did not allow.\n- If that review or the renderer identifies a concrete defect, make at most one\n  targeted repair and re-render; recheck only the affected facts\u002Fframes. If still\n  incorrect or unverifiable, report the limitation instead of certifying it.\n- Do not spawn acceptance agents, score aesthetics, add a separate pipeline\n  stage, or repeat an open-ended polish loop. Interactive motion, prototypes,\n  slides, documents and other tasks keep their existing ship-on-write policy.\n\n## Quality while composing\n\nFor each beat, account for focal point, motion cause, reading time and exit.\nAt a transition, account for both outgoing and incoming states and their overlap.\nAt the end, account for resolution, holding time and replay behavior.\n\nUse these concrete defect-to-decision pairs while building:\n\n| Defect | Better decision |\n| --- | --- |\n| Feels like a slideshow | Carry one object through a meaningful transformation |\n| Everything competes | Choose the lead action; reduce or delay support |\n| No sense of weight | Adjust travel time, acceleration, anticipation and settle |\n| Text is unreadable | Shorten copy only if allowed; increase hold and contrast |\n| Looks generic | Strengthen type, composition and the subject-specific motif |\n| Painterly texture flickers | Seed and cache marks; move a coherent field |\n| Sequence feels monotonous | Vary shot scale and action\u002Fhold rhythm with purpose |\n| Looks busy but says little | Remove decorative motion and show the causal action |\n\nDo not invent a numeric score to certify aesthetics. Report the usable artifact,\nits duration\u002Faspect, and any missing asset, audio or export capability succinctly.\n",{"od":23,"name":5,"triggers":28,"description":7},{"mode":24,"category":25,"featured":26,"example_prompt":27},"utility","animation-motion",-100,"Create a 15-second motion film for a focus timer. Show scattered thoughts converging into one clear task, with expressive typography, a continuous visual motif, and a confident closing frame.",[29,30,31,32,33,34,35],"motion design","motion graphics","视频动效","动态设计","MG动画","kinetic typography","animated explainer","main","3a6721b94dec7506e324023f2855495c9c54d0d2","skills\u002Fmotion-design",0,"https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design","https:\u002F\u002Fopen-design.ai","https:\u002F\u002Fgithub.com\u002Fandremolnar","2026-10-30 01:33:11",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add andremolnar\u002Fopen-open-design --skill motion-design",{"tool":50,"command":51},"bunx","bunx skills add andremolnar\u002Fopen-open-design --skill motion-design",{"tool":53,"command":54},"pnpm","pnpm dlx skills add andremolnar\u002Fopen-open-design --skill motion-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fmotion-design\u002FSKILL.md",true,[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"SOURCES.md","REFERENCE","参考文档",1560,"https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fmotion-design\u002FSOURCES.md",[65,72,79,86,93,102],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7DMPDFNBD52ZP0GNY046Z2A","Beta Skill","Instruction-only fixture skill.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7DMPC4JJ8ENX7VWTMP38Y9C","Alpha Skill","First fixture skill with a runnable demo.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7DMP9J5BX307VWVD67J0BBM","Deck One","A small deck template fixture.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fdesign-templates\u002Fdeck-one\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M7DMP7GNYTFXGK9RDZ2X723P","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M7DMP2WHMNKM0P5BXRYAG8D1","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","MIT","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M7DMP0GVJQ37CGXYQDD20VWS","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwpds\u002FSKILL.md",[],[]]