> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/getting-started/project-prep/2.-getting-ready-for-your-threekit-project.md).

# 2. Getting Ready for Your Threekit Project

**Overview**

Discussions around project readiness, we worked with our Implementation Team to provide you our best practices around preparing your data, models, and project team prior to kickoff and incorporated this into our [*Getting Ready For Your Visualization Project*](https://files.threek.it/training/CommunitySite_Resources/Getting%20Ready%20for%20Your%20Visualization%20Project.pdf), which you can also download at the bottom of this article.

We recommend reviewing this information prior to onboarding so you can address any questions with your Customer Success Manager or Implementation Team.

![](https://2029237644-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8N1IA5a0lqRClKT5eQQ7%2Fuploads%2FZMHoK3MxbURlpX3cGThq%2Fmceclip1.png?alt=media\&token=3da10eb6-7f99-4c74-92c9-42d938501309)

Continue your "Getting Ready" journey with [Org Provisioning & Adding Users](/getting-started/project-prep/3.-org-provisioning-and-adding-users.md). This will enable you to add members of your team to your Threekit project environment.


---

# 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://community.threekit.com/getting-started/project-prep/2.-getting-ready-for-your-threekit-project.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.