Merge branch 'main' into add-mysql-import-guide

content/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx

@@ -385,7 +385,7 @@ Both `posts` and `author` are relation fields because their types are not scalar
 
 Also note that the [annotated relation field](#annotated-relation-fields) `author` needs to link the relation scalar field `authorId` on the `Post` model inside the `@relation` attribute. The relation scalar field represents the foreign key in the underlying database.
 
-The other relation field called `posts` is defined purely on a Prisma ORM-level, it doesn't manifest in the database.
+Both the relation fields (i.e. `posts` and `author`) are defined purely on a Prisma ORM-level, they don't manifest in the database.
 
 ### Annotated relation fields
 

content/250-postgres/900-troubleshooting.mdx

@@ -53,3 +53,34 @@ To remove this warning and generate Prisam Client without the query engine, you
 ```
 npx prisma generate --no-engine
 ```
+
+## Workspace plan limit reached when running `prisma init --db`
+
+### Problem
+
+When running the command:
+
+```terminal
+npx prisma@latest init --db
+```
+
+You may encounter the following error message in your logs:
+
+```
+Workspace plan limit reached for feature "Project".
+```
+
+### Cause
+
+Your default [workspace](/platform/about#workspace) project limit has been reached.
+
+### Solution
+
+To resolve this issue, consider the following options:
+
+- Configure a different Workspace as your default—one that has available capacity for additional projects.
+- Delete unused projects or databases from your current default Workspace to free up space.
+- Ensure that you are logged into the correct account in the Prisma CLI. For more details on authentication and account management, please refer to the [Prisma CLI documentation](/platform/platform-cli/commands#authentication).
+- [Upgrade to a plan](/platform/about#billing) that supports more projects in your default Workspace.
+
+Implementing one or more of these solutions should help you overcome the plan limit issue.

content/800-guides/120-using-prisma-in-cursor.mdx

@@ -165,6 +165,10 @@ This file ensures consistent and maintainable code generation, reducing manual i
 
 Cursor’s [context-aware](https://docs.cursor.com/context/) capabilities let you add specific websites, files, folders or documentation to enhance its understanding of your project. By adding your `schema.prisma` file as context, you enable Cursor to generate more accurate queries, tests, and seed data based on your database schema.
 
+### Add Prisma docs `llm.txt` file as `@Docs` context
+
+To improve Cursor’s understanding of Prisma-related suggestions in your project, include the [`/llms.txt`](https://llmstxt.org/) markdown file as context. This file offers a concise overview, useful guidance, and links to detailed Prisma documentation—all optimized for LLM processing. Simply navigate to the [url](/llms.txt) and add it as a `@Docs` resource in your Cursor configuration.
+
 ### Adding additional Prisma documentation
 
 Cursor already includes built-in context from Prisma documentation, so you don't need to add anything to make us of our docs! You can view the existing resources Cursor uses [here](https://raw.githubusercontent.com/getcursor/crawler/main/docs.jsonl). 

package.json

@@ -42,7 +42,7 @@
     "@docusaurus/types": "^3.5.2",
     "prettier": "3.4.2",
     "typescript": "~5.7.3",
-    "wrangler": "^3.106.0"
+    "wrangler": "^3.107.3"
   },
   "browserslist": {
     "production": [