agentleFS
JiamingShi-JsPhysJiamingShi-JsPhys/3d-fabric/skills/texture-state-animation/SKILL.md

texture-state-animation

Skill2 starsChanged 3 days agoMITView on GitHub

Design and validate texture-state transitions for Blender animations without ugly whole-image crossfades, texture popping, misregistered morphs, or target-engine-incompatible Python-only swaps. Use when animating between multiple source textures, mascot/logo states, style states, lightmaps, decals, or UI skins.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use when: Texture state animation, texture morphs, material state transitions, image sequence planning, masked wipes, glow reveals, texture …

    line 10
  2. Distinctive:

    Before the first Blender call, read ../text-to-blender/references/mcp-backends.md.

    line 12
  3. Distinctive:

    avoid Blender Python handlers for final GLB unless the target runtime will recreate them.

    line 43
  4. Distinctive:

    No full-canvas crossfade is used unless state registration and semantics match.

    line 49

≈ “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

MCP backend

Use when: Texture state animation, texture morphs, material state transitions, image sequence planning, masked wipes, glow reveals, texture registration, avoiding bad crossfades, GLB-compatible texture animation planning.

Before the first Blender call, read ../text-to-blender/references/mcp-backends.md. Prefer official MCP for shared capabilities; preserve the selected backend for the whole task. Tool names in recipes are client/legacy examples: map them through that reference and its agent-host guide.

Texture State Animation

This skill exists because “crossfade several full images” usually looks bad. Texture animation must be designed like motion graphics: registered states, constrained transition channels, and preview gates.

Failure modes to avoid

  • Whole-frame crossfades between unrelated crops/compositions.
  • Python frame handlers as the only playback mechanism when export/runtime support is needed.
  • Texture swaps that change silhouette, camera crop, or scale at the same time as decorative motion.
  • Mixing aura/background/HUD pixels into the avatar surface texture unless that is the intent.
  • Morph pulses that break accepted geometry constraints such as constant depth.

Workflow

  1. Register states first: crop, scale, align, and color-normalize all source states into one canvas and one semantic mask.
  2. Classify pixels/layers:
    • avatar surface/base;
    • facial decal/features;
    • glow/emission accents;
    • background/aura/context;
    • HUD/circle elements.
  3. Choose transition type per layer, not one global blend:
    • avatar surface: hold, shimmer, subtle value/roughness pulse, or masked dissolve;
    • face features: hold or short opacity fade;
    • glow accents: emission pulse / traveling highlight;
    • aura/HUD: independent orbit/dash/dot animation;
    • background: separate plane/compositor, never baked into avatar unless requested.
  4. Use export-compatible channels when needed:
    • keyframed material values, opacity, UV transform, shape keys, object transforms;
    • image sequence only if target supports it;
    • avoid Blender Python handlers for final GLB unless the target runtime will recreate them.
  5. Render a contact sheet and flicker report before calling the animation acceptable.

Acceptance gates

  • Each texture state is registered to the same bbox/landmarks.
  • No full-canvas crossfade is used unless state registration and semantics match.
  • Avatar silhouette remains stable unless the story explicitly calls for a morph.
  • Context/aura elements are separate from the avatar material.
  • The exported format can reproduce the animation, or limitations are documented.

Scripts

  • scripts/texture_transition_plan.py creates a transition plan from source states and flags risky whole-frame crossfades.

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.