revert: keep --db out of the skill; database setup stays explicit

Author: AmanVarshney01

prisma-compute/SKILL.md

@@ -138,7 +138,7 @@ Use this skill for:
 - `env-cli-token-name` - `@prisma/cli` uses `PRISMA_SERVICE_TOKEN` for service-token auth.
 - `env-branch-scope` - Branch deploys, branch env vars, and branch databases must use the same branch name; pass `--branch <git-name>` explicitly when targeting a preview branch.
 - `env-production-vs-preview` - Use `--role production` for production env, `--role preview` for preview template env, and `--branch <git-name>` for branch-specific overrides.
-- `env-db-explicit` - Keep database and env wiring explicit: `app deploy --db` creates one branch-scoped database shared by every app on the branch and wires `DATABASE_URL`/`DIRECT_URL` (`--db --yes` in CI; `--yes` alone never creates one; `--no-db` skips). Everything else goes through database and project env commands, and deploys never run migrations, seed data, or create one database per app automatically.
+- `env-db-explicit` - Keep database and env wiring explicit through database and project env commands; deploy examples should not add database setup, and deploys do not run migrations, seed data, or create one database per app automatically.
 
 ### 7. Deploy Operations
 

prisma-compute/references/app-deploy-cli.md

@@ -156,7 +156,7 @@ bunx @prisma/cli@latest project env remove STRIPE_KEY --role preview
 
 `app deploy --env .env` loads environment variables from a file for the deployment. A config-backed deploy can instead load env through `prisma.compute.ts` `env`. Neither path is a migration command or seed command.
 
-Database setup is not part of `prisma.compute.ts`. Deploy-time setup goes through explicit flags: `app deploy --db` creates one branch-scoped Prisma Postgres database (shared by all apps on the branch) and wires `DATABASE_URL`/`DIRECT_URL` through project env; `--yes` alone never creates a database, so CI passes `--db --yes`; `--no-db` skips setup. `--db` and `--no-db` are mutually exclusive, and deploys still never run migrations or seed data. Outside deploy, keep database intent explicit with `database create` and project env commands. Treat any generated connection URL as a one-time secret.
+Database setup is not part of `prisma.compute.ts`. Keep database intent explicit with `database create` and project env commands. Do not add database setup to deploy examples. Treat any generated connection URL as a one-time secret.
 
 Database and env guardrails: