Skip to content
Back to skills

Ztx14 Curated Animation Ownership Boundary

ASecurity

Prevent conflicting animation engines by assigning each animated SVG/DOM property and state transition to one owner.

  • 14 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
designreactspringapiperformance

Works with

  • api

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add Realjustawall/Perfect-AI --skill ztx14-curated-animation-ownership-boundary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ztx14 Curated Animation Ownership Boundary?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ztx14 Curated Animation Ownership Boundary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/realjustawall-ztx14-curated-animation-ownership-boundary/badge)](https://www.skillsdirectory.com/skills/realjustawall-ztx14-curated-animation-ownership-boundary)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ztx14-curated-animation-ownership-boundary
description: Prevent conflicting animation engines by assigning each animated SVG/DOM property and state transition to one owner.
---

# Keep one owner for every animated property

> Curated implementation skill. Inspect the installed project and actual component source before changing behavior. Do not assume latest APIs are installed. Preserve unrelated files and existing component ownership.

## Core rule
For each element, list animated properties and their owner before editing: Isometric engine, CSS, Motion, GSAP, Rive, or application state. A property must not be continuously written by two engines.

## Workflow
1. Inspect the installed component and `lib/isometric/` source. The site documents an engine with projection, mesh/picking, springs, and a shared animation loop.
2. Create a short ownership table, e.g. `mesh coordinates → Isometric`, `button hover scale → CSS or Motion`, `long scroll timeline → GSAP`, `authored mascot state machine → Rive`.
3. Use the existing Isometric engine for its figures' pointer-to-geometry response. Add Motion only for adjacent DOM/UI behavior or a standalone overlay that the Isometric engine does not own.
4. Never animate the same `transform`, SVG path, point list, or inline style through both a React render and an imperative loop. If a library is already bound to that property, route new targets through its API.
5. Document unmount cleanup and transition interruption rules for imperative owners.

## Acceptance criteria
- One deterministic owner per animated property.
- No visual jitter from competing transforms or repeated state writes.
- Interaction still works after re-entry, interruption, resize, and unmount.

## Primary references
- [isometric](https://isometric.buildlab.in/llms.txt)
- [motion-spring](https://motion.dev/docs/react-use-spring)
- [react-effect](https://react.dev/reference/react/useEffect)
- [web-animation-performance](https://web.dev/articles/animations-guide)

## Completion evidence
- State what was inspected, what changed, and which checks actually ran. Never report unrun tests or unverified browser behavior as passing.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.