[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75YYDDZ8568QJZR4AP1P6J5":3,"skill-same:01M75YYDDZ8568QJZR4AP1P6J5":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75YYDDZ8568QJZR4AP1P6J5","design-motion",null,"Design or implement motion for creative work across media, including animation, graphic sequences, interfaces, and interactive pieces. Use when defining timing, movement feel, transitions, or animation briefs.","JoseArron\u002Fskills","JoseArron","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87633971?v=4","01M75YX3KAHAS3QG3VWTE99Q82","okjose","01M75YX3KY032CBX4FDYZVX0AN",2,"MIT","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreative\u002Fdesign-motion\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: design-motion\ndescription: \"Design or implement motion for creative work across media, including animation, graphic sequences, interfaces, and interactive pieces. Use when defining timing, movement feel, transitions, or animation briefs.\"\n---\n\n# Design motion\n\nMake movement express the brief's purpose and intended feeling. Weight, personality, abstraction, and material response are choices for the subject; a mood word becomes useful when it changes timing, pose, or path.\n\n## Read the movement's job\n\nRead selected direction, motion notes, the subject or composition, and interaction when relevant. Identify the movement's purpose, message, timing context, and feeling. Preserve selected movement and unrelated behavior.\n\nUse `ux-flows` for the user's journey or feedback placement; this skill owns how chosen feedback moves. Use `plan-trailer` for shot order, musical structure, and overall pacing. Load the needed entrypoint through the available skill mechanism or read it directly.\n\n## Define observable motion\n\nDescribe key poses and timing, path, acceleration, easing, anticipation, overlap, settling, and holds. Include contact, pivots, deformable regions, and anchors. Specify durations or curves as design parameters unless measured from a source.\n\n- Match deformation to the material. Squash, stretch, wobble, smear, and rigidity are options, not defaults.\n- For recognizable subjects, preserve defining features across extreme poses. For abstract sequences, preserve the intended geometry and compositional relationships.\n- Distinguish authored animation from simulation. For interactive motion, test the requested input, interruption, and final state. For a physical simulation, test relevant contact, deformation, release, and rest behavior.\n- For graphic motion, define hierarchy: what moves first, what the eye follows, and what stays readable. Avoid identical bounce on every layer.\n- For a loop, inspect the seam. For a transition, define entry, exit, interruption, and final state.\n- Where interface movement is optional, respect reduced-motion settings and preserve state information without the effect.\n\n## Make it reviewable\n\nDeliver a timing sheet, keyframe brief, generator-ready motion prompt, or runnable preview according to the request. For code, expose the parameters that affect feel. A still image does not prove motion.\n\nInspect at normal speed and relevant extremes. Check readability, contact, overshoot, settling, and interruptions. Separate observed behavior from planned behavior. Keep comparison runs identifiable so rejected movement does not become the default.\n\nFor export, record duration, frame rate, dimensions, alpha\u002Fbackground, loop convention, and state names as needed. For sprites, include frame order, pivots, and atlas layout. Carry selected rules into the contract or linked motion note; reusable sets belong in `build-asset-library`.\n","# Design motion\n\nMake movement express the brief's purpose and intended feeling. Weight, personality, abstraction, and material response are choices for the subject; a mood word becomes useful when it changes timing, pose, or path.\n\n## Read the movement's job\n\nRead selected direction, motion notes, the subject or composition, and interaction when relevant. Identify the movement's purpose, message, timing context, and feeling. Preserve selected movement and unrelated behavior.\n\nUse `ux-flows` for the user's journey or feedback placement; this skill owns how chosen feedback moves. Use `plan-trailer` for shot order, musical structure, and overall pacing. Load the needed entrypoint through the available skill mechanism or read it directly.\n\n## Define observable motion\n\nDescribe key poses and timing, path, acceleration, easing, anticipation, overlap, settling, and holds. Include contact, pivots, deformable regions, and anchors. Specify durations or curves as design parameters unless measured from a source.\n\n- Match deformation to the material. Squash, stretch, wobble, smear, and rigidity are options, not defaults.\n- For recognizable subjects, preserve defining features across extreme poses. For abstract sequences, preserve the intended geometry and compositional relationships.\n- Distinguish authored animation from simulation. For interactive motion, test the requested input, interruption, and final state. For a physical simulation, test relevant contact, deformation, release, and rest behavior.\n- For graphic motion, define hierarchy: what moves first, what the eye follows, and what stays readable. Avoid identical bounce on every layer.\n- For a loop, inspect the seam. For a transition, define entry, exit, interruption, and final state.\n- Where interface movement is optional, respect reduced-motion settings and preserve state information without the effect.\n\n## Make it reviewable\n\nDeliver a timing sheet, keyframe brief, generator-ready motion prompt, or runnable preview according to the request. For code, expose the parameters that affect feel. A still image does not prove motion.\n\nInspect at normal speed and relevant extremes. Check readability, contact, overshoot, settling, and interruptions. Separate observed behavior from planned behavior. Keep comparison runs identifiable so rejected movement does not become the default.\n\nFor export, record duration, frame rate, dimensions, alpha\u002Fbackground, loop convention, and state names as needed. For sprites, include frame order, pivots, and atlas layout. Carry selected rules into the contract or linked motion note; reusable sets belong in `build-asset-library`.\n",{"name":5,"description":7},"main","cb49d66200006e1d66bc1a8c416862b3b935c491","skills\u002Fcreative\u002Fdesign-motion",0,"https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills","https:\u002F\u002Fgithub.com\u002FJoseArron","2026-10-11 15:51:18",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add JoseArron\u002Fskills --skill design-motion",{"tool":37,"command":38},"bunx","bunx skills add JoseArron\u002Fskills --skill design-motion",{"tool":40,"command":41},"pnpm","pnpm dlx skills add JoseArron\u002Fskills --skill design-motion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreative\u002Fdesign-motion\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",112,"https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreative\u002Fdesign-motion\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M75Z1R3CAY688TG5NMBNZK28","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworking-with-skills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M75Z1P4SQQ2CSAGE9XD57GHZ","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworking-with-skills\u002Fusing-superpowers\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M75Z1K7X70CQ3DY038Q2Y37P","resync-upstream-skills","Resync a selectively derived skills repository with its recorded upstream sources. Use when the user wants to pull upstream skill releases, reconcile renamed or changed skills, refresh third-party attribution, or audit whether local adaptations have drifted.","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworking-with-skills\u002Fresync-upstream-skills\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M75Z1G8CEVXMY8QENAKCT9AC","find-skills","Helps users discover and install agent skills when they ask questions like \"how do I do X\", \"find a skill for X\", \"is there a skill that can...\", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworking-with-skills\u002Ffind-skills\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M75Z1E0RSRDZJ2F15YQ2Q6G2","ux-review","Evaluate a built screen or flow against UX heuristics and report what to fix — each finding with a severity and a concrete fix. Use to review or audit a UI's usability, before shipping a flow, or to turn \"this feels off\" into specific, rankable problems. The UX counterpart to \u002Fcode-review.","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fux\u002Fux-review\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M75Z1A7E4X45K9MEERGCY7D4","ux-flows","Design and implement app screens and user flows with calm, user-first UX — obvious CTAs, feedback at the point of action, thumb-zone layout, and domain-modularized components. Use when the user asks to build or polish UI\u002FUX, design a user flow, make a screen \"feel\" right, or mentions effortless\u002Fcalm design, confirmations, error states, or empty states.","https:\u002F\u002Fgithub.com\u002FJoseArron\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fux\u002Fux-flows\u002FSKILL.md",[],[]]