pose-library-design

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/X-manist/Cohmira --skill pose-library-design-x-manist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pose-library-design
Source: https://github.com/X-manist/Cohmira/tree/main/src/builtin-plugins/openmontage/.agents/skills/pose-library-design
Command: npx skills add https://github.com/X-manist/Cohmira --skill pose-library-design-x-manist

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 acting and duplicated rig data. ## Core Features & Use Cases - Pose Taxonomy: Defines standard pose categories covering neutral, attention, emotion, action, and mouth states so every required expression has a named pose. - Acting Pattern: Applies the anticipation -> action -> hold -> settle timing pattern so character acting stays readable instead of continuously animating every part. - Structured Pose Data: Provides a JSON pose data pattern where poses name only changed parts and inherit defaults from the rig, with hold frames and transition easing. - 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 or determined, and timed hold frames for each beat. ## Quick Start Use the pose-library-design skill to create a pose library JSON for a 2D character with emotion poses, a walk cycle, and timed hold frames.

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 2D character pose library for animation?

Define poses across five categories: neutral, attention, emotion, action, and mouth states. Each pose is a JSON object naming only the parts that change from rig defaults, with hold_frames and a transition easing such as back.out.

What is the anticipation action hold settle pattern in animation?

It is a timed pose sequence where a character prepares, performs, holds, and settles into each action. Holding poses instead of continuously animating every part keeps the acting readable for viewers.

How do I structure walk cycle poses for a 2D rig?

Reused walk cycles need at least contact and passing poses, defined as walk_contact and walk_passing in the action category. Each cycle pose references only the changed parts so rig defaults fill in the rest.

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 between the pose states defined in the JSON data.

Why should poses only name changed parts instead of the full rig?

Naming only changed parts keeps pose data small and avoids conflicts, since unchanged parts inherit defaults from the rig. This makes poses composable and easier to maintain across a library.