> 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/code/getting-started/tutorials/gum-project-forms-tutorial.md).

# Gum UI Tool and Code Tutorial

## Introduction

This series of tutorials covers how to use the Gum tool to create UI for your project. This tutorial shows how to create a *full featured* Gum project including:

* Creating and loading a Gum project
* Using Gum's code generation for strongly-typed access to your Gum project
* Using Forms controls including Button, TextBox, and ListBox
* Navigating multiple Screens
* Styling Gum Components

This tutorial assumes a basic understanding of the Gum tool. Specifically it assumes you know how to:

* Move and resize instances
* Create Screens and Entities
* Work with the Variables tab

If you are brand new to Gum, we recommend learning about how to work with the Gum tool by reading the Gum tool [Intro Tutorials](/gum/gum-tool/tutorials-and-examples/intro-tutorials.md).

{% hint style="info" %}
This tutorial series uses the Gum UI tool and loads the resulting .gumj project and its associated files. If you do not want to use the Gum tool, or if you have some restrictions (such as game IO restrictions), you may want to look at code-only projects. These are discussed in the [Code-Only Gum Forms Tutorial](/gum/code/getting-started/tutorials/code-only-gum-forms-tutorial.md) series.
{% endhint %}


---

# 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/code/getting-started/tutorials/gum-project-forms-tutorial.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.