Skip to content

Enhance documentation clarity for prisma-next repo #7881

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ankur-arch wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Enhance documentation clarity for prisma-next repo #7881

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2a9af5e
Enhance documentation clarity for prisma-next repo
ankur-arch May 8, 2026
ceca6a6
Merge branch 'main' into ankur-arch-patch-1
ankur-arch May 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,8 @@ Clone [`prisma/prisma-next`](https://pris.ly/pn-gh), point your coding agent at

The repo is dense with architecture docs, architecture decision record (ADRs), SPI READMEs, and reference extensions: enough context that an agent can absorb it in seconds and scaffold a working pack from your description alone, without you reading a line of it first.

The repo is packed with architecture docs, architecture decision records (ADRs), SPI READMEs, and reference extensions. Together, they give agents enough context to understand the system in seconds and scaffold a working pack from your description alone, without you having to read through the docs first. You can also browse the docs yourself [here](https://github.com/prisma/prisma-next/tree/main/docs).
Comment on lines 128 to +130
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot May 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicated “fastest way to start” paragraph and keep one tightened version.

Line 130 repeats the same message already stated on Line 128, so the section now feels redundant. Keep a single paragraph and include the docs link there.

Suggested edit 
-The repo is dense with architecture docs, architecture decision record (ADRs), SPI READMEs, and reference extensions: enough context that an agent can absorb it in seconds and scaffold a working pack from your description alone, without you reading a line of it first.
-
-The repo is packed with architecture docs, architecture decision records (ADRs), SPI READMEs, and reference extensions. Together, they give agents enough context to understand the system in seconds and scaffold a working pack from your description alone, without you having to read through the docs first. You can also browse the docs yourself [here](https://github.com/prisma/prisma-next/tree/main/docs).
+The repo is packed with architecture docs, architecture decision records (ADRs), SPI READMEs, and reference extensions: enough context for agents to understand the system in seconds and scaffold a working pack from your description alone, without you needing to read the docs first. If you want to browse them, start [here](https://github.com/prisma/prisma-next/tree/main/docs).
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
The repo is dense with architecture docs, architecture decision record (ADRs), SPI READMEs, and reference extensions: enough context that an agent can absorb it in seconds and scaffold a working pack from your description alone, without you reading a line of it first.
The repo is packed with architecture docs, architecture decision records (ADRs), SPI READMEs, and reference extensions. Together, they give agents enough context to understand the system in seconds and scaffold a working pack from your description alone, without you having to read through the docs first. You can also browse the docs yourself [here](https://github.com/prisma/prisma-next/tree/main/docs).
The repo is packed with architecture docs, architecture decision records (ADRs), SPI READMEs, and reference extensions: enough context for agents to understand the system in seconds and scaffold a working pack from your description alone, without you needing to read the docs first. If you want to browse them, start [here](https://github.com/prisma/prisma-next/tree/main/docs).
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx`
around lines 128 - 130, Remove the duplicated "fastest way to start" paragraph
in apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx by
keeping a single tightened version that includes the docs link; specifically,
locate the repeated paragraph that starts with "The repo is dense with
architecture docs..." (the duplicate at the later occurrence) and delete the
second instance so only one concise paragraph remains that includes the
https://github.com/prisma/prisma-next/tree/main/docs link.


The result is normal TypeScript you can read, edit, and iterate on like any other code, and it's dramatically faster than building one by hand from documentation.

If you'd rather start from a known-good template yourself, pick the existing extension closest to what you want and copy it:
Expand Down
Loading