Naming Convention Forge
Design a naming convention, check the generated regex, paste an asset list, and see what fails. Then export the wiki doc, regex, and a generated Python validator for your pipeline. Nothing uploads.
Edit the type prefixes, pick the case style and suffix rules, then paste real asset names and validate them. The example and regex update as you go. When the convention looks right, copy the Markdown for the wiki or download validate_names.py for a pre-submit hook.
Keeping naming rules consistent
A naming convention is easier to keep consistent when the pipeline checks it. Use the generated validator in a submit check, with messages that tell artists what needs changing. Keep the documentation alongside it and try the rules against existing assets before enforcing them.
Anatomy Of The Pattern
PREFIX_Name(_Variant)*(_NN)? gives you a type prefix, a base name, optional variant words and an optional padded number. This tool uses underscores as separators. Agree the case rules with the team and test them on your build machines, especially if you work across case-sensitive and case-insensitive filesystems.
Privacy
Your asset list is processed in this tab and isn’t uploaded. The downloaded validator is readable Python; inspect it before adding it to your pipeline. The site uses Google Analytics for site usage.