prisma-orm-v7-skills▌
gocallum/nextjs16-agent-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
$22
Links
- Upgrade guide (v7): https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7
- Prisma Config reference: https://www.prisma.io/docs/orm/reference/prisma-config-reference
- Prisma Client Extensions: https://www.prisma.io/docs/orm/prisma-client/client-extensions
- Prisma 7 migration prompt (AI agents): https://www.prisma.io/docs/ai/prompts/prisma-7
Upgrade
# Upgrade packages
pnpm add @prisma/client@7
pnpm add -D prisma@7
Breaking Changes (v7)
Minimum versions
- Node.js: 20.19.0+ (and 22.x)
- TypeScript: 5.4.0+
Prisma is now ESM
- Prisma ORM ships as ES modules.
- Set
"type": "module"inpackage.json(or migrate your project to ESM). - TypeScript projects must compile/resolve ESM (guide example:
module: ESNext,target: ES2023,moduleResolution: node).
Prisma schema + generation changes
- Generator provider:
prisma-client-js→prisma-client. outputis required ingenerator client.- Prisma Client is no longer generated into
node_modulesby default. - After
npx prisma generate, update imports to your generated output path (example:import { PrismaClient } from './generated/prisma/client').
Schema datasource deprecations:
url,directUrl,shadowDatabaseUrlinschema.prismaare deprecated.- Move datasource config to
prisma.config.ts(Prisma Config). - If you used
directUrlfor migrations, set the CLI migration connection string inprisma.config.ts.
Driver adapters required for Prisma Client (new instantiation)
- Prisma Client creation now requires a driver adapter for all databases.
- Example adapters:
- Postgres:
@prisma/adapter-pg(usePrismaPgwith a direct DB connection string) - SQLite:
@prisma/adapter-better-sqlite3
- Postgres:
Prisma Accelerate users (v6 → v7)
- Do not pass
prisma://orprisma+postgres://(Accelerate URLs) to a driver adapter. - Keep the Accelerate URL and instantiate Prisma Client with the Accelerate extension instead.
Env vars are not loaded by default
- Prisma CLI no longer auto-loads
.envfiles in v7. - Explicitly load env vars (for example
import 'dotenv/config'inprisma.config.ts, or load env in your scripts). - Bun users: no change required (bun auto-loads
.env).
Prisma CLI config moved to prisma.config.ts
- Prisma Config is now the default place to configure how Prisma CLI behaves.
- Place
prisma.config.tsat the project root (next topackage.json). - Configure schema path, migrations path/seed, and datasource URL there.
Client middleware removed
prisma.$use(...)is removed.- Migrate middleware logic to Prisma Client Extensions.
Metrics removed from Client Extensions
- The Metrics preview feature is removed in v7.
- Use your database driver/adapter or implement custom counters via extensions.
Migrate/seed/generate behavior changes
- Automatic seeding after
prisma migrate dev/prisma migrate resetis removed.- Run seeding explicitly:
pnpm prisma db seed(orpnpm exec prisma db seed).
- Run seeding explicitly:
--skip-generateand--skip-seedflags removed.prisma migrate devandprisma db pushno longer runprisma generateautomatically.- Run
pnpm prisma generate(orpnpm exec prisma generate) explicitly.
- Run
Prisma-specific env vars removed
- Removed env vars:
PRISMA_CLI_QUERY_ENGINE_TYPEPRISMA_CLIENT_ENGINE_TYPEPRISMA_QUERY_ENGINE_BINARYPRISMA_QUERY_ENGINE_LIBRARYPRISMA_GENERATE_SKIP_AUTOINSTALLPRISMA_SKIP_POSTINSTALL_GENERATEPRISMA_GENERATE_IN_POSTINSTALLPRISMA_GENERATE_DATAPROXYPRISMA_GENERATE_NO_ENGINEPRISMA_CLIENT_NO_RETRYPRISMA_MIGRATE_SKIP_GENERATEPRISMA_MIGRATE_SKIP_SEED
MongoDB support
- Prisma ORM 7 does not support MongoDB yet; stay on Prisma ORM 6 if you need MongoDB.
Upgrade Checklist (quick)
- Upgrade packages; confirm Node/TypeScript versions.
- Move to ESM (or adjust your runtime/build to consume ESM).
- Update
schema.prismagenerator toprovider = "prisma-client"and setoutput. - Run
pnpm prisma generateand update Prisma Client imports to the generated output path. - Add
prisma.config.tsat repo root; move datasource config and load env explicitly. - Update Prisma Client instantiation to use a driver adapter (unless using Accelerate).
- Update workflows: run
pnpm prisma generateandpnpm prisma db seedexplicitly.
How to use prisma-orm-v7-skills on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add prisma-orm-v7-skills
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches prisma-orm-v7-skills from GitHub repository gocallum/nextjs16-agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate prisma-orm-v7-skills. Access the skill through slash commands (e.g., /prisma-orm-v7-skills) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★57 reviews- ★★★★★Henry Desai· Dec 28, 2024
I recommend prisma-orm-v7-skills for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Li Chen· Dec 24, 2024
prisma-orm-v7-skills has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Li Gill· Dec 20, 2024
Keeps context tight: prisma-orm-v7-skills is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Lucas Jackson· Dec 8, 2024
Solid pick for teams standardizing on skills: prisma-orm-v7-skills is focused, and the summary matches what you get after install.
- ★★★★★Li Yang· Dec 8, 2024
We added prisma-orm-v7-skills from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yusuf Khanna· Nov 27, 2024
prisma-orm-v7-skills has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Meera Diallo· Nov 27, 2024
Useful defaults in prisma-orm-v7-skills — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Li Nasser· Nov 15, 2024
Solid pick for teams standardizing on skills: prisma-orm-v7-skills is focused, and the summary matches what you get after install.
- ★★★★★Naina Mehta· Nov 3, 2024
I recommend prisma-orm-v7-skills for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Li Ghosh· Oct 22, 2024
Keeps context tight: prisma-orm-v7-skills is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 57