Prisma Next — Feedback (Bug Reports, Feature Requests, Team Q&A)
Edit your data contract. Prisma handles the rest.
This skill is the
terminal
of the capability-gap routing pattern. Every other Prisma Next skill's
What Prisma Next doesn't do yet
entries route here when the user wants the gap closed; the skill also fires directly on prompts like
"this is a bug"
,
"file an issue"
,
"feature request"
,
"can I ask the team about this?"
,
"how should I integrate X with Prisma Next?"
.
The skill's job is to pick the
right channel
— GitHub issue or Discord — and then either produce a
structured, public-safe
issue body (no secrets, no proprietary schema) the framework team can act on, or hand the user a direct link to the Prisma Discord for synchronous Q&A. Submission to GitHub never happens without explicit user confirmation.
Canonical channels:
GitHub Issues
(bugs + concrete feature requests):
https://github.com/prisma/prisma-next/issues/new/choose
Prisma Discord
(Q&A, design feedback, direct team contact — including extension authors):
https://pris.ly/discord
When to Use
A capability-gap entry from another
prisma-next-*
skill fired and the user said
"yes, file the feature request"
.
User says
"this is a bug"
,
"file this"
,
"report this"
,
"file an issue against PN"
,
"send feedback"
,
"this should be a feature"
.
User describes an unexpected behaviour — wrong exit code, error message that didn't match what happened, type signature that doesn't match runtime behaviour, planner refused a migration that looked safe — and wants it on the framework team's radar.
User asks
"can I ask the Prisma team about this?"
,
"is there somewhere I can talk to the team?"
,
"is this the intended way to do X?"
,
"how should I integrate
prisma-next-feedback
安装
npx skills add https://github.com/prisma/prisma-next --skill prisma-next-feedback