> 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/intro-to-cad/level-2/a.-onshape-basics-wip.md).
# A. Onshape Basics (WIP)
## Introduction
Level 2 begins here! In this phase, you'll dive into a series of Onshape exercises and projects designed to strengthen your CAD skills within an FTC environment.
Level 2A is divided into three main sections:
* **Sketching and Part Design**
* **Multi-Part Part Studios**
* **Assemblies**
Each section provides a learning course to build your skills, followed by an exercise to apply them directly in an FTC context.
## Learning Courses
[Onshape's Learning Center](https://learn.onshape.com/) offers free courses and articles covering everything from basic document navigation and sketching to advanced surface and sheet metal modeling. It's a great resource for both beginners and experienced users.
Onshape's Learning Center
While we use a few selected courses to build foundational CAD skills in Onshape, the majority of the curriculum is project-based. Each course includes short videos and practice models, with an expected completion time of 2–4 hours.
---
# 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/intro-to-cad/level-2/a.-onshape-basics-wip.md?ask=&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.
