agentleFS
Sign inStart free
soilmasssoilmass/motion-design-agent/skills/lottie/SKILL.md

lottie

Skill7 starsChanged 10 months agoMITView on GitHub

Lottie animation format specification and usage. Use when exporting animations as Lottie JSON, working with dotLottie packages, or understanding Lottie capabilities and limitations. References LAC Lottie Spec v1.0 and dotLottie v2.0.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use waapi, three and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • anton-abyzovSkill

    waapi

    Web Animations API adapter patterns for HyperFrames. Use when authoring element.animate() motion, Animation currentTime seeking, document.getAnimations(), KeyframeEffect timing, fill modes, or native browser animations that must render deterministically in HyperFrames.

    Also in 5 projects that use this

  • anton-abyzovSkill

    three

    Three.js and WebGL adapter patterns for HyperFrames. Use when creating deterministic Three.js scenes, WebGL canvas layers, AnimationMixer timelines, camera motion, shader-driven visuals, or canvas renders that respond to HyperFrames hf-seek events.

    Also in 5 projects that use this

  • FldicoahkiinSkill

    contribute-catalog

    Author a new HyperFrames registry block (caption style, VFX block, transition, lower third) or component (text effect, overlay, snippet) and ship it as an upstream PR to the hyperframes repo. Use ONLY when the user wants to CONTRIBUTE to the public catalog — for in-project caption/transition authoring use the `hyperframes` skill, for installing existing registry items use the `hyperframes-registry` skill.

    Also in 3 projects that use this

  • software-mansion-labsSkill

    typegpu

    TypeGPU is type-safe WebGPU in TypeScript. Use whenever the user writes, debugs, or designs TypeGPU code: 'use gpu' shader functions, tgpu.fn, buffers, textures, bind groups, compute and render pipelines, command encoders, render passes, render bundles, vertex layouts, slots, accessors, @typegpu/react hooks (useRoot, useFrame, useUniform), React Native worklet rendering, and any TypeGPU API. Shader logic and CPU-side resources are tightly coupled - handle both sides here even if the user only mentions one (e.g. "how do I write a shader", "how do I create a buffer"). Trigger on any mention of typegpu, tgpu, "use gpu", TypedGPU, or WebGPU code written using TypeGPU's schema API (d.*, tgpu.*, std.*). Do NOT trigger for raw WebGPU (using GPUDevice/GPURenderPipeline directly without tgpu), WGSL-only questions, Three.js, Babylon.js, or WebGL.

    Also in 3 projects that use this

  • freshtechbroSkill

    animejs

    Versatile JavaScript animation engine for DOM, CSS, SVG, and JavaScript objects. Use when creating timeline-based animations, stagger effects, SVG morphing, keyframe sequences, or complex choreographed animations. Triggers on tasks involving Anime.js, timeline animations, staggered sequences, SVG path animations, morphing, or multi-step animation choreography. Alternative to GSAP for SVG-heavy animations and React-independent projects.

    Also in 6 projects that use this

  • LangChainSkill

    remotion-to-hyperframes

    Port an existing Remotion (React) composition''s source to HyperFrames HTML. Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source — one-way, Remotion-only. A passing Remotion mention, reference-only code, or "make something like my Remotion video" is a fresh build (/general-video). Unclear → /hyperframes.

    Also in 5 projects that use this

  • +2 more from anton-abyzov

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No native interactivity (requires external code)

    line 38
  2. Distinctive:

    No state machines (use Rive for that)

    line 40

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Lottie Specification

Industry-standard vector animation format.

Standards Reference

StandardAuthorityVersion
Lottie SpecLinux Foundation LACv1.0 (2024)
dotLottieLottieFilesv2.0
IANA RegistrationIANAMIME: video/lottie+json

Format Details

File Extension: .json (legacy), .lot (IANA registered)
MIME Type: video/lottie+json
Compression: None (JSON), gzip optional

Capabilities

  • Vector graphics (shapes, paths, masks)
  • Keyframe animation
  • Easing curves (cubic bezier)
  • Layer compositions
  • Text layers
  • Image assets (embedded or external)
  • Expressions (limited)

Limitations

  • No native interactivity (requires external code)
  • Limited After Effects feature support
  • No state machines (use Rive for that)
  • Some effects not supported (3D, certain blurs)

Creation Tools

ToolExport Method
After EffectsBodymovin plugin
LottieFiles EditorNative export
LottielabNative export
FigmaPlugins (LottieFiles, Phase)
RiveExport option

dotLottie v2.0 Structure

.lottie (ZIP archive)
├── manifest.json          # Required
├── animations/
│   ├── animation_1.json
│   └── animation_2.json
├── images/                # Optional
└── themes/                # v2.0

When to Use Lottie vs Rive

Use CaseLottieRive
Pre-designed playbackBestGood
Interactive elementsLimitedBest
After Effects workflowBestManual
File size priorityGoodBest (10-15x smaller)
State machinesNoBuilt-in
Cross-platformExcellentGood

Implementation

Web (lottie-web)

import lottie from 'lottie-web';

lottie.loadAnimation({
  container: document.getElementById('container'),
  renderer: 'svg',
  loop: true,
  autoplay: true,
  path: 'animation.json'
});

React

import Lottie from 'lottie-react';
import animationData from './animation.json';

<Lottie animationData={animationData} loop={true} />

Remotion

import { Lottie } from '@remotion/lottie';
import animationData from './animation.json';

<Lottie animationData={animationData} />

See references/lottie-spec.md for full specification details. See references/dotlottie-spec.md for packaging format. See references/supported-features.md for AE compatibility matrix.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free