> For the complete documentation index, see [llms.txt](https://docs.cb21829.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cb21829.org/ftc-java-beginner-guide/structuring-your-code.md).

# Structuring your code

### Constants in one place

Avoid magic numbers. Put them in one file.

```java
public class Constants {
    public static final double CLAW_OPEN   = 0.0;
    public static final double CLAW_CLOSED = 0.55;
    public static final double LIFT_SPEED  = 0.8;
    public static final int    LIFT_HIGH   = 2200;
}
```

Then reference `Constants.CLAW_OPEN` instead of repeating values.

### A hardware class

As the robot grows, move repeated `hardwareMap.get(...)` calls into one class. That class can own the hardware and expose helper methods for both TeleOp and Autonomous.

### Naming

Name devices for what they are:

* `frontLeft`
* `intakeMotor`
* `wristServo`

Avoid names like `motor1` and `m2`.

### Version control with Git

Use Git from day one.

```bash
git add .
git commit -m "Add mecanum teleop"
git push
```

Git gives you:

* a history of working versions
* safer collaboration
* an easy rollback when something breaks


---

# 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://docs.cb21829.org/ftc-java-beginner-guide/structuring-your-code.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.