AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Dev Prisma

skill-christopherlouet-claude-base-dev-prisma · by christopherlouet

Development with Prisma ORM (schema, migrations, type-safe queries, Accelerate, transactions). Trigger when the user wants to add a model, create a migration, optimize Prisma queries, or when schema.prisma is detected in the project.

No reviews yet
0 installs
38 views
0.0% view→install

Install

$ agentstack add skill-christopherlouet-claude-base-dev-prisma

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-christopherlouet-claude-base-dev-prisma)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Dev Prisma? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Prisma ORM (pointer)

Prisma publishes the canonical agent skill at prisma/skills — maintained by the Prisma team, in sync with v7 (ESM-only, driver adapters, prisma.config.ts). The vendor reference stays current with every release; the prior foundation skill (418 lines) drifted on each Prisma version bump.

Delegate to the vendor skill

# Prisma's preferred path (verify on their README):
npx skills add prisma/skills

# Fallback — clone and copy:
git clone --depth 1 https://github.com/prisma/skills ~/dev/vendor-skills/prisma
# Skill content lives in CLAUDE.md / AGENTS.md per their convention.

Recipe entry: [docs/recipes/recommended-vendor-skills.md](../../../docs/recipes/recommended-vendor-skills.md) §"Prisma — prisma/skills". Reduction rationale: [specs/foundation-positioning-review/spec.md](../../../specs/foundation-positioning-review/spec.md) Wave 1.

Foundation-unique angle preserved: cross-cutting discipline

The vendor covers the Prisma API surface. The foundation enforces version-agnostic conventions that survive across releases:

  • Security: never select: { passwordHash: true } or any sensitive column without explicit need; default to select over include for security + perf — cross-ref .claude/rules/security.md.
  • TDD with a real DB: integration tests hit a real test database (Docker Compose pattern), never a Prisma mock — cross-ref the dev-tdd skill.
  • Postgres interop: if the stack uses Supabase, Prisma operates against the same Postgres — cross-ref the dev-supabase skill (Supabase RLS coexists with Prisma queries).

Foundation rules preserved

  • NEVER use prisma migrate dev in production. Always prisma migrate deploy.
  • prisma generate MUST run after every schema change. Add it to the CI build step.
  • Singleton PrismaClient (HMR-safe globalThis pattern in dev) — avoid connection leaks.
  • YOU MUST add an index on every foreign key and on every column in frequent WHERE clauses.
  • YOU MUST use select instead of include when you know the fields (security + perf).
  • NEVER commit .env with DATABASE_URL. Always .env.example with placeholders.
  • NEVER rename a field in one migration. Two steps: add new column → backfill → remove old column (avoids prod downtime).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.