avatar-create
Skill12 starsChanged 23 days agoMITView on GitHub
Use when a character creator needs stable part, slider/morph or hotspot identities, save/load compatibility, rig/socket constraints, cosmetic ownership and explicit separation from gameplay-affecting body rules.
In this repository194 other files it gives its agents.
- llms.txtllms.txt
- hd-sprite-sequenceSkill
- pixel-animationSkill
- skin-weightsSkill
- spine-skeletalSkill
- sprite-atlasSkill
- sprite-catalogSkill
- sprite-skinSkill
- art-bibleSkill
- asset-pack-intakeSkill
- character-rigSkill
- materialsSkill
- model-pipelineSkill
- open-asset-fixtureSkill
- vfx-generateSkill
- a11y-controlsSkill
- ability-gateSkill
- action-feelSkill
- ad-breakSkill
- adventure-toolSkill
- aggro-tableSkill
- aim-assistSkill
- ammo-reloadSkill
- analytics-funnelSkill
- animation-blendSkill
- animation-graphSkill
- asset-runtimeSkill
- attack-tellSkill
- audio-busesSkill
- audio-feelSkill
- balance-designSkill
- boss-designSkill
- browser-inputSkill
- camera-anti-clipSkill
- camera-modestySkill
- camera-shotsSkill
- cert-handoffSkill
- chemistry-verbsSkill
- climb-vaultSkill
- cloud-saveSkill
- collision-layersSkill
- combo-designSkill
- cover-shooterSkill
- cover-spaceSkill
- crafting-loopSkill
- currency-dualSkill
- cutscene-handoffSkill
- day-nightSkill
- death-carrySkill
- debug-slateSkill
- deck-buildSkill
- dialogue-beatSkill
- dialogue-flagsSkill
- difficulty-designSkill
- dodge-iframeSkill
- durability-economySkill
- encounter-designSkill
- enemy-aiSkill
- enemy-fireSkill
- enemy-kit-balanceSkill
- The first 60 shown.
The file
Files
Avatar create
Compatible modes
part-kit | slider-morph | hotspot-sculpt
The project may combine modes when ownership and serialization are explicit.
Creator schema
Persist stable IDs/values rather than visible labels or array indices:
creator schema/version
base/body preset ID when applicable
part/cosmetic IDs + slots
slider/morph semantic IDs + values
material/colour IDs or normalized values
rig/body compatibility tags
random seed when randomisation must reproducesave-systems owns migration/atomic persistence. character-rig owns skeleton/sockets; face-morph owns facial channel schema; game-monetization/entitlements own paid/unlocked access.
Rules
- Creator state must save and reload/migrate by stable identity across reordered catalogs where supported.
- Parts/sliders respect declared rig, socket, clipping, LOD and animation compatibility. Invalid combinations are rejected, constrained or supplied a documented fallback.
- Cosmetic presentation does not silently change hitboxes, cancel windows, movement or other gameplay. If body morphology is gameplay-affecting, a separate explicit gameplay/body/collision contract owns it.
- Availability/unlock policy is project/economy data; do not assume body identity is always free/up-front or wardrobe always unlocks later.
- Randomisation and presets use stable IDs/seed when reproducibility matters and do not produce unsupported combinations.
- Proportion sliders (height, head-to-body ratio, limb length) declare which regions stay rigid (head, face texture, sockets) and how the rest maps. Lengthening without matching width/thickness rules gives implausible bodies. Validate each slider at both ends of its range across LOD tiers for rig/socket fit, clipping and triangle/memory budget. Adapt resolution or LOD where the budget would otherwise be exceeded.
- Preset values derived from other parameters, such as proportion from height, come from a documented, versioned function of stable inputs. Saves store either the resolved values or the inputs plus the derivation version.
Accept
Save/load several materially different creators, reorder a test catalog/schema migration, exercise incompatible part/rig cases, and build every proportion slider at its range ends on each LOD tier. Stable identities reconstruct the intended avatar or a documented fallback, while cosmetic-only changes leave gameplay contracts unchanged.
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
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.

