build-accessible-motion-systems

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Build Accessible Motion Systems

## When to use

- Adding a consistent motion language to a game interface, site, or application.
- Replacing scattered animation values with governed tokens.
- Reviewing motion for accessibility, lifecycle, or performance defects.

## Workflow

1. Define the user purpose for each motion category: orientation, hierarchy, continuity, feedback, or emphasis.
2. Create bounded duration, easing, distance, delay, and stagger tokens.
3. Implement a small primitive set before composing sequences.
4. Specify interruption, reversal, repeated activation, focus, visibility, and route-change behavior.
5. Provide reduced-motion behavior that preserves state comprehension without decorative movement.
6. Measure animation cost and dispose timers, observers, listeners, frames, and rendering resources.
7. For games, resolve compatible UI/animation feature skills through `resolve-skill.sh`. Assign simulation or presentation clock ownership, bounded overlap, cancellation handles, and scene/pause/focus behavior. Reduced motion must retain truthful state, focus, and essential cues even when camera shake or transition movement is removed.

## Output

- A motion token table and primitive inventory.
- Choreography rules with responsive and reduced-motion behavior.
- Implementation, cleanup, performance, and test acceptance criteria.

## Guardrails

- For browser interfaces, prefer transform or opacity when they express the result without repeated layout work. Verify the selected engine's own layout and rendering costs for native UI.
- Do not make essential content depend on an animation completing.
- Do not add continuous movement without a user benefit and pause strategy.
- Do not equate reduced motion with reduced haptic intensity: expose the relevant preferences separately and use `build-gameplay-runtime` for actual tactile output.

From TimothyMeadows/OpenCaw, MIT.

More from TimothyMeadows/OpenCaw