fixing-motion-performance workflow skill. Use this skill when the user needs Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
fixing-motion-performance workflow skill. Use this skill when the user needs Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/fixing-motion-performance from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses metadata.json plus ORIGIN.md as the provenance anchor for review.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: how to use, common fixes, review guidance, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
adding or changing UI animations (CSS, WAAPI, Motion, rAF, GSAP)
refactoring janky interactions or transitions
implementing scroll-linked motion or reveal-on-scroll
animating layout, filters, masks, gradients, or CSS variables
reviewing components that use will-change, transforms, or measurement
Use when the request clearly matches the imported source intent: Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation....
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
/fixing-motion-performance
Apply these constraints to any UI animation work in this conversation.
/fixing-motion-performance <file>
Review the file against all rules below and report:
violations (quote the exact line or snippet)
why it matters (one short sentence)
a concrete fix (code-level suggestion)
Do not migrate animation libraries unless explicitly requested. Apply rules within the existing stack.
Examples
Example 1: Ask for the upstream workflow directly
Use @fixing-motion-performance to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @fixing-motion-performance against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @fixing-motion-performance for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @fixing-motion-performance using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
priority - category - impact
1 - never patterns - critical
2 - choose the mechanism - critical
3 - measurement - high
4 - scroll - high
5 - paint - medium-high
6 - layers - medium
Imported Operating Notes
Imported: rule categories by priority
priority
category
impact
1
never patterns
critical
2
choose the mechanism
critical
3
measurement
high
4
scroll
high
5
paint
medium-high
6
layers
medium
7
blur and filters
medium
8
view transitions
low
9
tool boundaries
critical
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/fixing-motion-performance, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@20-andruia-niche-intelligence-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@2d-games - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: quick reference
1. never patterns (critical)
do not interleave layout reads and writes in the same frame
do not animate layout continuously on large or meaningful surfaces
do not drive animation from scrollTop, scrollY, or scroll events
no requestAnimationFrame loops without a stop condition
do not mix multiple animation systems that each measure or mutate layout
2. choose the mechanism (critical)
default to transform and opacity for motion
use JS-driven animation only when interaction requires it
paint or layout animation is acceptable only on small, isolated surfaces
one-shot effects are acceptable more often than continuous motion
prefer downgrading technique over removing motion entirely
3. measurement (high)
measure once, then animate via transform or opacity
batch all DOM reads before writes
do not read layout repeatedly during an animation
prefer FLIP-style transitions for layout-like effects
prefer approaches that batch measurement and writes
4. scroll (high)
prefer Scroll or View Timelines for scroll-linked motion when available
use IntersectionObserver for visibility and pausing
do not poll scroll position for animation
pause or stop animations when off-screen
scroll-linked motion must not trigger continuous layout or paint on large surfaces
5. paint (medium-high)
paint-triggering animation is allowed only on small, isolated elements
do not animate paint-heavy properties on large containers
do not animate CSS variables for transform, opacity, or position
do not animate inherited CSS variables
scope animated CSS variables locally and avoid inheritance
6. layers (medium)
compositor motion requires layer promotion, never assume it
use will-change temporarily and surgically
avoid many or large promoted layers
validate layer behavior with tooling when performance matters
7. blur and filters (medium)
keep blur animation small (<=8px)
use blur only for short, one-time effects
never animate blur continuously
never animate blur on large surfaces
prefer opacity and translate before blur
8. view transitions (low)
use view transitions only for navigation-level changes
avoid view transitions for interaction-heavy UI
avoid view transitions when interruption or cancellation is required
treat size changes as potentially layout-triggering
9. tool boundaries (critical)
do not migrate or rewrite animation libraries unless explicitly requested
apply these rules within the existing animation system
never partially migrate APIs or mix styles within the same component
Imported: common fixes
/* layout thrashing: animate transform instead of width *//* before */.panel { transition: width 0.3s; }
/* after */.panel { transition: transform 0.3s; }
/* scroll-linked: use scroll-timeline instead of JS *//* before */ window.addEventListener('scroll', () => el.style.opacity = scrollY / 500)
/* after */.reveal { animation: fade-in linear; animation-timeline: view(); }
// measurement: batch reads before writes (FLIP)// before — layout thrash
el.style.left = el.getBoundingClientRect().left + 10 + 'px';
// after — measure once, animate via transformconst first = el.getBoundingClientRect();
el.classList.add('moved');
const last = el.getBoundingClientRect();
el.style.transform = `translateX(${first.left - last.left}px)`;
requestAnimationFrame(() => { el.style.transition = 'transform 0.3s'; el.style.transform = ''; });
Imported: review guidance
enforce critical rules first (never patterns, tool boundaries)
choose the least expensive rendering work that matches the intent
for any non-default choice, state the constraint that justifies it (surface size, duration, or interaction requirement)
when reviewing, prefer actionable notes and concrete alternatives over theory
Imported: Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
