本文へ移動
cccskills
無料GitHub で公開

prisma-next

Route a vague Prisma Next prompt to the right specific skill. Use for "help me with Prisma Next", "what is Prisma Next", "explain Prisma Next", "I'm new to PN", "where do I start", "what can I do with Prisma Next", "what can I do next with Prisma", "just ran createprisma", "tour of Prisma Next", "Prisma Next overview", and comparison questions like "Prisma Next vs Prisma 7", "PN vs Drizzle", "PN vs Kysely", "PN vs TypeORM". Do NOT use when the prompt clearly matches a workflow skill — adoption / quickstart / first-touch orientation / brownfield introspection, schema / contract editing, migration authoring (db update / migration plan / migrate), migration review on deploy / concurrent migrations, queries / db.orm / db.sql / TypedSQL, runtime / db.ts / middleware wiring, build / Vite plugin / Next.js plugin, debug / structured error envelopes / PN-* error codes, or feedback / bug report / feature request — load that sibling skill directly.

prisma/open-chat
インストール方法を見る

含まれるファイル（1）

  • SKILL.md5.2 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Prisma Next — Router

Edit your data contract. Prisma handles the rest.

This skill exists to disambiguate vague Prisma Next prompts. When the user hasn't yet committed to a specific workflow (e.g. "help me with Prisma Next", "explain how Prisma Next works", "I'm new to PN, where do I start?"), this skill fires and routes them to the right specific skill.

When to Use

  • The user has not yet stated a concrete task.
  • The user types a meta-question about Prisma Next ("what is Prisma Next?", "how does PN compare to Drizzle/Prisma 7?").
  • The user asks for a tour, an overview, or a starting point.

When Not to Use

  • The user named a workflow — use the matching skill directly:
    • Setting up a new project or adopting an existing DB → prisma-next-quickstart.
    • Editing the schema, adding a model, changing a field → prisma-next-contract.
    • Authoring a migration, fixing a planner error → prisma-next-migrations.
    • Reviewing what's about to run on merge, handling concurrent migrations → prisma-next-migration-review.
    • Writing a query → prisma-next-queries.
    • Wiring db.ts, middleware, environment config → prisma-next-runtime.
    • Build-system / dev-server plugin (Vite, Next.js, …) → prisma-next-build.
    • A specific error code or symptom → prisma-next-debug.
    • Reporting a bug or filing a feature request against Prisma Next → prisma-next-feedback.

Routing rules

If the user's prompt clearly matches one of the workflow skills, route there directly without asking.

Otherwise, ask one disambiguating question. Pick from:

  • "Are you new to Prisma Next and asking what you can do with it, or where to start?" (and any "what can I do with Prisma Next?" / "I just ran createprisma" variant) → prisma-next-quickstart (first-touch orientation path).
  • "Do you want to set up a new Prisma Next project, or wire it into an existing database?" → prisma-next-quickstart.
  • "Do you want to edit your data contract (add a model / field / relation), or work with the database (migrations, queries)?" → prisma-next-contract vs the others.
  • "Is this about authoring a migration, or about reviewing what's going to run on deploy?" → prisma-next-migrations vs prisma-next-migration-review.
  • "Is this about wiring Prisma Next into your build tool (Vite / Next.js / …), or about wiring db.ts and middleware at runtime?" → prisma-next-build vs prisma-next-runtime.
  • "What error or symptom are you seeing?" → prisma-next-debug.
  • "Do you want to report this as a bug to the Prisma Next team, or is this a feature request?" → prisma-next-feedback.

If you still can't tell which skill applies, ask the user what they want to do. Do not guess.

The canonical model (one paragraph)

Prisma Next is a contract-first data layer. You author a data contract (a contract.prisma file, or a TypeScript builder). The framework emits machine-readable artifacts (contract.json, contract.d.ts) and gives you three runtime surfaces on SQL targets: a typed SQL query builder (db.sql.from(...)), a typed ORM client (db.orm.User.select(...)), and a raw SQL escape hatch (db.sql.raw(...)). On MongoDB targets only the ORM lane exists, and its keys are collection storage names (db.orm.users) rather than PSL model names — prisma-next-queries § MongoDB ORM addressing covers the rule. Migrations are planned from the contract diff; you review them, optionally edit the migration.ts for data transforms, and apply.

Three steps the user does:

  1. Edit your data contract. (prisma-next-contract)
  2. The system plans the migrations for you. (prisma-next-migrations)
  3. If you need data migrations, you edit migration.ts and execute it. (prisma-next-migrations)

Everything else — queries, runtime wiring, build integration, debugging, feedback — sits on top of those three.

Checklist

  • If the prompt matches a specific workflow skill, route there without asking.
  • If the prompt is vague, ask one disambiguating question.
  • Do not attempt to answer the user's question from this skill — load the right specific skill first.
  • If the user describes a missing feature or a misbehaviour they want fixed, route to prisma-next-feedback.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

prisma-next-build

無料

Wire Prisma Next into the project's build system with the right build-tool plugin — Vite today via @prisma-next/vite-plugin-contract-emit (Vite 7 / 8); Next.js / Webpack / esbuild / Rollup / Turbopack are named as gaps rather than fabricated. Always offers the Vite plugin proactively when the project is using Vite. Use for vite plugin, vite-plugin, vite.config.ts, prismaVitePlugin, contract emit on save, HMR, hot reload contract, dev server, Next.js plugin, next plugin, withPrismaNext, webpack plugin, esbuild plugin, rollup plugin, build integration, dev server plugin, vite 7, vite 8.

日本語の概要は準備中です。原文の説明を表示しています。

prisma/open-chat232026年7月23日 更新

prisma-next-contract

無料

Edit the Prisma Next data contract — add models, fields, relations, indexes, enums, value objects (composite types), type aliases, namespaces (Postgres schemas), cross-contract foreign keys (cross-space FK), polymorphic types (`@@discriminator` / `@@base`), use extension namespaces (`pgvector.Vector(...)`, `cipherstash.EncryptedString(...)`), wire `prisma-next.config.ts` with `defineConfig` from the `@prisma-next/<target>/config` façade, and run `prisma-next contract emit`. Use for schema, models, fields, attributes, soft delete, paranoid, scopes, validations, callbacks, prisma schema, PSL, contract.prisma, contract.ts, contract.json, contract.d.ts, façade imports, `@prisma-next/postgres/config`, `@prisma-next/postgres/contract-builder`, `@prisma-next/postgres/control`, `@prisma-next/mongo/config`, `@prisma-next/mongo/contract-builder`, `extensions:`, `extensionPacks`, pgvector, cipherstash, postgis, paradedb, supabase, `@prisma-next/extension-supabase`, `@@control`, control policy, managed, tolerated, external, observed, PN-CLI-4002, PN-CLI-4003, PN-CLI-4011.

日本語の概要は準備中です。原文の説明を表示しています。

prisma/open-chat232026年7月23日 更新

prisma-next-debug

無料

Read a Prisma Next structured error envelope and route to the right recovery — code, domain, severity, why, fix, meta. Use for error, exception, my emit failed, my query won't typecheck, my query crashed, my migration won't apply, MIGRATION.HASH_MISMATCH, BUDGET.ROWS_EXCEEDED, BUDGET.TIME_EXCEEDED, RUNTIME.ABORTED, PLAN.HASH_MISMATCH, CONTRACT.MARKER_MISSING, PN-RUN-3001, PN-RUN-3002, PN-RUN-3030, PN-MIG-2001, PN-CLI-4011, PN-SCHEMA-0001, drift, capability missing, planner conflict, prisma studio, EXPLAIN, query log, db.end, db.close, script won't exit, hangs, close connection, pool.end, client is closed.

日本語の概要は準備中です。原文の説明を表示しています。

prisma/open-chat232026年7月23日 更新

prisma-next-extension-upgrade

無料

Upgrade Prisma Next in your extension. Bumps every `@prisma-next/*` dependency to the requested target (or npm `latest`), runs the per-transition upgrade instructions for the extension SPI (middleware lifecycle, codec / migration-tools / framework-components churn, seed-migration on-disk shape), verifies the pins are correctly exact via `prisma-next-check-pins`, runs the extension's own typecheck and tests, and commits each minor step on its own. Use when the user asks to "upgrade Prisma Next" in an extension package, or to update an extension's `@prisma-next/*` deps to a new minor.

日本語の概要は準備中です。原文の説明を表示しています。

prisma/open-chat232026年7月23日 更新

prisma-next-feedback

無料

Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing feature, this should be a feature, file this, this is a bug, this is broken, surprising behaviour, this doesn't work, file feedback, send feedback, capability gap, file via prisma-next-feedback, ask the team, talk to the team, talk to the Prisma team, talk to Prisma, Discord, Prisma Discord, Q&A, design feedback, is this the intended way, how should I do X, extension author question, extension author needs help.

日本語の概要は準備中です。原文の説明を表示しています。

prisma/open-chat232026年7月23日 更新

prisma-next-migration-review

無料

Review what Prisma Next migrations will run on merge or deploy, render the migration graph, resolve concurrent / diamond-convergence conflicts, and configure environment refs for CI. Use for "what migrations are going to run", "what runs on deploy", merge conflict, diamond convergence, concurrent migrations, migration status, ref management, staging, production, MIGRATION.DIVERGED, MIGRATION.NO_MARKER, MIGRATION.MARKER_NOT_IN_HISTORY, prisma migrate status, prisma migrate diff, prisma migrate resolve.

日本語の概要は準備中です。原文の説明を表示しています。

prisma/open-chat232026年7月23日 更新

prisma のスキルをすべて見る

このスキルの問題を報告する