Raw Art Asset Foldering & File Naming Convention

5. FileContext Naming ConventionCode (Locked Vocabulary)

File Naming Convention

[PROJECTCODE]_[AssetPrefix]_[AssetName]_[AssetSuffix].[FileType]

To keep file names readable while aligning with industry-recognized shorthand (including Unreal Engine standards), the following context vocabularies and codes are locked.

Rationale

• CPT is more recognizable than CON and avoids collision with config/console shorthand.
• SM / SK follow Unreal Engine conventions and are immediately readable by tech art and engineers.
• Folder names remain semantic; codes are optimized for filenames and engine adjacency.

6. Stage Applicability Matrix

This matrix defines which development stages are applicable per ASSET_TYPE. Stages not listed should not be created unless explicitly approved.

Legend

• ✓ = Standard / expected stage
• △ = Optional, asset-dependent
• ✕ = Not applicable

7. Asset-Level Folder Structure

/[ASSET_NAME]/
	/REFERENCES/_brief/
	/CONCEPT/_reviews/
	/STATIC/_wip/
	/ANIMATION/01_CONCEPT/ -> PSD, CSP, etc
	/VFX/02_STATIC/ -> ZPR, BLEND, FBX, TOOLBAG, PAINTER, PSD, CSP, etc
	/REVIEWS/03_ANIMATION/ -> BLEND, FBX, SPINE, etc
	/WORK/04_VFX/ -> PSD, HIP/HDA, FBX, BLEND, etc
	/PUBLISH/05_PUBLISH/ -> FBX, SKEL, TEXTURES, etc game ready

Folder Intent

• REFERENCES_brief → Briefs, paintovers,initial sketches from directors/leads, moodboards, external refs
• CONCEPT_reviews → Time-based progress previews and feedback records ****
• _wip → Misc WIP, temporary or cross-stage files
• 01_CONCEPT → Concept art, exploration, silhouettes, color keys
• STATIC02_STATIC → Static asset development (model, sculpt, textures)
• ANIMATION03_ANIMATION → Rig, skinning, animation clipsdata
• VFX04_VFX → Asset-specific visual effects (if applicable)
• REVIEWS → Time-based progress previews and feedback records
• WORK → Misc WIP, temporary or cross-stage files
• PUBLISH05_PUBLISH → Approved handoff files per stage

(We will refine the folder/stage matrix for each asset type as we go)

7.1 Reviews Folder Structure & Rules

Progress updates and feedback must be stored under the REVIEWS folder to ensure clear historical tracking and auditability.

/REVIEWS/_reviews/
  /[YYYYMMDD]_[STAGECODE]_update/
  /[YYYYMMDD]_[STAGECODE]_feedback/

Naming Rules

• YYYYMMDD uses calendar date of the review or submission

• STAGECODE must match the asset stage being reviewed (CPT / SM / SK / VFX)

• One update folder may have multiple preview files (screenshots, playblasts, turntables)

• Feedback folders may contain:

  • Annotated imagesimages/videos
  • Written feedback (PDF, TXT, MD)
  • Call notes or screenshots from review tools

Example

/REVIEWS/_reviews/
  /20260120_SM_update/
    ASTRA_HeroKnight_SM_turntable.VA6_HeroKnight_SM_turntable.mp4
    ASTRA_HeroKnight_SM_view01.VA6_HeroKnight_SM_view01.png
  /20260121_SM_feedback/
    ASTRA_HeroKnight_SM_feedback_v01.VA6_HeroKnight_SM_feedback_v01.pdf

Feedback File Naming Hint (Recommended)

[PROJECT]_[ASSET]_[STAGECODE]_feedback_v##.[ext]

Suggested

Additional Best Practices

• Use one update folder per milestone or daily check-in

• Feedback should always reference the corresponding update date and stage

• Do not overwrite previous update or feedback folders

• If multiple review cycles happen in one day, append an index:

  • 20260120_SM_update_aVA6_HeroKnight_SM_view01
  • `20260120_SM_update_b``VA6_HeroKnight_SM_view02

8. File Naming Convention (General Format)

[PROJECT]PROJECTCODE]_[ASSET]ASSETTYPE]_[ASSET_TYPE]AssetName]_[STAGECODE]_[DESC]_[VERSION]Suffix].[Filetype]

Example

ASTRA_HeroKnight_Characters_STA_Model_v03.ASTRA_CHR_HeroKnight_SM_Model.blend -> static model file
ASTRA_CHR_HeroKnight_SK_RIG.blend -> rig file
ASTRA_CHR_HeroKnight_SK_AnimationSet.blend -> animation file

### 
Field Definitions
-

**PROJECT**
PROJECTCODE → Project code
- **ASSET**
ASSET → Asset name (matches folder name)
- **ASSET\_TYPE**
ASSET_TYPE → Characters / Environments / Props / UIs / Cinematics / Marketings
- **DESC**
DESC → Purpose or content (Model, Sculpt, Rig, Tex, Blockout)
- **STAGECODE**
STAGECODE → CONCode /for STAthe /stage ANIfollowing /context VFXcode /table REFon /5. WRKContext /Code
PUB
- **VERSION**
SUFFIX → `v01`Additional context, like N (Normal Map), `v02`,ORM `v03`,(Occlusion/Roughness/Metalness etc.Map) *for Textures


(Exact abbreviations to be finalized)*
---

## 9. Versioning Rules (Draft)

- Always increment version numbers, never overwrite
- Use two-digit versions: `v01`, `v02`, `v10`
- Do **not** use `final`, `final2`, `latest`, etc.
- Published files must reference a specific version

---

## 9.1
9 Publish Folder – Approval & Sign-off Rules
The **PUBLISH**PUBLISH folder represents an official, approved state of the asset. Files placed here are considered **production-valid**valid.
###
Rules
Rules

- 
Only **approved versions**versions may exist in `PUBLISH`PUBLISH
- 
Each published file must:must - Matchmatch an approved review cycle in `/REVIEWS`_reviews
-
Reference
Authority
a

specific version number
  - Correspond to a clear development stage (CPT / SM / SK / VFX)

### Authority

- 
Assets may only be moved or copied into `PUBLISH`PUBLISH by:
-

Art Lead / Art Director
- 
Or delegated ownerPIC defined per project
###


Non-Rules
-

`PUBLISH`
PUBLISH is **not**not a backup folder
- `PUBLISH`
PUBLISH is **not**not a place for iteration or WIP
###
Approval Traceability (Recommended)
For every published asset, at least one of the following must exist:
-

A corresponding `[YYYYMMDD]_[STAGECODE]_feedback`_feedback folder indicating approval
- 
A signed-off feedback file (PDF or annotated image)
>

If it’s not in **REVIEWS**_reviews, it’s not approved.

---

## 10. Naming Examples by Asset Type

### Character – Modeling

ASTRA_HeroKnight_Char_Model_v05.blend

###

Prop – Texture

ASTRA_BarrelA_Prop_Texture_v02.spp

### UI – Screen Design

ASTRA_Inventory_UI_Screen_v04.psd

---

## 11.
10. Common Do & Don’t
###
Do
Do

- 
Match file name with asset folder name
- 
Use English, no spacesspaces, -use _underscores_between_naming_codes.

Use UPPERCASE or PascalCase or snake\_caseconsistently
consistently
### 
Don’t
-

Use personal initials in file names
- 
Use ambiguous terms ("test", "new", "fix")
- 
Store final work only in WORKWIP folder
---
Bloat ## 12. Vendor Delivery Checklist (One-Page)

This checklist must be completed by **external vendors** before any asset delivery or milestone submission. Deliveries that do not meet this checklist may be rejected without review.

---

### 12.1 Folder & Structure Compliance

- [ ] Asset is placed under correct `PROJECT_CODE/ART/RAW/ASSET_TYPE/ASSET_NAME/`
- [ ] Folder structure matches studio standard exactly:
  - REFERENCES / CONCEPT / STATIC / ANIMATION / VFX / REVIEWS / WORK / PUBLISH
- [ ] No extra or custom folders added without approval
- [ ] Asset name matchesWIP folder
name
exactly (case-sensitive)

---

### 12.2 File Naming Compliance

- [ ] All files follow naming format:

[PROJECT][ASSET][ASSET_TYPE][STAGECODE][DESC]_[VERSION]

- [ ] Correct **STAGECODE** used (CPT / SM / SK / VFX / REF / WRK / PUB)
- [ ] Version numbers incremented correctly (`v01`, `v02`, etc.)
- [ ] No use of `final`, `latest`, `new`, or personal initials

---

### 12.3 Reviews & Feedback

- [ ] Latest progress preview is submitted under:

/REVIEWS/[YYYYMMDD]_[STAGECODE]_update/

- [ ] Preview includes appropriate media:
- Screenshots / turntables (static)
- Playblast or animation preview (animation)
- [ ] All received feedback is stored under:

/REVIEWS/[YYYYMMDD]_[STAGECODE]_feedback/

- [ ] No feedback or approvals are referenced only via chat or email

---

### 12.4 Publish Folder Rules (Critical)

- [ ] `PUBLISH` contains **only approved files**
- [ ] Each published file:
- References a specific version number
- Matches an approved review cycle
- Uses correct STAGECODE
- [ ] No WIP, test, or backup files exist in `PUBLISH`
- [ ] Vendor has **not self-approved** files unless explicitly authorized

---

### 12.5 Content & Technical Hygiene

- [ ] No broken links, missing textures, or external file dependencies
- [ ] Scene files are clean (no unused test meshes, cameras, lights)
- [ ] Scale, orientation, and unit setup follow project brief
- [ ] Texture sources are included where applicable

---

### 12.6 Final Confirmation (Required)

Before submission, vendor must confirm:

- [ ] All checklist items above are completed
- [ ] Delivery reflects **latest approved feedback only**
- [ ] No additional changes are pending or hidden

> **Reminder:** Assets that do not comply with this checklist may be returned without review or payment delay may apply depending on contract.

---

## 13. Open Questions / To Be Defined

- Final asset naming grammar (singular/plural, numbering)
- Engine-export folder structure alignment
- Automated validation possibilities for vendors

---

**Next Step:** Iterate section-by-section and lock rules once agreed by Art Direction, Tech Art, and Production.