agentleFS
arjun988arjun988/blender-skills/.claude/skills/hair-groom/SKILL.md

hair-groom

Skill2.2k starsChanged 4 months agoMITView on GitHub

Hair and fur grooming in Blender using curves, particle hair, geometry nodes, and game hair-card workflows. Use for characters, creatures, and real-time hair cards via MCP.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 8 mentionsNov 2026: 3 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the arjun988/blender-skills repository that our weekly crawl found: only 12 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about arjun988/blender-skills

The biggest 5 of 12 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 12

Talked about on GitHub (12 times).

On GitHub · 12

7 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Prefer opacity clip or hashed for Eevee preview

    line 65
  2. Distinctive:

    Test silhouette from game camera angles

    line 78

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

Hair Groom

Believable hair flow. Scalp coverage. Cards for games. Curves/particles for cinematic.

When to Use

  • Character scalp hair, beards, brows
  • Creature fur / mane / whiskers
  • Game hair-card generation and placement
  • Cinematic curve/particle grooms

Path Decision

Target = Game / real-time  → Hair cards (+ optional proxy curves)
Target = Cinematic        → Curves or particle hair + materials
Target = Both             → High groom → bake cards / textures

Workflow (Game Cards)

Scalp mesh → Guide curves → Card strips along flow
  → Atlas UVs → Alpha/normal hair texture → LOD cards → Export

Workflow (Cinematic)

Scalp → Particle/curve groom → Clump/frizz/noise
  → Hair shader (melanin/roughness) → Render test → Cache if needed

Groom Principles

  1. Flow first — Primary direction before flyaways
  2. Density hierarchy — Dense roots, controlled tips
  3. Clumps — Hair reads as groups, not spaghetti
  4. Silhouette — Outer shape more important than strand count
  5. Scalp bleed — Avoid bald patches at hairline

Card Guidelines

LODCards (guide)Notes
Hero close-up80–200Layered shells
Standard30–80Main masses
Distant8–20Cap + few strips
  • Name: SM_HairCard_[Region]
  • Atlas: T_Hair_[Name]_RGBA (alpha in A)
  • Prefer opacity clip or hashed for Eevee preview

Naming

  • Guides: CRV_HairGuide_[Region]
  • Cards: SM_HairCard_[Region]
  • Collection: COL_Hair_[Character]

Constraints

MUST DO

  • Establish hairline and parting early
  • Match card UVs to atlas layout
  • Test silhouette from game camera angles

MUST NOT DO

  • Uniform card width everywhere
  • Skip root density near scalp
  • Over-detail flyaways before primary masses

Reference Guide

TopicReferenceLoad When
Hair Card Atlasreferences/hair-card-atlas.mdWhen needed
Groom Flow Regionsreferences/groom-flow-regions.mdWhen needed
Cinematic Vs Gamereferences/cinematic-vs-game.mdWhen needed

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.