> For the complete documentation index, see [llms.txt](https://codethreat-sast.gitbook.io/codethreat-knowledge-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codethreat-sast.gitbook.io/codethreat-knowledge-center/usage-guide/projects/project-structure.md).

# Project Structure

The Project Structure view provides a visual representation of the organization of files and folders within a software project. This guide will help you understand and navigate the structure of your project.

<figure><img src="/files/JKxKQWkbA8UwLKuoM1AV" alt=""><figcaption></figcaption></figure>

* Click on the plus (+) or minus (-) icons to expand or collapse folders, revealing or hiding their contents.
* Folders may represent different aspects of a project such as libraries, frameworks, and custom code.

**Viewing Files**

* Files will typically be listed under their respective folders, often with icons indicating their file type (e.g., `.cs` for C# files).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://codethreat-sast.gitbook.io/codethreat-knowledge-center/usage-guide/projects/project-structure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.