tinqs/animation
5
0
Fork 0
Code Pull Requests Actions Packages Projects Releases Wiki Activity Issues

docs(naming): dance codes are ceremony-based (<ceremony><NN>)

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Jeremy
2026-07-16 14:28:35 -07:00
parent b918d8670f
commit 6a1290b1d1
2 changed files with 12 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/skills/animation/SKILL.md
+5 -3
View File
@@ -36,9 +36,11 @@ Two-stage names. **New dances get a provisional id, never a content name**: at
conversion, assign the next free `nd##` from the registry — pack `nd08`, clip `ND08`,
JSON `nd08.json`, variants `nd08_pp`/`ND08PP` — regardless of what the PC export was
called (a take named "firedance1" turned out to be dance1's choreography). Only when
Jeremy **adopts** a take for a specific in-game dance is it renamed to its dance code:
`<style><NN>` lowercase pack (`haka01`), PascalCase clip (`Haka01`) — via
`tools/rename_clip.py` + JSON rename + registry update. Rejected takes are archived
Jeremy **adopts** a take for a specific in-game dance is it renamed to its dance code —
codes are named after the **dance ceremony** the take corresponds to: `<ceremony><NN>`
lowercase-ascii pack (`powhiri01`, `hulakahiko01`, `sivaafi01`), PascalCase clip
(`Powhiri01`) — via `tools/rename_clip.py` + JSON rename + registry update. Never
guess the ceremony; Jeremy assigns it. Rejected takes are archived
(`archive/` here; `archive/dances/` in ariki-game, which is `.gdignore`d), never deleted.
Numbers are never reused. Always update the registry row when converting/adopting/archiving.