> For the complete documentation index, see [llms.txt](https://www.ftcwiki.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ftcwiki.org/design-style/design-guidelines/naming-conventions.md).

# Naming Conventions

CAD files can become a mess faster than your pit table if you don’t stay organized. Clean file structure and naming make it easier for multiple people to collaborate and modify the design as it evolves.

#### Naming Conventions

Good names are:

* **Descriptive** (e.g., `right_drive_motor_mount` vs. `part3`)
* **Consistent** (stick to lower\_case\_with\_underscores or CamelCase—not both)
* **Structured** by category: `drive_`, `intake_`, `arm_`, etc.

#### Folder and Feature Management

* Organize parts into folders by subsystem
* Name sketches, features, and planes clearly (`sketch_belt_profile`, `plane_mount_face`)
* Use labels or custom colors to differentiate moving vs. fixed parts

#### Version Control

* Use `V1`, `V2`, etc. in part names or folders when iterating
* Archive old versions instead of deleting
* Record design decisions in comments or a changelog

#### Onshape Tips

* Use Part Studios to group related geometry
* Use Assembly tabs to simulate movement and fit
* Use variable naming for constants like extrusion length, spacing, or hole offsets


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.ftcwiki.org/design-style/design-guidelines/naming-conventions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.