docs(compute): centralize monorepo guidance

Author: AmanVarshney01

apps/docs/content/docs/(index)/prisma-compute/deploy.mdx

@@ -156,7 +156,7 @@ Make sure your project directory is a Git repository with a GitHub remote, then
 npx @prisma/cli@latest git connect
 ```
 
-`git connect` wires up the project this directory is linked to, which exists once you have deployed at least once. For monorepos and CI, see the [GitHub integration docs](/compute/github).
+`git connect` wires up the project this directory is linked to, which exists once you have deployed at least once. For a repository with several apps, see [Deploy a monorepo](/compute/monorepos). For integration details, see the [GitHub docs](/compute/github).
 
 ## Hand it to your agent
 
@@ -185,5 +185,6 @@ Notes for your agent:
 - [Branching](/compute/branching): how preview branches isolate work and map to your Git branches.
 - [Add environment variables](/compute/environment-variables) for configuration, secrets, and your database connection string.
 - [Deployments](/compute/deployments): promote, roll back, and inspect what you ship.
-- [GitHub integration](/compute/github): the full picture on deploy-on-push, monorepos, and cleanup.
+- [Deploy a monorepo](/compute/monorepos): configure, verify, and deploy several apps from one repository.
+- [GitHub integration](/compute/github): the full picture on deploy-on-push and cleanup.
 - [Read the full CLI getting-started guide](/compute/getting-started) for frameworks, project linking, and CI.

apps/docs/content/docs/compute/cli-reference.mdx

@@ -61,7 +61,7 @@ Manage apps and deployments for a project.
 | `app rollback`                | Roll back production to the previous deployment, without rebuilding       |
 | `app remove`                  | Remove the app from the current branch                                    |
 
-Promote and rollback switch the live endpoint between existing deployments; nothing is rebuilt, and env vars stay as resolved when each deployment was created. Most `app` commands also accept an optional `[app]` positional argument to pick a target from `prisma.compute.ts` when the config defines multiple apps.
+Promote and rollback switch the live endpoint between existing deployments; nothing is rebuilt, and env vars stay as resolved when each deployment was created. Most `app` commands also accept an optional `[app]` positional argument to pick a target from `prisma.compute.ts` when the config defines multiple apps. See [Deploy a monorepo](/compute/monorepos) for target setup and workflows.
 
 ### `app deploy` options
 

apps/docs/content/docs/compute/configuration.mdx

@@ -9,7 +9,7 @@ metaDescription: "Reference for the prisma.compute.ts file: declare your app's f
 `prisma.compute.ts` is an optional, committed file that declares what you deploy. [`app deploy`](/compute/cli-reference#app) already works with zero config (it detects your framework and builds), so reach for a config file when you want one of these:
 
 - **Reproducible deploys.** Pin the framework, port, and build settings so every deploy (yours, a teammate's, or [deploy-on-push](/compute/github)) does the same thing without re-passing flags.
-- **A monorepo.** Declare several apps in one repository and deploy them together, or one at a time.
+- **A monorepo.** [Declare several apps](/compute/monorepos) in one repository and deploy them together, or one at a time.
 - **Type safety.** Catch a typo'd field or an invalid framework in your editor, before you deploy.
 
 The file is read by `app deploy` and `app build`. It never selects your project, branch, or production; those stay explicit. It also does not configure a database; that stays on the [`--db` flag](/compute/cli-reference#app-deploy-options).
@@ -143,47 +143,7 @@ The config file's directory is treated as the project directory: the [`.prisma/l
 
 ## Monorepos
 
-Use `apps` instead of `app` to declare several apps in one repository, keyed by a target name. For an end-to-end setup with local builds, single-app deploys, deploy-all, and GitHub automation, see [Deploy a monorepo](/compute/monorepos).
-
-```ts title="prisma.compute.ts"
-import { defineComputeConfig } from "@prisma/compute-sdk/config";
-
-export default defineComputeConfig({
-  apps: {
-    api: {
-      root: "apps/api",
-      framework: "hono",
-      entry: "src/index.ts",
-    },
-    web: {
-      root: "apps/web",
-      framework: "nextjs",
-    },
-  },
-});
-```
-
-All the apps live in one project, deploying to the same branch. From here:
-
-- **Deploy everything** with a bare `app deploy`, which deploys every app in order. This is the default when no target is named or inferred:
-
-  ```npm
-  npx @prisma/cli@latest app deploy
-  ```
-
-- **Deploy one app** by naming its target, or by running from inside its `root` (the deepest matching root wins):
-
-  ```npm
-  npx @prisma/cli@latest app deploy api
-  ```
-
-  ```npm
-  cd apps/api && npx @prisma/cli@latest app deploy
-  ```
-
-When you deploy everything at once, per-app flags like `--framework` or `--entry` are rejected as ambiguous. Pass a target to apply them to one app. Project- and branch-level flags (`--branch`, `--db`, `--prod`, `--yes`) apply to the whole run.
-
-`app build` always targets a single app in a multi-app config. Unlike `deploy`, it has no all-apps form, so pass a target or run from inside the app's `root`.
+Use `apps` instead of `app` to declare several apps in one repository. Each map key is a CLI target, and every target accepts the same fields listed above. See [Deploy a monorepo](/compute/monorepos) for the complete config, directory layout, target selection, local builds, deploy-all behavior, and GitHub automation.
 
 ## How config and flags interact
 
@@ -203,4 +163,4 @@ A config that fails to load or validate stops the deploy before any remote work,
 - [CLI reference](/compute/cli-reference): every command, flag, and error code.
 - [Deploy your first app](/prisma-compute/deploy): the end-to-end quickstart.
 - [Environment variables](/compute/environment-variables): scoped configuration, secrets, and your database connection string.
-- [GitHub integration](/compute/github): deploy-on-push, including monorepos.
+- [GitHub integration](/compute/github): deploy-on-push and branch previews.

apps/docs/content/docs/compute/faq.mdx

@@ -57,7 +57,7 @@ No. Variables resolve at deploy time, so you need to redeploy for the app to pic
 
 ## How do I deploy from CI?
 
-Use a service token and explicit targets:
+Use a service token and name the remote project and app explicitly:
 
 ```bash
 PRISMA_SERVICE_TOKEN=... npx @prisma/cli@latest app deploy \
@@ -68,7 +68,7 @@ PRISMA_SERVICE_TOKEN=... npx @prisma/cli@latest app deploy \
   --no-interactive
 ```
 
-Passing every target explicitly keeps the run self-contained; `--json` makes the result parseable, and `--no-interactive` turns any would-be prompt into a structured error.
+Passing every selector explicitly keeps the run self-contained; `--json` makes the result parseable, and `--no-interactive` turns any would-be prompt into a structured error. For multiple config targets in one repository, follow [Deploy a monorepo](/compute/monorepos).
 
 ## Why did my production deploy fail with `PROD_DEPLOY_REQUIRES_FLAG`?
 

apps/docs/content/docs/compute/github.mdx

@@ -56,19 +56,9 @@ Once a project is connected:
 
 Connecting doesn't deploy anything on its own; it wires up automation for *future* events. To deploy right now, run `app deploy` yourself.
 
-## CI and monorepos
+## Monorepos
 
-Auto-deploy handles [monorepos that declare their apps in `prisma.compute.ts`](/compute/monorepos): one pushed commit fans out into a targeted build per app. For custom pipelines, or anywhere you want full control, set `PRISMA_SERVICE_TOKEN` and `PRISMA_PROJECT_ID`, then name the config target positionally:
-
-```bash title="CI"
-PRISMA_SERVICE_TOKEN=... PRISMA_PROJECT_ID=... \
-  npx @prisma/cli@latest app deploy web \
-  --branch "${GITHUB_HEAD_REF:-$GITHUB_REF_NAME}" \
-  --json \
-  --no-interactive
-```
-
-This keeps deploys deterministic and gives agents a structured result to read.
+A connected repository can deploy several Compute apps from each push. See [Deploy a monorepo](/compute/monorepos) for the root `prisma.compute.ts` config, build fan-out, target selection, and custom CI commands.
 
 ## What's not in beta
 

apps/docs/content/docs/compute/limitations.mdx

@@ -38,7 +38,7 @@ Prisma Compute is in [Public Beta](/console/more/feature-maturity#public-beta).
 ## GitHub
 
 - GitHub is the only supported provider, and a project connects to one repository.
-- Auto-deploy supports multiple apps declared in `prisma.compute.ts`: one push build fans out into a targeted build per app. CI with a service token remains available when you need full control.
+- Auto-deploy supports [multiple apps declared in a monorepo config](/compute/monorepos).
 - The webhook path is branch- and push-driven. There are no PR comments or PR status automation.
 
 ## Domains