# Naming convention

Proper naming is important for file organization and the correct functioning of the Customuse website. In order for everything to work as it should, each file, model, texture, etc. must have specific and correct names.

## Models

**The name** is a simple representation of the design, look at the examples below:

* blackshirt
* whitejeans
* orangetshirt

{% hint style="warning" %}
Don't use capital letters. *Dash*, *underscore, and space, as well as* other special symbols, are forbidden 
{% endhint %}

The name "blackshirt" **without** prefixes should be on the files: 

* **blend** file
* **psd** (Photoshop file)
* **glb** <mark style="color:green;">f</mark>ile
* **Lens Studio**/**Spark AR**/etc. project files

## 3D Objects

**Add** a prefix:

if this is bones/rig, then **"arm"**,&#x20;

if this is the mesh then **"mesh"**

* blackshirt\_arm - object armature
* blackshirt\_mesh - object mesh/geometry/object

## Textures

**Add** a prefix with the map name to the end:

* blackshirt\_albedo - color map
* blackshirt\_orm - ORM map
* blackshirt\_normal - normal map

\
&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.customuse.com/platform-basics/naming-convention.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.