TastefulKit 8 views · 24h
← AI skills

Rive — Interactive Graphics and Runtime Handoff

Plans Rive artboards, state machines and semantic data bindings, with runtime contracts, interruption behavior, reduced-motion checks and developer handoff.

riveinteractive-motiondata-bindingdesign-handoff
View skill source ↗ Repository ↗ Website ↗

10 GitHub stars (repository-wide; checked Nov 4, 2026)

skills.sh installs: not checked View on skills.sh

When to use it

Supply the .riv asset or intended behavior, target runtime/renderer, input methods and accessibility needs. Produces named state graphs, View Model schemas, property directions, integration responsibilities and an evidence-labeled QA checklist. Distinct from CSS/logo animation: focuses on Rive authoring and application-to-animation contracts. Live file editing requires suitable Rive Editor tooling such as Rive MCP. Without it, only instructions and architecture are possible. Exact APIs and renderer support require current official documentation. Preserve references/ and agents/. Prompt-based clients use the separate bundled rive-instructions.md; that is not a second skill. Source documentation reviewed; not installed or runtime-tested. GitHub stars are repository-wide, not skill-specific.

Compatible agents

Codex

Installation

Clone https://github.com/uianimation/rive-skill.git. For a personal Codex skill, copy the complete cloned rive-skill directory to ~/.codex/skills/rive (create the parent directory first); for project scope use .codex/skills/rive. Keep SKILL.md, references/ and agents/ together. Start a new session and invoke `$rive`. The README separately offers rive-instructions.md for prompt-based tools; editing .riv files needs separate Editor tooling.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Nov 4, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.