agentleFS
gaia-researchgaia-research/gaia-skill-heaven/.claude/skills/lucy-rive/SKILL.md

lucy-rive

Skill4 starsChanged 12 days agoMITView on GitHub

Build, verify and review Lucy's live Rive character for a Skill Heaven state gate (Heaven, Hell, Zero, Ultra) — gold master to script-free .riv, acceptance viewer, gate evidence, Rive cloud file, owner visual gate. Pointer to the canonical skill in gaia-research/lucy. Triggers on "/lucy-rive", "Lucy rig", "Lucy Alive", "Rive Lucy", "next Lucy gate", "rig Hell/Zero/Ultra".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If ~/lucy is missing: gh repo clone gaia-research/lucy ~/lucy.

    line 15
  2. Very specific:

    Never advance to the next state before the owner's visual approval of the current one is recorded (gaia-skill-heaven#153).

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Lucy · Rive character — pointer

The canonical skill lives with the character source, in gaia-research/lucy at .agents/skills/lucy-rive/SKILL.md (local checkout: ~/lucy). Read it in full before any Lucy rig work — it carries the gate order, canon per state, toolchain facts (Rive CLI, Editor MCP limits, cloud file ids), the pipeline commands, and the lessons that each already cost a build.

If ~/lucy is missing: gh repo clone gaia-research/lucy ~/lucy.

What stays in this repo (the consumer side):

  • Product state + timing: packages/site/src/lucy-scene/scene.ts (SceneState, SCENE_TIMING), lifecycle useSceneLifecycle.ts.
  • The character seam and semantic contract: packages/site/src/lucy-scene/LucyLive.tsx (LucyCharacter).
  • The finished atmosphere (do not change it to suit the rig): packages/site/src/lucy-scene/atmosphere/; review switches ?lucy=off, ?atmo=off.
  • Glass wings are a hero effect layer, not character (src/assets/hero-commission/v01/, WING_CONFIG* in variations/hero/useHeroEngine.ts).
  • Raster production rules: .agents/skills/lucy-image-production/SKILL.md.

Never advance to the next state before the owner's visual approval of the current one is recorded (gaia-skill-heaven#153).

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.