Embed a Rive animation in an application

Use this skill when a .riv file must ship inside a website, mobile app, desktop app, or game. Read references/runtime-guides.md for platform examples before writing integration code.

Inspect the host project first

1. Identify the framework, package manager, build tool, platform, asset directory, test commands, and existing Rive dependency.
2. Do not replace an existing Rive runtime or upgrade unrelated dependencies without a reason.
3. Inspect the exported file with OpenRive (inspect_riv, openrive info, or the project MCP tools). Record the exact artboard, animation, state-machine, property, and theme names.
4. Copy the .riv into the host project's normal static asset location. Prefer a local, versioned asset over an opaque remote URL.
5. Choose the runtime for the host platform. Use the current official Rive runtime documentation for package names and versions; do not assume an old API is still valid.

Cross-platform rules

1. Detect the host operating system and use its normal package-manager and shell conventions, but keep the workflow itself platform-neutral.
2. Do not require Bash-only commands, Unix permissions, /tmp, Windows drive letters, or hard-coded path separators. Use the host project's path utilities (path.join, Path.Combine, File.path.join, or the platform equivalent).
3. Use forward slashes only for browser URLs, package paths, and .riv paths inside web bundles. Quote filesystem paths with spaces in shell examples.
4. For skills installation on Windows or Linux, npx skills add ... --copy is the portable fallback when symlinks are unavailable. The skill content must not assume that a global agent directory is writable.
5. Treat line endings as host-controlled. Do not compare generated text files byte-for-byte unless the format requires it; .riv binary round-trip checks remain byte-exact.