> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/getting-started/already-using-jet-start-with-ai.md).

# Already using Jet? Start with the AI builder

You can use the Prompt Assistant for a new app without rebuilding every Classic app. Start with a task that needs a new screen, process, or user flow, and decide which existing data and rules it depends on.

1. List the data sources, user roles, and actions the current app relies on.
2. Connect the same sources in a new AI app or use a test copy of the data. Name actual fields in the first prompt.
3. Build the smallest working slice and compare its screens, queries, and permissions with the existing app.
4. Test write actions and access with representative roles. Publish only after the new behavior is clear.

For a side-by-side choice, see [Choose AI or Classic App Builder](/getting-started/choose-ai-or-classic-app-builder.md). Keep the [Classic App Builder guides](/classic-app-builder/maintain-an-existing-classic-app.md) for maintaining your existing visual-builder app. Move from Classic to AI covers a gradual transition.


---

# 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.jetadmin.io/getting-started/already-using-jet-start-with-ai.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.