---
title: Game Asset Naming
category: product
entity_type: skill
price: $15
canonical: https://forgehouse.ai/skills/game-asset-naming/
lang: en
hreflang_alt: https://forgehouse.ai/tr/skiller/game-asset-naming/
last_updated: 2026-06-20
---

# Game Asset Naming

> Enforce consistent naming conventions for game assets scene/prefab/script/sprite/…

A naming-convention enforcement system for Unity 6 game assets: sprites, prefabs, scenes, scripts, animation clips, audio, materials, and tiles. It defines a strict prefix-and-pattern grammar (char_, env_, tile_, prop_, ui_, fx_ and more) and enforces it through three layers: a Unity import-time validator, a pre-commit hook, and CI lint. This kills naming drift that breaks search, spawns duplicate assets, and corrupts Addressables catalogs.

## Use cases
- Seeding a naming convention at the start of a new Unity project
- Catching badly named sprites and prefabs before they reach a commit
- Standardizing character, tile, animation, and scene naming patterns
- Preventing duplicate assets caused by inconsistent naming
- Onboarding new artists and developers with a readable naming reference
- Blocking Unicode, spaces, and mixed-case filenames that break cross-platform builds

## Benefits
- Find any asset in seconds via prefix filters instead of scanning manually
- Eliminate duplicate assets and the bundle bloat they cause on mobile
- Catch naming violations at import, commit, and CI: three layers, nothing slips through
- Cut new-developer onboarding time with names that read at a glance

## What’s included
- Prefix taxonomy mapping each category to its folder and example name
- Naming-pattern regexes for sprites, tiles, animations, prefabs, and scenes
- Unity AssetPostprocessor validator that flags violations at import time
- Pre-commit and CI lint scripts that block non-compliant filenames
- PascalCase rules for C# scripts and folder-structure standards
- Cross-platform case-sensitivity guidance and an anti-pattern reference

## Who it’s for
Unity game developers and technical artists on teams who need a searchable, collision-free asset library that scales past thousands of files.

## How it runs
Badly named assets get caught three times: at import by an AssetPostprocessor, at commit by a pre-commit lint, and again in CI. Renames migrate references through a 30-day alias instead of breaking scenes.
1. Seeds the convention first: a category prefix table (char_, env_, tile_, prop_, ui_, fx_, audio_sfx_...) plus the full pattern prefix_entity_variant_direction_frame, all lowercase ASCII, with C# scripts as the single PascalCase exception.
2. Validates at import time: the AssetNamingValidator AssetPostprocessor checks every new asset against per-folder regexes (sprites, prefabs, scenes each have their own) and logs an explicit error with the expected format. ThirdParty and Packages folders are exempt by design.
3. Re-checks on move and rename: OnPostprocessAllAssets re-validates moved assets, so a correctly named file dragged into the wrong category folder (env_tree.png inside Characters) is caught immediately.
4. Blocks at commit: the pre-commit lint script walks git's staged added files, matches them against the same regexes, and exits 2 with the violation list, so a bad name never lands in history. CI repeats the same lint on the pull request as the third net.
5. Handles renames without breaking references: instead of renaming in place, the old asset stays as a 30-day alias while all scene references migrate to the new name, then the old one is deleted.
6. Sweeps the anti-pattern list on existing projects: mixed case, spaces, Turkish or Unicode characters, version numbers and dates baked into filenames, and ambiguous abbreviations all get flagged for migration.

## FAQ
### Can I adopt this mid-project, or only on a fresh Unity repo?
You can seed it mid-project and the validator will catch new violations from that point, but renaming an existing library is manual migration work. It is cheapest at project start and still worth it later, just with more cleanup up front.

### Won't strict naming rules just slow my team down?
The grammar is what makes a large asset library searchable and free of name collisions, and the import-time check catches mistakes before they reach a commit. It saves more time hunting and renaming later than it costs to follow up front.

### Does it organize my folders or manage the asset content?
No, it governs names and patterns, the char_, tile_ and prop_ grammar, not your folder structure or what the assets contain. It makes the library searchable, it does not author or arrange the assets.

## Price
$15, one-time, no subscription. VAT included.

Related guide: [A 2.5D isometric game-dev AI workflow with Unity](https://forgehouse.ai/guides/unity-isometric-ai-workflow/)