Claude Cursor Skill

configure-animation

Use before playing, blending, or retargeting GLB animation clips in PlayCanvas, or when diagnosing T-pose, frozen playback, or binding failures.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download playcanvas-skills-skills_configure-animation-8fd2b26.zip · 3 KB

Install

skills CLI npx skills add https://github.com/playcanvas/skills/tree/main/skills/configure-animation
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install playcanvas-skills@llmmart
Git git clone https://github.com/playcanvas/skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole playcanvas/skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Animation setup

Get clip and joint names from inspect-glb; never guess them.

  • For one clip, use the surface's simple playback path. For blending, transitions, or events, adapt an AnimStateGraph from an official animation example with find-examples.
  • Put the anim component on or above the rendered skinned hierarchy, not on a separate pivot.
  • Clamp every 1D blend parameter to its first and last child points. The Engine does not; values outside the span zero every weight and can make synced speeds non-finite, freezing the pose.
  • Retarget only when each source animationTargets path, minus its .translation, .rotation, .scale, or .weights suffix, matches a destination nodePaths entry below the model root. Equal joint counts or similar names are not enough.
  • Scale a wrapper, never skinned bones.

Prove playback

An active state or advancing state time does not prove motion. Sample two non-root joints over several rendered frames (inspect-runtime) at idle and at both ends of each blend tree. Zero joint motion means a binding, playback, or blend-weight failure.

Diagnose

  • T-pose: no clip assigned, target paths differ, or the anim component sits outside the rendered hierarchy.
  • Frozen pose: an unclamped blend input or a non-finite speed.
  • Partial or exploded motion: incompatible rigs.

Read only the reference matching the code: direct Engine, React, or Web Components.

Files (skills)
  • references
    • direct-engine.md 1.3 KB
      Loading…
    • react.md 1.3 KB
      Loading…
    • web-components.md 957 B
      Loading…
  • SKILL.md 1.7 KB
    ---
    name: configure-animation
    description: Use before playing, blending, or retargeting GLB animation clips in PlayCanvas, or when diagnosing T-pose, frozen playback, or binding failures.
    ---
    
    # Animation setup
    
    Get clip and joint names from `inspect-glb`; never guess them.
    
    - For one clip, use the surface's simple playback path. For blending, transitions, or events, adapt
      an `AnimStateGraph` from an official animation example with `find-examples`.
    - Put the `anim` component on or above the rendered skinned hierarchy, not on a separate pivot.
    - Clamp every 1D blend parameter to its first and last child points. The Engine does not; values
      outside the span zero every weight and can make synced speeds non-finite, freezing the pose.
    - Retarget only when each source `animationTargets` path, minus its `.translation`, `.rotation`,
      `.scale`, or `.weights` suffix, matches a destination `nodePaths` entry below the model root.
      Equal joint counts or similar names are not enough.
    - Scale a wrapper, never skinned bones.
    
    ## Prove playback
    
    An active state or advancing state time does not prove motion. Sample two non-root joints over
    several rendered frames (`inspect-runtime`) at idle and at both ends of each blend tree. Zero joint motion means a
    binding, playback, or blend-weight failure.
    
    ## Diagnose
    
    - T-pose: no clip assigned, target paths differ, or the anim component sits outside the rendered
      hierarchy.
    - Frozen pose: an unclamped blend input or a non-finite speed.
    - Partial or exploded motion: incompatible rigs.
    
    Read only the reference matching the code: [direct Engine](references/direct-engine.md),
    [React](references/react.md), or [Web Components](references/web-components.md).
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.