[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ENTEFBFZ6ME4HF6F5392AX":3,"skill-same:01M7ENTEFBFZ6ME4HF6F5392AX":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7ENTEFBFZ6ME4HF6F5392AX","prisma-postgres-setup",null,"Obtain or reuse a Prisma Postgres database and connect an application. Use for \"set up Prisma Postgres\", \"connect my app to Prisma Postgres\", or Prisma Postgres setup in v0 and Vercel Marketplace. Hands Prisma ORM configuration to prisma-orm-setup; honors an explicit driver, alternative ORM, or database-only choice.","aandremillan10\u002Fhealth-ier","aandremillan10","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F115795929?v=4","01M7ENHS9EHES711QABVQPHFWA","01M7ENHSA0P9ESB83XTN263PX8",0,"MIT","https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-postgres-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\r\nname: prisma-postgres-setup\r\ndescription: Obtain or reuse a Prisma Postgres database and connect an application. Use for \"set up Prisma Postgres\", \"connect my app to Prisma Postgres\", or Prisma Postgres setup in v0 and Vercel Marketplace. Hands Prisma ORM configuration to prisma-orm-setup; honors an explicit driver, alternative ORM, or database-only choice.\r\nlicense: MIT\r\nmetadata:\r\n  author: prisma\r\n  version: \"2.0.0\"\r\n---\r\n\r\n# Prisma Postgres setup\r\n\r\nConnect the intended database, then verify it from the application. Keep provisioning separate from ORM configuration so an existing database is reused.\r\n\r\n## 1. Inspect the project\r\n\r\nCheck the user's requested ORM or driver, installed packages, database connection, and environment-loading files. Check secret presence without printing values.\r\n\r\n- Honor explicit choices such as Drizzle, `pg`, or database-only setup.\r\n- For query or schema work in an already configured app, use its version-matched ORM guidance; do not restart setup.\r\n\r\n## 2. Reuse or obtain a database\r\n\r\n| Situation                                    | Action                                                                                                           |\r\n| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |\r\n| Existing connection or connected integration | Verify its project, database, and environment; reuse it.                                                         |\r\n| v0 or Vercel Marketplace                     | Read [Marketplace setup](references\u002Fvercel-marketplace.md) and use the native integration flow.                  |\r\n| Standalone persistent database               | Read [provisioning](references\u002Fprovisioning.md); use an authenticated CLI, MCP tool, Console, or Management API. |\r\n| Temporary development database requested     | Read the `create-db` section in [provisioning](references\u002Fprovisioning.md), including expiry and claiming.       |\r\n\r\nResolve the workspace, project, and region before creation. If several resources fit, ask which one to use. If provisioning is blocked by permissions or quota, report the blocker; do not delete another resource or switch workspaces to get around it.\r\n\r\n## 3. Connect the application\r\n\r\nUse the connection appropriate to the chosen driver and runtime. Store it in the project's secret environment configuration, never source code or chat. Preserve unrelated entries, update the intended variable once, and ensure local secret files are ignored by Git.\r\n\r\nApplication processes and CLI commands may load different environment files. For example, a framework may load `.env.development.local` while a shell command does not. A variable missing from the shell does not mean the database is missing: load the intended file for that command without displaying credentials, and do not provision another database.\r\n\r\n## 4. Configure the ORM and verify\r\n\r\nFor Prisma ORM setup, read [prisma-orm-setup\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fprisma\u002Fskills\u002Fblob\u002Fmain\u002Fprisma-orm-setup\u002FSKILL.md) directly, or load the installed `prisma-orm-setup` skill when the host resolves sibling skills by name. It owns ORM version selection and configuration. If that handoff is unavailable, report it.\r\n\r\nFor an explicitly selected alternative, keep that ORM or driver and use its documented setup. For database-only setup, stop after verifying connectivity.\r\n\r\nRun a read-only query against the intended database through the application's chosen ORM or driver. Report what was connected, the selected ORM\u002Fversion, and the query result without secrets. If any step is blocked or untested, say so instead of claiming setup is complete.\r\n\r\nFor Studio, SDK integrations, or database operations beyond initial setup, read [operations](references\u002Foperations.md).\r\n","# Prisma Postgres setup\r\n\r\nConnect the intended database, then verify it from the application. Keep provisioning separate from ORM configuration so an existing database is reused.\r\n\r\n## 1. Inspect the project\r\n\r\nCheck the user's requested ORM or driver, installed packages, database connection, and environment-loading files. Check secret presence without printing values.\r\n\r\n- Honor explicit choices such as Drizzle, `pg`, or database-only setup.\r\n- For query or schema work in an already configured app, use its version-matched ORM guidance; do not restart setup.\r\n\r\n## 2. Reuse or obtain a database\r\n\r\n| Situation                                    | Action                                                                                                           |\r\n| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |\r\n| Existing connection or connected integration | Verify its project, database, and environment; reuse it.                                                         |\r\n| v0 or Vercel Marketplace                     | Read [Marketplace setup](references\u002Fvercel-marketplace.md) and use the native integration flow.                  |\r\n| Standalone persistent database               | Read [provisioning](references\u002Fprovisioning.md); use an authenticated CLI, MCP tool, Console, or Management API. |\r\n| Temporary development database requested     | Read the `create-db` section in [provisioning](references\u002Fprovisioning.md), including expiry and claiming.       |\r\n\r\nResolve the workspace, project, and region before creation. If several resources fit, ask which one to use. If provisioning is blocked by permissions or quota, report the blocker; do not delete another resource or switch workspaces to get around it.\r\n\r\n## 3. Connect the application\r\n\r\nUse the connection appropriate to the chosen driver and runtime. Store it in the project's secret environment configuration, never source code or chat. Preserve unrelated entries, update the intended variable once, and ensure local secret files are ignored by Git.\r\n\r\nApplication processes and CLI commands may load different environment files. For example, a framework may load `.env.development.local` while a shell command does not. A variable missing from the shell does not mean the database is missing: load the intended file for that command without displaying credentials, and do not provision another database.\r\n\r\n## 4. Configure the ORM and verify\r\n\r\nFor Prisma ORM setup, read [prisma-orm-setup\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fprisma\u002Fskills\u002Fblob\u002Fmain\u002Fprisma-orm-setup\u002FSKILL.md) directly, or load the installed `prisma-orm-setup` skill when the host resolves sibling skills by name. It owns ORM version selection and configuration. If that handoff is unavailable, report it.\r\n\r\nFor an explicitly selected alternative, keep that ORM or driver and use its documented setup. For database-only setup, stop after verifying connectivity.\r\n\r\nRun a read-only query against the intended database through the application's chosen ORM or driver. Report what was connected, the selected ORM\u002Fversion, and the query result without secrets. If any step is blocked or untested, say so instead of claiming setup is complete.\r\n\r\nFor Studio, SDK integrations, or database operations beyond initial setup, read [operations](references\u002Foperations.md).\r\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"version":25},"prisma","2.0.0","master","2a47f88dcbb7be2f7916208357084d080851f407","server\u002F.agents\u002Fskills\u002Fprisma-postgres-setup","https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier","https:\u002F\u002Fgithub.com\u002Faandremillan10","2026-10-15 23:26:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add aandremillan10\u002Fhealth-ier --skill prisma-postgres-setup",{"tool":38,"command":39},"bunx","bunx skills add aandremillan10\u002Fhealth-ier --skill prisma-postgres-setup",{"tool":41,"command":42},"pnpm","pnpm dlx skills add aandremillan10\u002Fhealth-ier --skill prisma-postgres-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-postgres-setup\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Foperations.md","REFERENCE","参考文档",1779,"https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-postgres-setup\u002Freferences\u002Foperations.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fprovisioning.md",4765,"https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-postgres-setup\u002Freferences\u002Fprovisioning.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fvercel-marketplace.md",1792,"https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-postgres-setup\u002Freferences\u002Fvercel-marketplace.md",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7ENTM9PBVPKP9W9D2B79V0Z","prisma-upgrade-v7","Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on \"upgrade to prisma 7\", \"prisma 7 migration\", \"prisma-client generator\", \"driver adapter required\".","https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-upgrade-v7\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7ENTHSW1W9V566QK6718G6W","prisma-postgres","Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.","https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-postgres\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7ENTA9M9TDEE1QAXSRX85X5","prisma-orm-setup","Set up Prisma ORM in an application, connect its database, or troubleshoot the connection of an existing Prisma 6, 7, or 8 app. Defaults new applications to Prisma ORM 8 and loads the package-owned prisma-8 skill; keeps existing Prisma 6\u002F7 apps on their version with provider references for PostgreSQL, MySQL, SQLite, SQL Server, CockroachDB, MongoDB, and Prisma Postgres.","https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-orm-setup\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7ENT6C76JZ1ZE92QS43TQ2Z","prisma-mongodb-upgrade","Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when \"upgrade to prisma 7\" comes up in a project with provider = \"mongodb\", or when evaluating a move to Prisma 8. Triggers on \"upgrade prisma mongodb\", \"prisma 7 mongodb\", \"mongodb prisma migration\", \"prisma 8 mongodb\".","https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-mongodb-upgrade\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7ENT11MS7RW30YHYEGR5928","prisma-driver-adapter-implementation","Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.","https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-driver-adapter-implementation\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7ENSYRZBVC610EMT657PXNF","prisma-database-setup","Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.","https:\u002F\u002Fgithub.com\u002Faandremillan10\u002Fhealth-ier\u002Fblob\u002Fmaster\u002Fserver\u002F.agents\u002Fskills\u002Fprisma-database-setup\u002FSKILL.md",[],[]]