> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/developers/getting-started/tooling.md).

# Prepare Your Tools

Install the XL1 wallet and development tools required by the guide you choose.

Different samples were created at different times, so their runtime and package-manager requirements are not identical. Follow the versions in the sample you are running instead of applying one version to every XL1 project.

| Guide                | Runtime             | Package manager | Wallet             |
| -------------------- | ------------------- | --------------- | ------------------ |
| Local React sample   | Node.js 22 or newer | npm             | XL1 browser wallet |
| Local Node.js sample | Node.js 22 or newer | Yarn            | XL1 browser wallet |

## Before you begin

* Install the exact Node.js and package-manager versions named by the guide.
* Use only the wallet type the sample expects.
* Keep seed phrases, private keys, passwords, and provider API keys out of source control.
* Confirm whether the sample targets Local, Sequence, or Mainnet.

See [Developer Tools](/developers/tools.md) for official wallets, explorers, repositories, and samples.


---

# 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.xyo.network/developers/getting-started/tooling.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.