Prisma Schema Editing
SkillAI & modelsSafe workflow for editing prisma/schema.prisma without corrupting model blocks, and for regenerating the Prisma client. Use whenever you need to add, remove, or modify a field or model in the Prisma schema.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Prisma Schema Editing skill
What this skill tells your AI
The instructions your AI receives, as published by mxz7/nypsi in .agents/skills/prisma-schema/SKILL.md and read by ahel’s review.
- When modifying
prisma/schema.prisma, replace the entire model block rather than inserting/editing partial lines near block boundaries (e.g. adding a field right before the closing}). Partial edits at model edges have corrupted the schema in past sessions (stray braces, misplaced fields). - Prefer reading the full model block first, then doing one
replace_string_in_fileswapping the wholemodel X { ... }block for the updated version. - After confirming schema changes are correct, run
npx prisma generateto refreshsrc/generated/prisma/types (imported via#generated/prisma). If a model delegate seems missing from the generated client (e.g.prisma.lotterynot existing) even though the schema has it, that's usually a stale generate - rerun it. - Do not create migrations yourself - the user handles
prisma migrate devonce all schema changes for a task are confirmed. Migrations created by the user should be committed to git; do not flag an existing committed migration merely because agents are prohibited from generating one.
Signals
- GitHub stars
- 69
- Forks
- 31
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
prisma-schema- Source
- github.com/mxz7/nypsi