chore(prisma-compute): deduplicate restated guidance

Author: AmanVarshney01

prisma-compute/SKILL.md

@@ -162,7 +162,7 @@ Use this skill for:
 - `deploy-json-for-agents` - Use `--json --no-interactive` for scripts and agent-readable output.
 - `deploy-create-project` - Use `--create-project <name>` only when the user wants deploy to create and link a new project; it conflicts with `--project` and `PRISMA_PROJECT_ID`.
 - `deploy-ops-targets` - App show/open/logs/list-deploys/promote/rollback/remove and domain commands can also accept `[app]` targets from `prisma.compute.ts`.
-- `deploy-report-cli-bugs` - When a `@prisma/cli` command crashes (`UNEXPECTED_ERROR`) or fails in a way you cannot resolve, report it with `bunx @prisma/cli@latest feedback "<command>: <error summary>"`. Crash envelopes in `--json` include the exact pre-filled command in `nextActions`; run it as-is. Reports are anonymous and carry only the message plus CLI, node, and OS versions; never include secrets, URLs with credentials, or user data in the message.
+- `deploy-report-cli-bugs` - On `UNEXPECTED_ERROR` or an unresolvable failure, report it with the feedback command; see "Send Feedback and Report CLI Issues" above.
 
 ### 8. SDK and API
 
@@ -188,9 +188,5 @@ Use this skill for:
 - Do not bury Compute deployment guidance in the generic `prisma-cli` skill.
 - Do not run `create-prisma` inside an existing app just to deploy it; use the generated `compute:deploy` script or `@prisma/cli app deploy`.
 - Do not tell users that every `create-prisma` template can auto-deploy.
-- Do not put Compute deploy defaults in `prisma.config.ts`; use `prisma.compute.ts`.
 - Do not deploy with placeholder `DATABASE_URL` values.
 - Do not assume `next start` is the Compute runtime path; Next.js deploys need standalone output.
-- Do not expose secret values from `.env`, CLI output, Management API responses, or logs.
-- Do not assume a stored OAuth login means the desired workspace is active; inspect or switch it explicitly.
-- Do not auto-switch to another cached workspace after logout or auth refresh failure.

prisma-compute/references/frameworks.md

@@ -161,7 +161,6 @@ Project expectations:
 - `src/main.ts` or the compiled runtime must start an HTTP server
 - read `process.env.PORT` and default to the same port used by `--http-port`
 - omit the host argument in `app.listen(port)` or pass `"0.0.0.0"`; do not pass `"localhost"` or `"127.0.0.1"`
-- a `build` block is optional for NestJS; the framework strategy supplies the build/output defaults, and a committed `build` block overrides them
 - use `app build --build-type nestjs` for a Compute artifact check; `app run --build-type nestjs` is not supported, so use the Nest dev server locally
 
 Example runtime shape:
@@ -234,7 +233,7 @@ export default defineComputeConfig({
 });
 ```
 
-Nuxt uses Nitro output at `.output/server/index.mjs`. Keep the Nitro preset compatible with a Node server runtime. A `build` block is optional for Nuxt: the framework strategy supplies the build command and output, and a committed `build` block overrides them.
+Nuxt uses Nitro output at `.output/server/index.mjs`. Keep the Nitro preset compatible with a Node server runtime.
 
 ## Astro
 
@@ -269,8 +268,6 @@ export default defineConfig({
 })
 ```
 
-A `build` block is optional for Astro: the framework strategy supplies the build command and output, and a committed `build` block overrides them.
-
 ## Bun, Elysia, and Plain Source Servers
 
 Use the Bun deploy key for app shapes without a dedicated `--framework` value:

prisma-compute/references/troubleshooting.md

@@ -432,4 +432,4 @@ When a CLI failure survives the checks above, or a command crashes with `UNEXPEC
 bunx @prisma/cli@latest feedback "app deploy crashed: <first error line>"
 ```
 
-Crash output points here on its own: human mode prints a `Tell us what happened:` hint, and `--json` crash envelopes carry the exact pre-filled command as a `recover` entry in `nextActions`; prefer running that command verbatim. Feedback is anonymous and attaches only the CLI version, node version, and OS platform/arch. Do not put secrets, connection URLs, or tokens in the message.
+Prefer the pre-filled command from a `--json` crash envelope's `nextActions` verbatim. Anonymous; never put secrets, connection URLs, or tokens in the message.