fix: clarify studio better

[ankur-arch]

Summary by CodeRabbit

• Documentation
  • Added new getting started documentation section for MySQL database quickstart workflow.
  • Updated Prisma Studio documentation to reflect Prisma 7's new standalone Studio capabilities that operate independently from Prisma ORM and perform direct database introspection.
  • Enhanced Studio usage examples with improved database connection configuration guidance and updated command examples for different use cases.

[github-actions]

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

[coderabbitai]

Walkthrough

Updates Prisma Studio documentation across three files to reflect Prisma 7's standalone Studio architecture. Changes clarify that the new Studio introspects databases directly without requiring a Prisma schema file, update configuration details to reference prisma.config.ts, and adjust usage examples. Minor content additions included in the MySQL quickstart section.

Changes

Cohort / File(s)	Summary
Quickstart Documentation content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx	Inserted new "Create a new project" documentation section with surrounding spacing.
Prisma Studio Core Documentation content/200-orm/400-tools/06-prisma-studio.mdx	Refactored Studio documentation to emphasize Prisma 7's standalone, schema-less architecture; updated prerequisites, configuration references (prisma.config.ts), and usage examples to reflect direct database introspection; clarified legacy Studio status; removed Prisma schema file dependency claims throughout.
PostgreSQL Studio Guide content/250-postgres/300-database/675-prisma-studio/index.mdx	Updated Studio invocation command to explicitly include database URL parameter; adjusted spacing and note formatting.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Primary focus: Verify that the Prisma Studio documentation in content/200-orm/400-tools/06-prisma-studio.mdx accurately represents the schema-less, direct-introspection behavior of Prisma 7's new standalone Studio and that all configuration references to prisma.config.ts align with current product behavior.
• Secondary focus: Confirm that the PostgreSQL example command with explicit URL parameter correctly demonstrates the new Studio usage pattern.

Possibly related PRs

• fix: add SQLite notes #7277: Updates the same 06-prisma-studio.mdx file with configuration and prerequisite changes for Prisma Studio documentation.
• feat: add mentions of new Prisma Studio #7270: Modifies both 06-prisma-studio.mdx and the PostgreSQL Studio guide, overlapping with the same documentation files updated here.
• Docs for v6.17.0 #7133: Makes related changes to Prisma Studio documentation and PrismaConfig studio setting configuration details.

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'fix: clarify studio better' is vague and generic. While it touches on the changes made to Studio documentation, 'clarify studio better' lacks specificity about which aspects were clarified or what improvements were made.	Revise the title to be more specific: e.g., 'docs: update Prisma Studio documentation for version 7' or 'docs: clarify Studio's standalone mode and database introspection'. This would better convey the scope of documentation updates.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

• This PR does not change any pages in a way that would require a redirect.

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	8fae296
Status:	✅  Deploy successful!
Preview URL:	https://f1f3714f.docs-51g.pages.dev
Branch Preview URL:	https://ankur-code-rabbit-patch.docs-51g.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

content/200-orm/400-tools/06-prisma-studio.mdx (1)

14-40: Rewrite Prerequisites section—both options contain architectural errors in Prisma 7.

The documentation misrepresents how Prisma Studio actually works:

1. Option 1 (line 23): --url flag does not exist for prisma studio. This command will fail when users try it. Studio requires a schema.prisma file with a datasource block to read the database connection.

2. Option 2 (line 32): Misidentifies the configuration file. The documentation states Studio requires prisma.config.ts, but actually:

   • Studio reads from schema.prisma (with datasource pointing to your database via env var or literal)
   • prisma.config.ts is optional—only needed if customizing Studio's adapter behavior
   • The actual command is: npx prisma studio or npx prisma studio --schema=path/to/schema.prisma

For standalone use, users should point Studio to a schema.prisma file (not use a non-existent --url flag). For programmatic/embedded setups, use @prisma/studio-core with a runtime connection string.

Revise both options to reflect the actual Prisma 7 Studio architecture: Studio always introspects a database, but it needs either a schema.prisma file (CLI) or programmatic configuration—not --url and not prisma.config.ts for typical usage.

🧹 Nitpick comments (1)

content/200-orm/400-tools/06-prisma-studio.mdx (1)

8-12: Clarify "SQL-driven" terminology for accuracy. The description mixes two concepts: "SQL-driven" (line 10) and "introspects your database directly" (line 10). The latter is clearer—Studio reads the database schema directly without requiring a Prisma schema file. Consider whether "SQL-driven" adds clarity or creates ambiguity about how Studio determines the schema structure. If it refers to internal implementation details, consider omitting it in favor of the more user-facing concept of real-time introspection.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf88d09 and 8fae296.

📒 Files selected for processing (3)

• content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx (1 hunks)
• content/200-orm/400-tools/06-prisma-studio.mdx (3 hunks)
• content/250-postgres/300-database/675-prisma-studio/index.mdx (1 hunks)

🧰 Additional context used

🧠 Learnings (4)

📚 Learning: 2025-10-09T21:32:50.340Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.

Applied to files:

• content/250-postgres/300-database/675-prisma-studio/index.mdx
• content/200-orm/400-tools/06-prisma-studio.mdx

📚 Learning: 2025-10-08T16:23:00.388Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".

Applied to files:

• content/250-postgres/300-database/675-prisma-studio/index.mdx
• content/200-orm/400-tools/06-prisma-studio.mdx
• content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx

📚 Learning: 2025-08-11T09:40:55.237Z

Learnt from: ankur-arch
Repo: prisma/docs PR: 7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.

Applied to files:

• content/200-orm/400-tools/06-prisma-studio.mdx

📚 Learning: 2025-10-08T16:23:00.388Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.

Applied to files:

• content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Check internal links
• GitHub Check: Cloudflare Pages

🔇 Additional comments (4)

content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx (1)

30-32: Section addition is well-structured. The new step integrating the <CreateProject /> component fits logically into the workflow and uses proper sentence case for the heading. This reuses the shared component consistently with other quickstart guides.

content/250-postgres/300-database/675-prisma-studio/index.mdx (1)

13-13: Clarifies Postgres-specific Studio invocation. The explicit --url flag with a full connection string makes the configuration clear for Postgres users, and the updated note appropriately cross-links to the general ORM Studio docs for other databases.

Also applies to: 20-20

content/200-orm/400-tools/06-prisma-studio.mdx (2)

43-59: Usage examples are clear and well-structured. The parallel presentation of standalone and ORM workflows makes the distinction intuitive. Line 59's explanation of real-time introspection and schema independence reinforces the key architectural shift. Pending confirmation of CLI flag validity from the Prerequisites section review.

---

61-186: Existing content aligns with new architecture. The features, database support, and troubleshooting sections remain valid and consistent with the new introspection-based design. Line 127 appropriately references "introspects it directly from your database," reinforcing the architectural messaging.