# Choose a Prisma ORM setup path (/docs/getting-started) > For the complete Prisma documentation index, see [llms.txt](https://www.prisma.io/docs/llms.txt). A markdown version of any docs page is available by appending `.md` to its URL. Pick the Prisma ORM quickstart that matches where you are starting from. Location: Choose a Prisma ORM setup path Prisma ORM 8 is a release candidate, and [Release status](https://www.prisma.io/docs/orm/release-status) says what that means for your app. Pick the page that matches where you are starting from. Each page uses PostgreSQL, and if you use MongoDB, it links to its MongoDB version. - [I'm creating a new app](https://www.prisma.io/docs/prisma-orm/quickstart/postgresql): Create an app from a template and run your first query. - [I have an app, no database](https://www.prisma.io/docs/prisma-orm/quickstart/existing-app/postgresql): Add Prisma ORM to your app, create the tables, and apply your first migration. - [I have a database already](https://www.prisma.io/docs/prisma-orm/add-to-existing-project/postgresql): Generate a Prisma schema from your existing tables, then change the schema and apply the change with a migration. - [I have a Prisma 6 or 7 app](https://www.prisma.io/docs/guides/upgrade-prisma-orm): Upgrade all at once, or run Prisma ORM 7 and Prisma ORM 8 side by side and move your code over one part at a time. To build an app, put it on Prisma Postgres, and deploy it to Prisma Compute in one sitting, follow the [full-stack tutorial](https://www.prisma.io/docs/full-stack-tutorial). To look up what a Prisma ORM 7 API is called in Prisma ORM 8, see [Coming from Prisma ORM 7](https://www.prisma.io/docs/orm/coming-from-prisma-orm-7). ## Use with your agent [#use-with-your-agent] If you are creating a new app, you can hand the work to your coding agent instead. Copy this prompt and give it to your agent. You can replace `[framework]` with one of the template names listed in the prompt, or leave it, and the agent asks you which one you want. The prompt uses PostgreSQL: ```text Create a new [framework] application with Prisma ORM, seed it, and run it locally. If I have not told you which framework, stop and ask before scaffolding. Valid --template values: minimal (the default), next, hono, nuxt, astro, nest, svelte, tanstack-start, elysia, turborepo (a monorepo: the server is in apps/server, and the contract, seed and database client are in packages/database/src). Check the Node.js version first: `node --version` must print 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer. For the nuxt template, it must print 22.22.3 or newer on the 22 line, 24.15 or newer on the 24 line, or 26 or newer, because Nuxt requires it. The npm that ships with your Node.js release works; on Node.js 22 that is npm 10. 1. Scaffold the app: `npm create prisma@latest -- my-app --template [framework] --provider postgres --yes`. 2. Get a database connection string: use the one I give you, or create a Prisma Postgres database with `npx create-db@latest` and show me the claim URL it prints. Export it as `DATABASE_URL` in the shell: in a project created with `npm create prisma`, the Prisma CLI scripts in package.json read the environment variable, not `.env`. 3. From the project directory, apply the starter contract: `npm run db:init`. The app seeds sample users on its first query, from `src/prisma/seed.ts` (`packages/database/src/seed.ts` for turborepo); there is no seed command to run. 4. Edit the starter contract under `src/prisma/` (`packages/database/src/` for turborepo) into a small schema for my use case, then run `npm run contract:emit` and plan and apply the migration: `npx prisma migration plan --name `, then `npx prisma db migrate --advance-ref db --yes`. Migration planning diffs the emitted contract, so the emit step is required. Pass `--advance-ref db` on every apply to this development database, so that the next `migration plan` starts from the state you applied; without it, the next plan repeats the last change and `db migrate` fails with `MIGRATION.PATH_UNREACHABLE`. 5. Update `src/prisma/seed.ts` (`packages/database/src/seed.ts` for turborepo) and the app routes to query the new schema, start `npm run dev` in the background (with `DATABASE_URL` exported), and verify with a request against the running app. For the `nest` template, if routes return 500s with `reading 'findAll'` in the logs, add explicit `@Inject()` tokens as shown in https://www.prisma.io/docs/guides/frameworks/nestjs.md. Use the installed Prisma ORM skills and the current Prisma docs: https://www.prisma.io/docs/llms.txt (append `.md` to any docs URL for a markdown version). ``` ## Related pages - [Console](https://www.prisma.io/docs/console): Learn how to use the Console to manage and integrate Prisma products into your application. - [Introduction to Prisma ORM](https://www.prisma.io/docs/prisma-orm): Prisma ORM 8 is a release candidate. - [Local development](https://www.prisma.io/docs/local-development): Run the whole Prisma stack on your machine, with your app on Bun, a local Prisma Postgres database, and local object storage. - [Overview](https://www.prisma.io/docs/cli): Prisma CLI reference - [Overview](https://www.prisma.io/docs/guides): Practical, step-by-step guides for building with Prisma ORM and deploying to Prisma Compute, each one run end to end before it ships.