pose-library-design

Design reusable 2D character pose libraries, action cycles, and expression states for data-driven animation.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/zamansepeti43/c-rak-agent --skill pose-library-design-zamansepeti43
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pose-library-design
Source: https://github.com/zamansepeti43/c-rak-agent/tree/main/video-engine/.agents/skills/pose-library-design
Command: npx skills add https://github.com/zamansepeti43/c-rak-agent --skill pose-library-design-zamansepeti43

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Animators and developers building data-driven 2D character animation often lack a consistent structure for defining poses, expressions, and action cycles, leading to unreadable motion and duplicated rig data. ## Core Features & Use Cases - Pose Taxonomy: Organizes poses into Neutral, Attention, Emotion, Action, and Mouth categories so every required state is covered. - Acting Pattern: Applies the anticipation -> action -> hold -> settle timing pattern with hold frames to keep acting readable instead of continuously animating every part. - Pose Data Pattern: Defines a JSON schema where poses name only changed parts and inherit defaults from the rig, with hold_frames and transition easing such as back.out. - Use Case: When producing a pose_library artifact for a Remotion or GSAP character animation, use this Skill to define walk contact and passing poses, emotion states like surprised, and mouth shapes for phoneme-ish lip sync. ## Quick Start Use the pose-library-design skill to create a pose_library JSON for a 2D character with idle, walk cycle, and happy and surprised expressions.

Frequently Asked Questions about pose-library-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a reusable 2D character pose library?

Organize poses into Neutral, Attention, Emotion, Action, and Mouth categories, then define each pose as JSON naming only the parts that change from rig defaults. Include hold_frames and a transition easing so sequences stay readable.

How to structure walk cycle poses for data-driven animation?

Define walk_contact and walk_passing poses as the core of the cycle and reuse them across loops. The quality checklist requires that reused cycles always include contact and passing poses so the gait reads correctly.

Can I use GSAP or Remotion with a JSON pose library?

Yes. GSAP timelines sequence multi-step poses, while Remotion interpolate and spring functions handle frame-based transitions and natural motion. The pose JSON transition field maps to easings like back.out.

Why does my character animation look jittery or over-animated?

Continuously animating every part removes readability. Use the anticipation -> action -> hold -> settle pattern and hold poses for a set number of frames so the audience can register each action.

What are the limitations of a pose-only animation approach?

Pose libraries rely on rig defaults for unchanged parts, so they cannot express fully freeform motion. Complex continuous movement still requires custom interpolation beyond discrete pose states.