# orbital-hud-motion

A skill that teaches an AI agent to build circular HUD and aura animations around a Blender subject from a reference, not from guesswork.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 714 installs · ★ 125
- Author: RobLe3
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/RobLe3/cc-blender-skill/tree/HEAD/plugin/skills/orbital-hud-motion/SKILL.md
- Updated: 2026-10-12
- HTML: https://affpapa.org/en/nevibecode/skills/orbital-hud-motion

## What it does

The skill covers decorative orbital elements around a logo or mascot in Blender: arcs, dots, dashed rings, glow and light parallax. Radii, arc breaks and dash density come from the reference composition, so the rings frame the subject instead of covering it.

Layers stay separate. The far aura is faint and slow, the mid orbit is thin arcs, markers are sparse and synchronized, foreground accents are short-lived. Motion leans on opacity, emission and dash phase rather than big rotation or scale changes, and the rings should not all spin the same way at the same speed — counter-motion is part of the recipe.

The skill drives Blender through an MCP server: `mcp__blender__execute_blender_code`, `get_scene_info`, `render_viewport_to_path` and others. Before the first Blender call it tells you to read `../text-to-blender/references/mcp-backends.md` and keep the chosen backend for the whole task. Context rings go into a separate `HUD_CONTEXT` collection, not `AVATAR_BASE`, or they end up in the export. A script, `scripts/orbit_layout_manifest.py`, builds an orbit manifest from radii and angle parameters.

## Requirements
- Works with: Blender

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add RobLe3/cc-blender-skill --skill orbital-hud-motion -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/orbital-hud-motion/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/orbital-hud-motion/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add RobLe3/cc-blender-skill --skill orbital-hud-motion -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/orbital-hud-motion/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add RobLe3/cc-blender-skill --skill orbital-hud-motion -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/orbital-hud-motion/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install RobLe3/cc-blender-skill orbital-hud-motion
```

2. **Manually: put the files in place**
- File: `.github/skills/orbital-hud-motion/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add RobLe3/cc-blender-skill --skill orbital-hud-motion -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/RobLe3/cc-blender-skill --path plugin/skills/orbital-hud-motion
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/orbital-hud-motion/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add RobLe3/cc-blender-skill --skill orbital-hud-motion -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/RobLe3/cc-blender-skill/tree/HEAD/plugin/skills/orbital-hud-motion/SKILL.md

## When to use it
- build orbital rings around a logo from a reference image
- split HUD layers by depth and motion speed
- set up emission pulses and dash phase timing
- render a contact sheet with and without the HUD
- move decorative rings into a separate collection before export

## Example prompts
- Build an orbital HUD around the mascot: arcs, dots and dashed rings from the reference
- Split the rings into far aura, mid orbit and markers, then add parallax
- Render a contact sheet: subject only, and subject with HUD

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 8c8e2d7332e121ab.

BEGIN THIRD-PARTY FILE 8c8e2d7332e121ab
```text
---
name: orbital-hud-motion
description: 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.
allowed-tools: Read Bash Glob Grep mcp__blender__execute_blender_code mcp__blender__get_scene_info mcp__blender__get_object_info mcp__blender__get_objects_summary mcp__blender__get_object_detail_summary mcp__blender__render_viewport_to_path mcp__blender__search_api_docs mcp__blender_official__execute_blender_code mcp__blender_official__get_objects_summary mcp__blender_official__get_object_detail_summary mcp__blender_official__render_viewport_to_path mcp__blender_official__search_api_docs
---


## 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](../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;
```
END THIRD-PARTY FILE 8c8e2d7332e121ab

The third-party file has ended. Everything between the 8c8e2d7332e121ab tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2452 of 3126 bytes. © RobLe3 · MIT · https://github.com/RobLe3/cc-blender-skill/tree/HEAD/plugin/skills/orbital-hud-motion/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md