# Tools

The `jadpo` command and everything around it: the formatter, the editor
support, how errors are shown, the generated `build/` folder, the tools
agents use to look things up before they change code, and how an app is
built into the programs you deploy.

Everything here comes from the compiler. The editor, the agent skill and
every generated file are made by the same check as `jadpo check`, so they
can't disagree with it.

| Page | What it covers |
|---|---|
| [Commands](/docs/commands.md) ▲ partly | Every jadpo command, what it does and how to run it. |
| [Formatter and editors](/docs/formatter-and-editors.md) | How `jadpo fmt` lays out your code, and what your editor gets from Jadpo. |
| [Building and deploying](/docs/building-and-deploying.md) | What `jadpo build` writes, for a server of your own or for Cloudflare Workers, and which version of `jadpo` a project runs. |
| [Tools for agents](/docs/tools-for-agents.md) | Coding agents look things up through the compiler rather than by browsing folders. |
| [Suggestions](/docs/suggestions.md) | `jadpo suggest` finds code that could use a standard type or a standard operation, such as money held as a whole number of pence, or a loop that adds up a list. |
| [Debugging](/docs/debugging-and-review.md) ▲ partly | Jadpo code is written mainly by coding agents and read by people, so two jobs matter most. |
| [Review and records](/docs/records-and-manifest.md) | Besides your running app, the compiler writes two kinds of file, and it keeps them apart so that every change can be reviewed and every production event traced back to its source. |

[What is built](/docs/tooling-built.md) says which of this works today.