agentleFS
BintzGavinBintzGavin/helios/skills/design/animated-video-philosophy/SKILL.md

animated-video-philosophy

Skill130 starsChanged 38 days agoApache-2.0View on GitHub

Story-first motion design philosophy for animated video: motion must earn its place; arc (establish, complicate, resolve); show vs tell; shots as units of thought; quiet vs loud motion; Disney principles with restraint; timing heuristics; composition; grammar by medium (product demos, logos, data viz, explainers); technical commitments (deterministic time, scrubbability, refs); cutting discipline; explicit anti-patterns. Use when planning, storyboarding, critiquing, or implementing programmatic or motion-driven video (Helios, Remotion, explainers, loops, UI capture, logo reveals), or when the user asks for motion direction, pacing, or visual-story structure.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Read philosophy.md start to finish before giving creative direction, critiquing a cut, or structuring scenes.

    line 17
  2. Distinctive:

    When reviewing builds, check IX.

    line 22
  3. Distinctive:

    When timing or rhythm feels wrong, use VI (including the ~30 viewings rule) before tuning easing alone.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Animated video philosophy

Read philosophy.md start to finish before giving creative direction, critiquing a cut, or structuring scenes. That file is the verbatim working philosophy.

How to apply it

  • Gate work on the five questions at the end of philosophy.md. If they are not clear, prioritize script and intent over more keyframes.
  • When reviewing builds, check IX. The technical commitments and XI. What I won't do explicitly.
  • When timing or rhythm feels wrong, use VI (including the ~30 viewings rule) before tuning easing alone.

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.