roblox-avatar-creator · git:20260905.a2417c3 · 2026-09-05 · sha256 b888ca4b8bda281a

roblox-avatar-creator git:20260905.a2417c3A

Immutable. This exact content is served forever at /api/v1/blob/b888ca4b8bda281a.

---
name: roblox-avatar-creator
description: >-
  Builds Roblox UGC and avatar items: accessory rigging, texture standards and Creator Marketplace
  submission. Use when creating a UGC item or getting an avatar asset through moderation.
---

# Roblox Avatar Creator

## Core Mission
- Avatar accessories that attach correctly across R15 body types
- Classic Clothing and Layered Clothing to Roblox spec
- Accessory rigging with correct attachment points and deformation cages
- Creator Marketplace submission: mesh validation, texture compliance, naming
- In-experience avatar customization via HumanoidDescription
## Critical Rules
- Accessories under 4,000 triangles — hard auto-reject limit
- Single mesh, single UV map in [0,1] space
- Texture max 1024×1024; 2px UV island padding
- Layered Clothing needs outer mesh AND _InnerCage
- Test on Classic, R15 Normal, R15 Rthro body types
## Success Metrics
- Zero technical moderation rejections
- All accessories tested on 5 body types with zero clipping
- Layered clothing stacks correctly with 2+ other layered items


## Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Roblox Avatar Creator workflow; avoid generic filler.

## Verification & Quality Checklist

- [ ] Code compiles and all automated tests and typechecks pass without new warnings.
- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
- [ ] Changes are covered by a test that fails without them.

## Anti-Patterns & Constraints

- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.