Sounds like you’re already on the right track with the numbered series. Here’s a quick routine that keeps things tight when you’ve got several rigs: 1. Pick a root prefix that’s unique to the project – like “ProjX_” – then add the rig type, e.g. “ProjX_Spine_01”. 2. Lock the naming pattern in a spreadsheet or a small JSON file you check in with your repo; that way the next person sees exactly how you structure it. 3. Use a script that scans the hierarchy and flags any node that breaks the pattern – better to catch a typo than a mis‑named joint later. 4. If you’re juggling multiple characters, include a character code in the prefix, e.g. “C1_Spine_01”. 5. Finally, commit a naming‑policy doc to your project wiki and keep it handy – consistency is the fastest way to avoid those “where did that joint go?” moments. Give it a go and let me know if the auto‑check script catches anything fishy.