> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/gum/gum-tool/project-tab.md).
# Project Tab
### Introduction
The Project Tab displays all Screens, Components, Behaviors, and Standard Elements in a project. Standard types are shown at the bottom of the tab as chips, and the rest are organized in folders.
Project tab displaying a Gum project
### Searching
The search bar can be used to find elements in your project by searching for their name. By default the following are searched:
* Screen Names
* Component Names
* Standard Element Names
* Behavior Names
Searching for "Button" displays all elements and behaviors with the word "button"
Additionally, variable values can be searched by checking the **Search variables** checkbox. When checked, variable values are searched for the entered text.
Searching for variables checks all variable values
---
# 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://docs.flatredball.com/gum/gum-tool/project-tab.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.
