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/transition-authoring.md
View on GitHub# Constrained transition authoring
The runtime schema is `transitionPlanSchema` exported by Motion Debugger. Serialize `schemaVersion: 1`, an explicit `browser-monotonic-ms` or `controlled-preview-ms` clock, stable logical actor IDs, DOM/SVG selectors or owned Three object/camera IDs, source locations and protected visual attributes. Projected screen positions use CSS pixels; orientation uses radians. World/parent positions use declared scene units and must be projected before pixel acceptance checks. Every beat has a trigger, purpose, from/to pose, acyclic `after` dependencies, duration and overlap. App states can still cycle open/close/reopen.
`inputPolicy` declares latest-input wins. Retargeting carries position and velocity. Direct scrub and intentional cuts carry none and exclude continuity checks. Acceptance includes useful completion, forbidden visible errors, reduced motion and per-actor destination tolerances, response/settling bounds and required travel. A stationary canvas is not actor evidence. Save permitted source files, protected files and bounded editable parameter names with the plan.
The capture recipe supplies the executable side of that intent. Use `intent: {schemaVersion:1, beats:[{beatId,actionIndexes}]}` to bind each relevant plan beat to concrete runner actions. Review evaluates every mapped epoch, bounds response search at the next epoch and reports expired deadlines, genuine supersession, already-valid poses and missing observation separately. Do not rely on free-text button labels. For actor destinations, omit `mode` only for the conservative legacy terminal-through-capture rule; otherwise use `mode:"terminal"` or `mode:"waypoint"` with `afterActionIndex` and a later `holdUntilActionIndex` for a waypoint.
DOM/SVG orientation contracts use wrapped Z radians and require complete ordered finite phase coverage, including the phase endpoints and actual read spacing. Screen-anchor contracts pair two separately registered DOM/SVG actors one-to-one in the same observed frame with bounded skew; they cannot reuse sparse anchor samples or consume samples outside the declared phase. Scene-published orientation/position remains annotation-only until independently checked in native pixels.
Use `createDOMBinding`, `createSVGBinding` or `createThreeBinding` on original objects. Resolve relative DOM positions with `begin()` at transition start. Invalidate on viewport/layout/scene changes and rebind before advancing. Three bindings own no renderer, camera or geometry; they write parent-local transforms in the existing render loop. Consumers explicitly project world destinations and supply custom material mappings when needed.
`createPersistentHandoff` retargets the existing spring channels without resets. `createStagedDecomposition` accepts editable beat targets and relative phase overlap. `createDragReleaseSettling` distinguishes direct pointer seeking from release retargeting. Advance controllers using native elapsed seconds from the consumer's existing renderer. Initialize the elapsed clock from the first native frame callback (zero initial delta); an earlier frame timestamp can precede performance.now() read during module setup. If the consumer stops its render loop while paused, reset that elapsed baseline when resuming so paused wall time is not integrated. All retain pause, replay and meaningful reduced-motion targets. Dispose controllers without disposing consumer objects.
Before normal coding edits, call `snapshotProtectedDesign(projectRoot, plan.edits.protectedFiles)` or freeze equivalent exact SHA-256 hashes. Verify these bytes after every candidate. Protect assets, layout, copy, materials and interactions unless explicitly permitted. Keep the current candidate, one minimal revision and optional alternative staging: at most three total under the same budget. Rendering, reviews, tool calls, decoding and failed attempts all count.
Execute the same short native journey and meaningful contracts for each candidate. Reject failed/unverified function or changed protected design first. Keep motion meaning, response, trackability and visual preference as separate judgments; cite actual delivered native capture/event/frame evidence. `selectMotionCandidate` validates bounds, measured costs and citation correspondence; it is a nomination guard, not an aesthetic oracle or proof that a model perceived the frames. Critic nominations may abstain and require calibration against blinded humans before serving as the main selector. Pose previews cannot support timing/performance claims.
Create a recoverable `createVerifiedMotionCheckpoint` only for a functional native-verified candidate with unchanged protected hashes. It retains exact authorized source bytes, plan/bindings, evidence IDs and hashes. Restore through normal host editing tools if later revisions fail. Retain every attempt and stop within the existing two-repair bound. Save successful app-specific configurations and regression journeys, with why they helped and which constraints passed.
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 |