prisma
diff --git a/‎apps/docs/content/docs/(index)/getting-started.mdx‎
Lines changed: 45 additions & 38 deletions b/‎apps/docs/content/docs/(index)/getting-started.mdx‎
Lines changed: 45 additions & 38 deletions
@@ -1,71 +1,78 @@
 ---
-title: Choose a setup path
-description: Choose the fastest path to start using Prisma ORM, Prisma Postgres, or Prisma Compute in a new or existing TypeScript project.
+title: Prisma 7 setup paths
+description: Choose the fastest path to start using Prisma ORM 7, Prisma Postgres, or Prisma Compute in a new or existing TypeScript project.
 url: /getting-started
-metaTitle: Prisma getting started
-metaDescription: Choose the fastest path to start using Prisma ORM, Prisma Postgres, or Prisma Compute in a new or existing TypeScript project.
+metaTitle: Prisma 7 getting started
+metaDescription: Choose the fastest Prisma 7 setup path. Quickstarts and existing-project guides for Prisma ORM 7, Prisma Postgres, and Prisma Compute, plus an agent prompt.
 ---
 
-Prisma gives you a few starting points depending on what you want to do first: deploy an app, create a database, use Prisma ORM locally, or add Prisma to an existing project.
+Prisma 7 is the current generally available release of Prisma ORM, and `npx prisma@latest init` installs it. This page collects the Prisma 7 starting points: start a new project, add Prisma to an existing one, then deploy.
 
-## Choose your path
+:::note
 
-### Deploy a full-stack app with a database
+Starting a new project? [Prisma Next](/next) is the recommended path for new apps. It is the next major version of Prisma ORM (soon Prisma 8), available now in Early Access. The [getting started page](/) covers it.
 
-Use this path if you want to deploy a TypeScript app with Prisma Compute and run it alongside Prisma Postgres.
+:::
 
-- [Deploy your first app](/prisma-compute/deploy) on [Prisma Compute](/compute), currently in Public Beta, to run it next to your Prisma Postgres database
+## Start a new project
 
-### Start a new project
+The recommended path is the [Quickstart with Prisma Postgres](/prisma-orm/quickstart/prisma-postgres): it provisions a managed PostgreSQL database for you and gets you from install to first query in about five minutes.
 
-Use this path if you are creating a new app and want to set up Prisma from the beginning.
+Working with a specific database instead?
 
-- [Quickstart with Prisma Postgres](/prisma-orm/quickstart/prisma-postgres) for the fastest end-to-end path with a managed PostgreSQL database
-- [Quickstart with PostgreSQL](/prisma-orm/quickstart/postgresql) if you want to work with PostgreSQL
+- [Quickstart with PostgreSQL](/prisma-orm/quickstart/postgresql)
 - [Quickstart with SQLite](/prisma-orm/quickstart/sqlite) for a lightweight local setup
-- [Quickstart with MySQL](/prisma-orm/quickstart/mysql) if your application uses MySQL
-- [Quickstart with MongoDB](/prisma-orm/quickstart/mongodb) if your application uses MongoDB
+- [Quickstart with MySQL](/prisma-orm/quickstart/mysql)
+- [Quickstart with MongoDB](/prisma-orm/quickstart/mongodb)
 
-### Add Prisma to an existing project
+## Add Prisma to an existing project
 
-Use this path if you already have an application or database and want to add Prisma ORM.
+Use these guides if you already have an application or database and want to add Prisma ORM:
 
 - [Add Prisma ORM to an existing PostgreSQL project](/prisma-orm/add-to-existing-project/postgresql)
 - [Add Prisma ORM to an existing MySQL project](/prisma-orm/add-to-existing-project/mysql)
 - [Add Prisma ORM to an existing SQLite project](/prisma-orm/add-to-existing-project/sqlite)
 - [Add Prisma ORM to an existing MongoDB project](/prisma-orm/add-to-existing-project/mongodb)
 - [Add Prisma ORM to an existing Prisma Postgres project](/prisma-orm/add-to-existing-project/prisma-postgres)
 
-## What you will do
+## Deploy to Prisma Compute
 
-Most Prisma ORM and Prisma Postgres guides follow the same basic flow:
+Once your app runs locally, [Prisma Compute](/compute) (currently in Public Beta) runs it next to your Prisma Postgres database:
 
-1. Define a database connection and data model in your [Prisma schema](/orm/prisma-schema/overview).
-2. Set up your database, either with [Prisma Postgres](/postgres) or another supported database.
-3. Install Prisma CLI and [Prisma Client](/orm/prisma-client).
-4. Run `prisma generate` to create a type-safe client for your schema.
-5. Create or introspect your database.
-6. Start sending queries from your application.
+1. Sign in with `npx @prisma/cli@latest auth login`.
+2. Run `npx @prisma/cli@latest app deploy` from your app directory to get a live URL, adding `--env .env` so environment variables like `DATABASE_URL` reach the deployment.
+3. `--env .env` applies to that one deployment. Persist variables for future deploys with `npx @prisma/cli@latest project env add --file .env --role production`; see [environment variables](/compute/environment-variables).
+4. Keep deploying from the CLI, or [connect GitHub](/compute/github) to deploy on push.
 
-Then you can deploy your app to [Prisma Compute](/compute). The flow is:
+The [deploy guide](/prisma-compute/deploy) covers build settings, frameworks, and troubleshooting.
 
-1. Sign in with `npx @prisma/cli@latest auth login`.
-2. Run `npx @prisma/cli@latest app deploy` from your app directory to get a live URL.
-3. Connect your app to [Prisma Postgres](/postgres) or another database with [environment variables](/compute/environment-variables).
-4. Redeploy to apply the environment variables.
-5. Keep deploying from the CLI, or [connect GitHub](/compute/github) to deploy on push.
+## Use with your agent
+
+To hand the full Prisma 7 stack to your coding agent, copy this prompt. The commands below install Prisma 7, not Prisma Next:
+
+<AgentPrompt>
+
+```text
+Set up the Prisma 7 stack: Prisma ORM 7, Prisma Postgres, and Prisma Compute.
+
+If I have not told you which framework template to use, stop and ask.
+
+1. Scaffold a new app non-interactively: `npx create-prisma@latest --name my-app --template [next|hono|nuxt|astro|nest|svelte|tanstack-start|elysia|turborepo] --provider postgresql --no-deploy`. Or add Prisma 7 to an existing app with `npx prisma@latest init --db`, which provisions a Prisma Postgres database; before that, check `npx @prisma/cli@latest auth whoami` and stop and ask me to run `auth login` if I am not signed in, because provisioning can open a browser.
+2. From the project directory, define a small schema in `prisma/schema.prisma`, then run `npx prisma migrate dev --name init` and `npx prisma generate`. If migrate dev asks to reset the database, stop and ask me first.
+3. Update the seed and app code to query the schema, and verify locally with the dev script.
+4. Deploy with Prisma Compute: check `npx @prisma/cli@latest auth whoami` first. If I am not signed in, stop and ask me to run `npx @prisma/cli@latest auth login`, because that step opens a browser. Then run `npx @prisma/cli@latest app deploy --create-project my-app --env .env` so DATABASE_URL reaches the deployment, and verify the deployed URL with curl.
+
+Current docs: https://www.prisma.io/docs/getting-started.md and https://www.prisma.io/docs/llms.txt.
+```
+
+</AgentPrompt>
 
 ## Next steps
 
 After setup, these pages are usually the next ones people need:
 
 - [Prisma Client overview](/orm/prisma-client)
-- [Generating Prisma Client](/orm/prisma-client/setup-and-configuration/generating-prisma-client)
 - [Prisma Migrate getting started](/orm/prisma-migrate/getting-started)
 - [Prisma schema overview](/orm/prisma-schema/overview)
-
-## If you want the fastest path
-
-- [Quickstart with Prisma Postgres](/prisma-orm/quickstart/prisma-postgres) if you want Prisma to provision the database layer for you
-- [Open Prisma Studio](/studio/getting-started) if you want to inspect and edit data visually once your app is running
-- [Review pricing](https://www.prisma.io/pricing) if you're evaluating Prisma Postgres or other paid workflows for a team
+- [Open Prisma Studio](/studio/getting-started) to inspect and edit data visually
+- [Review pricing](https://www.prisma.io/pricing) if you're evaluating Prisma Postgres for a team