prisma-next-contract
Build Prisma Next Data Contracts
Complex Prisma Next contracts can fail when schemas, extensions, and configuration drift. This skill guides contract edits, configuration, diagnostics, and artifact emission.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "prisma-next-contract" from https://skillstore.io/skills/prisma-prisma-next-contract.md and its manifest at https://skillstore.io/api/skills/prisma-prisma-next-contract/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "prisma-next-contract". Add posts with authors, unique titles per author, and cascading deletion.
Expected outcome:
The contract gains a Post model, an owning author relation, a composite unique constraint, and an author index. Emitted artifacts are refreshed.
Using "prisma-next-contract". Add 1536-dimension embeddings with pgvector.
Expected outcome:
The configuration registers the pgvector control descriptor. The contract uses its vector type, and TypeScript authoring registers the matching pack.
Using "prisma-next-contract". Explain why contract emit returns PN-CLI-4011.
Expected outcome:
The contract references an extension namespace that configuration does not register. Add the matching extension descriptor, then emit the contract again.
Security Audit
SafeAll 153 static alerts are false positives caused by Markdown formatting, documented Prisma commands, schema identifiers, and extension type names. No prompt injection, malicious intent, credential exfiltration, or unsafe executable implementation was found.
Risk Factors
⚙️ External commands (50)
🔑 Env variables (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/prisma-prisma-next-contract/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/prisma-prisma-next-contract?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/prisma-prisma-next-contract?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prisma-prisma-next-contract/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/prisma-prisma-next-contract.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
prisma. (2026). prisma-next-contract security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/prisma-prisma-next-contract/audits/1BibTeX citation
@techreport{prisma-prisma-prisma-next-contract-2026,
author = {prisma},
title = {prisma-next-contract security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/prisma-prisma-next-contract/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "prisma-next-contract security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "prisma"
date-released: "2026-08-17"
url: "https://skillstore.io/skills/prisma-prisma-next-contract/audits/1"
identifiers:
- type: other
value: "skillstore:prisma-prisma-next-contract:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Extend an application schema
Add models, relations, constraints, and indexes while preserving the established contract layout.
Configure database extensions
Register extension descriptors and use namespaced types such as vectors or encrypted strings.
Model shared contract spaces
Define namespaces, external tables, control policies, and cross-contract foreign keys.
Try These Prompts
Add a {model_name} model to my Prisma Next contract with these fields: {fields}. Preserve the current authoring format.Create a {relation_type} relation between {source_model} and {target_model}. Add explicit referential actions and useful indexes.Configure {extension_name} for this Prisma Next project and add a field using {extension_type}. Update every required descriptor surface.Design a Prisma Next contract for {domain}. Include namespaces, value objects, polymorphism, control policies, and cross-contract references where justified.Best Practices
- Read prisma-next.config.ts first and edit only the configured contract source.
- Use public target and extension facade imports in user-authored files.
- Emit after every source change and verify both generated artifacts changed.
Avoid
- Do not edit contract.json or contract.d.ts because emission replaces manual changes.
- Do not use internal Prisma Next package imports from application code.
- Do not treat a field rename as a safe automatic drop and add.