> 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/cad-programs/solidworks.md).

# Solidworks

VEX CAD Solidworks Library.

## [Latest Release: 1.1.0](https://github.com/VEX-CAD/VEX-CAD-Solidworks/releases/latest)

This library includes all VEX parts (as of 2/17/2023) for ease of use when CADing.

### [Parts Library Download](https://github.com/VEX-CAD/VEX-CAD-Solidworks/releases/latest)

The recommended file structure is to have a CAD folder anywhere on your computer, and place the [latest release](https://github.com/VEX-CAD/VEX-CAD-Solidworks/releases/latest) in this folder. Every new robot you create will be a new folder in the CAD folder.

## [Change Log](https://github.com/VEX-CAD/VEX-CAD-Solidworks/blob/v1.1.0/Changelog.txt)

To see everything changed between versions, check the [changelog](https://github.com/VEX-CAD/VEX-CAD-Solidworks/blob/v1.1.0/Changelog.txt)!

## [FAQ](https://github.com/VEX-CAD/VEX-CAD-Solidworks/wiki)

Please read the [FAQ](https://github.com/VEX-CAD/VEX-CAD-Solidworks/wiki) if you're having installation issues.

## [VEX CAD Discord](https://discord.gg/BKV3DJm)

If you need more help, or would like assistance from experienced users, please ask in our [Discord server](https://discord.gg/BKV3DJm)!

## Solidworks Library Contributors

* Owen - 169E
* Ryan - 4253B

NOTE: This library is not backwards compatible for versions before Solidworks 2021-2022


---

# 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/cad-programs/solidworks.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.