ShadowKingYT444/motion-debugger / plugin/motion-debugger/skills/motion
motion
VerifiedCreate and verify polished website motion from a normal website or app prompt. Use when the user tags Motion Debugger or asks for expressive animations, spatial scenes, scroll choreography or refined microinteractions. Includes runnable spring, scroll chapter, articulated colony, task handoff, elapsed task sequence, kinetic identity field and modal drawer recipes, then actual browser evidence.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| agents/openai.yaml | config | 269 B |
| recipes/colony-scene.mjs | script | 12.9 KB |
| recipes/drawer.mjs | script | 3.5 KB |
| recipes/elapsed-sequence.mjs | script | 6.2 KB |
| recipes/kinetic-field.mjs | script | 12.6 KB |
| recipes/scene-actor-adapter.mjs | script | 3.2 KB |
| recipes/scroll-chapters.mjs | script | 2.1 KB |
| recipes/spring.mjs | script | 3.1 KB |
| recipes/task-handoff.mjs | script | 2.5 KB |
| recipes/transition-bindings.mjs | script | 6.4 KB |
| recipes/transition-patterns.mjs | script | 7.1 KB |
| references/evidence.md | markdown | 5.5 KB |
| references/transition-authoring.md | markdown | 4.9 KB |
| references/usage.md | markdown | 8.3 KB |
references/evidence.md
View on GitHub# Evidence for creation and refinement
Before capture, write the actual product journey and its positive result, deadlines, error states and interruption cases. Example for a colony launch page: open the task panel, select a worker, switch worker while its token is traveling, run the task, and verify that the visible result corresponds to the selected worker. Verify the ordinary CTA and links independently. A looping ant scene is not task completion.
Capture a trusted credential-free local development page at desktop and narrow widths. Use a unique target and the same viewport, interactions, duration, reduced-motion preference and explicit contracts across before/after runs. Include the delayed end, not only the initial reveal. Keep enough frames around reversals and final state. The tool returns a capture ID and stores real browser footage; do not synthesize traces or substitute scene counters for measurements.
1. `motion_capture({recipe})` records the specified interaction.
2. `motion_inspect({captureId,fromMs,toMs,includeSamples:true})` reveals the event/sample context around a finding.
3. `motion_frames({captureId,timestampsMs})` returns recorded native images; look at them, including intermediate states.
4. After a source repair, rerun the unchanged recipe and use `motion_compare({beforeId,afterId})`; inspect the after frames as well.
Obtain tool schema and current limits from the connected server; do not invent arguments or shorten a journey to fit the default capture duration. Each wait is at most 4000ms, all waits total at most 10000ms, and the entire interaction is at most 12000ms. Leave room for actual clicks and settling. `contract.outcomes.timeoutMs` is a deadline measured from capture START, including actions; it is not an extra timeout after the final wait. Omit it to use the capture duration. Positive checks run after the actions before that deadline; forbidden visible errors are observed throughout. For example, use a 12000ms capture with three waits of 3000ms for a nine-second task, with no shorter outcome timeout.
The ordinary browser remains available for outcome assertions, keyboard journeys, screenshots and long interactions. Capture tools are observation tools; the host coding agent writes source and tests. Do not loosen budgets after seeing a failure.
For internal actors, bind the actual moving DOM/SVG element rather than a static scene container. Orientation uses radians and needs finite ordered browser reads at every sample through both declared phase boundaries; a stale early transform cannot establish the terminal pose. A screen anchor registers both actors and needs one-to-one same-frame geometry with bounded read skew. App-published scene poses are annotations, not independent painted evidence. When any requested feature is unsupported, annotation-only or insufficient, leave it unverified rather than converting it into a pass.
Map review beats to executable recipe actions with `intent.schemaVersion: 1` and action indexes. This prevents button labels or prose from being guessed as input intent and causes every mapped epoch to be evaluated. Distinguish a destination that must remain through capture end from a waypoint that may depart after a later mapped action. Legacy destinations with no mode remain conservatively terminal.
```json
{
"actions": [{"action":"click","selector":"#advance"},{"action":"click","selector":"#next"}],
"intent": {"schemaVersion":1,"beats":[{"beatId":"advance-part","actionIndexes":[0]}]},
"actors": [{
"id":"part","kind":"dom","selector":"[data-motion-id=part]",
"acceptance": {
"destination":{"x":240,"y":120,"tolerancePx":3,"deadlineMs":900,"settleMs":50,"mode":"waypoint","afterActionIndex":0,"holdUntilActionIndex":1},
"orientation":{"axis":"z","unit":"radian","maxStepAt60HzRad":0.25,"phase":{"startMs":100,"endMs":900}}
}
}]
}
```
These are generic contracts, not proof that an unlabeled internal element corresponds to product intent. Keep the identical recipe, actors, phases and budgets for before/after comparison.
The interaction deadline also applies to exploratory captures without outcomes. Overlong waits or blocked inputs retain incomplete evidence rather than a completed report. `recipeWarnings` identifies known wait/drag schedules that exhaust the budget; leave additional room for real input. For held scrubbing, use `action:"drag"`, a unique selector, 2–12 normalized `{x,y}` waypoints and 100–2000ms duration. Every reversal is visited while the native pointer stays down, then it is released even on failure. Match the recorded range to its actual thumb geometry; observe release state separately from any playback that resumes afterward.
Canvas movement needs footage of the canvas contents. A static DOM box can contain rich motion or a stalled renderer. Frame cadence, motion continuity, meaningful final state and visual composition are separate observations. Static screenshots cannot establish smoothness; sparse frames and dropped/insufficient footage are inconclusive. Report the exact source revision, runtime, viewport, captures and checks. Distinguish protocol/tool connectivity from an actual fresh agent-host invocation.
For a matched A/B, preserve the same brief, model, assets and comparable effort; both agents retain ordinary browser tools. Log the extra plugin guidance and tool use in the assisted condition. Preserve failures and incomplete recordings. A recipe demonstration or handwritten repair proves the artifact behaves as inspected; it does not establish general coding-agent improvement.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |