agentleFS
JiamingShi-JsPhysJiamingShi-JsPhys/3d-fabric/skills/orbital-hud-motion/SKILL.md

orbital-hud-motion

Skill2 starsChanged 3 days agoMITView on GitHub

Create tasteful circular/orbital HUD and aura animations around a Blender subject using source-derived arcs, dots, dashes, opacity, parallax, and restrained motion. Use when decorative circles, halos, orbit markers, scanner rings, or HUD effects must correlate with a logo/mascot rather than looking like random oversized rings.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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. Distinctive:

    Use when: Animated circular HUD elements, aura rings, orbit arcs, dots, dashed circles, halo effects, mascot/logo motion graphics, …

    line 10
  2. Distinctive:

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

    line 12
  3. Distinctive:

    Keep the avatar/subject dominant.

    line 19
  4. Very specific:

    Prefer opacity/emission/dash phase over large rotation/scale changes.

    line 26
  5. Distinctive:

    Never animate all rings in the same direction/speed.

    line 27
  6. Distinctive:

    Do not include context rings in the base avatar mesh/export unless explicitly requested.

    line 28
  7. Very specific:

    Create an HUD_CONTEXT collection separate from AVATAR_BASE.

    line 32
  8. Distinctive:

    No random full circles when the reference has broken arcs/dashed guides.

    line 44
  9. Distinctive:

    No oversized markers unless the source has them.

    line 45
  10. Distinctive:

    No HUD animation until static avatar baseline is locked.

    line 46

≈ “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: Animated circular HUD elements, aura rings, orbit arcs, dots, dashed circles, halo effects, mascot/logo motion graphics, source-derived decorative elements, avoiding bad outside-element animation.

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.

Orbital HUD Motion

Decorative circles are design elements, not filler. They must be derived from the reference composition and support the subject.

Design rules

  • Keep the avatar/subject dominant; rings should frame, not trap or overpower it.
  • Derive radii, arc breaks, marker positions, and dash density from the reference image when possible.
  • Separate layers:
    • far/background aura: faint, slow, soft;
    • mid orbit: thin arcs/dashes;
    • markers/dots: sparse and synchronized;
    • foreground accents: rare and short-lived.
  • Prefer opacity/emission/dash phase over large rotation/scale changes.
  • Never animate all rings in the same direction/speed; use subtle counter-motion/parallax.
  • Do not include context rings in the base avatar mesh/export unless explicitly requested.

Animation recipe

  1. Create an HUD_CONTEXT collection separate from AVATAR_BASE.
  2. Build arcs/dots from a manifest of normalized radii and angles.
  3. Keyframe:
    • dash offset or arc reveal;
    • emission strength pulse;
    • subtle rotation (1–12 degrees per loop, not full spin unless requested);
    • marker opacity/scale blips at beats.
  4. Render a contact sheet with subject-only and with-HUD views.
  5. Reject if rings obscure the face/silhouette or dominate the frame.

Hard rules

  • No random full circles when the reference has broken arcs/dashed guides.
  • No oversized markers unless the source has them.
  • No HUD animation until static avatar baseline is locked.
  • For GLB, use object transforms/material keyframes or document runtime requirements.

Scripts

  • scripts/orbit_layout_manifest.py creates a source-independent orbit manifest from simple radii/angle parameters.

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.