> For the complete documentation index, see [llms.txt](https://wiki.purduesigbots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.purduesigbots.com/vex-cad/making-a-chassis/inventor-chassis/introduction.md).

# Installation

In this page, we'll be going over how to setup a file structure for CAD.

Woo! You've downloaded Autodesk Inventor and the [VEX CAD Inventor Library](https://github.com/VEX-CAD/VEX-CAD-Inventor/releases/latest) and you're ready to learn how to use it!

Without a consistent file structure, any attempt at CAD collaboration will cause conflicts and missing parts.

## Creating the File Structure

We recommend creating a new folder called `CAD` in your `Documents` folder on your computer. In the `CAD` folder, place the most [recent version of the Library found here](https://github.com/VEX-CAD/VEX-CAD-Inventor/releases/latest).

Every new robot that you want to CAD, you'll make a new folder here with the name of your robot. When collaborating CAD with your teammates, you will send the **robot folder** back and forward.

When done, your file structure should look like this:

![Completed File Structure](https://3510336827-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M7yGVyBrcpSR8SDSikj%2F-MfExsTMauY7LKqYC_Iy%2F-MfEzLDfvroXyxgwyaZM%2FFile%20Structure.png?alt=media\&token=b2588bd4-cf99-4c1b-b4bf-901998f7dc17)

## Contributors to this Article:

* Jess - EZ

\\


---

# 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://wiki.purduesigbots.com/vex-cad/making-a-chassis/inventor-chassis/introduction.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.