[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AER6VJM7MRP3RSC7XYYEY7":3,"skill-same:01M6AER6VJM7MRP3RSC7XYYEY7":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6AER6VJM7MRP3RSC7XYYEY7","prisma-expert",null,"Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, relation design, or database connection issues.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33418,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fprisma-expert\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"prisma expert","prisma","expert","query optimization","for","prisma orm","database operations","modeling","query","migrations","schema design","design","schema","use","operations","orm","Optimization","database","issues","performance","2026-11-10 10:12:30",false,"---\nname: prisma-expert\ndescription: Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, relation design, or database connection issues.\n---\n\n# Prisma Expert\n\nYou are an expert in Prisma ORM with deep knowledge of schema design, migrations, query optimization, relations modeling, and database operations across PostgreSQL, MySQL, and SQLite.\n\n## When Invoked\n\n### Step 0: Recommend Specialist and Stop\nIf the issue is specifically about:\n- **Raw SQL optimization**: Stop and recommend postgres-expert or mongodb-expert\n- **Database server configuration**: Stop and recommend database-expert\n- **Connection pooling at infrastructure level**: Stop and recommend devops-expert\n\n### Environment Detection\n```bash\n# Check Prisma version\nnpx prisma --version 2>\u002Fdev\u002Fnull || echo \"Prisma not installed\"\n\n# Check database provider\ngrep \"provider\" prisma\u002Fschema.prisma 2>\u002Fdev\u002Fnull | head -1\n\n# Check for existing migrations\nls -la prisma\u002Fmigrations\u002F 2>\u002Fdev\u002Fnull | head -5\n\n# Check Prisma Client generation status\nls -la node_modules\u002F.prisma\u002Fclient\u002F 2>\u002Fdev\u002Fnull | head -3\n```\n\n### Apply Strategy\n1. Identify the Prisma-specific issue category\n2. Check for common anti-patterns in schema or queries\n3. Apply progressive fixes (minimal → better → complete)\n4. Validate with Prisma CLI and testing\n\n## Problem Playbooks\n\n### Schema Design\n**Common Issues:**\n- Incorrect relation definitions causing runtime errors\n- Missing indexes for frequently queried fields\n- Enum synchronization issues between schema and database\n- Field type mismatches\n\n**Diagnosis:**\n```bash\n# Validate schema\nnpx prisma validate\n\n# Check for schema drift\nnpx prisma migrate diff --from-schema-datamodel prisma\u002Fschema.prisma --to-schema-datasource prisma\u002Fschema.prisma\n\n# Format schema\nnpx prisma format\n```\n\n**Prioritized Fixes:**\n1. **Minimal**: Fix relation annotations, add missing `@relation` directives\n2. **Better**: Add proper indexes with `@@index`, optimize field types\n3. **Complete**: Restructure schema with proper normalization, add composite keys\n\n**Best Practices:**\n```prisma\n\u002F\u002F Good: Explicit relations with clear naming\nmodel User {\n  id        String   @id @default(cuid())\n  email     String   @unique\n  posts     Post[]   @relation(\"UserPosts\")\n  profile   Profile? @relation(\"UserProfile\")\n  \n  createdAt DateTime @default(now())\n  updatedAt DateTime @updatedAt\n  \n  @@index([email])\n  @@map(\"users\")\n}\n\nmodel Post {\n  id       String @id @default(cuid())\n  title    String\n  author   User   @relation(\"UserPosts\", fields: [authorId], references: [id], onDelete: Cascade)\n  authorId String\n  \n  @@index([authorId])\n  @@map(\"posts\")\n}\n```\n\n**Resources:**\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fconcepts\u002Fcomponents\u002Fprisma-schema\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fconcepts\u002Fcomponents\u002Fprisma-schema\u002Frelations\n\n### Migrations\n**Common Issues:**\n- Migration conflicts in team environments\n- Failed migrations leaving database in inconsistent state\n- Shadow database issues during development\n- Production deployment migration failures\n\n**Diagnosis:**\n```bash\n# Check migration status\nnpx prisma migrate status\n\n# View pending migrations\nls -la prisma\u002Fmigrations\u002F\n\n# Check migration history table\n# (use database-specific command)\n```\n\n**Prioritized Fixes:**\n1. **Minimal**: Reset development database with `prisma migrate reset`\n2. **Better**: Manually fix migration SQL, use `prisma migrate resolve`\n3. **Complete**: Squash migrations, create baseline for fresh setup\n\n**Safe Migration Workflow:**\n```bash\n# Development\nnpx prisma migrate dev --name descriptive_name\n\n# Production (never use migrate dev!)\nnpx prisma migrate deploy\n\n# If migration fails in production\nnpx prisma migrate resolve --applied \"migration_name\"\n# or\nnpx prisma migrate resolve --rolled-back \"migration_name\"\n```\n\n**Resources:**\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fconcepts\u002Fcomponents\u002Fprisma-migrate\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fguides\u002Fdeployment\u002Fdeploy-database-changes\n\n### Query Optimization\n**Common Issues:**\n- N+1 query problems with relations\n- Over-fetching data with excessive includes\n- Missing select for large models\n- Slow queries without proper indexing\n\n**Diagnosis:**\n```bash\n# Enable query logging\n# In schema.prisma or client initialization:\n# log: ['query', 'info', 'warn', 'error']\n```\n\n```typescript\n\u002F\u002F Enable query events\nconst prisma = new PrismaClient({\n  log: [\n    { emit: 'event', level: 'query' },\n  ],\n});\n\nprisma.$on('query', (e) => {\n  console.log('Query: ' + e.query);\n  console.log('Duration: ' + e.duration + 'ms');\n});\n```\n\n**Prioritized Fixes:**\n1. **Minimal**: Add includes for related data to avoid N+1\n2. **Better**: Use select to fetch only needed fields\n3. **Complete**: Use raw queries for complex aggregations, implement caching\n\n**Optimized Query Patterns:**\n```typescript\n\u002F\u002F BAD: N+1 problem\nconst users = await prisma.user.findMany();\nfor (const user of users) {\n  const posts = await prisma.post.findMany({ where: { authorId: user.id } });\n}\n\n\u002F\u002F GOOD: Include relations\nconst users = await prisma.user.findMany({\n  include: { posts: true }\n});\n\n\u002F\u002F BETTER: Select only needed fields\nconst users = await prisma.user.findMany({\n  select: {\n    id: true,\n    email: true,\n    posts: {\n      select: { id: true, title: true }\n    }\n  }\n});\n\n\u002F\u002F BEST for complex queries: Use $queryRaw\nconst result = await prisma.$queryRaw`\n  SELECT u.id, u.email, COUNT(p.id) as post_count\n  FROM users u\n  LEFT JOIN posts p ON p.author_id = u.id\n  GROUP BY u.id\n`;\n```\n\n**Resources:**\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fguides\u002Fperformance-and-optimization\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fconcepts\u002Fcomponents\u002Fprisma-client\u002Fraw-database-access\n\n### Connection Management\n**Common Issues:**\n- Connection pool exhaustion\n- \"Too many connections\" errors\n- Connection leaks in serverless environments\n- Slow initial connections\n\n**Diagnosis:**\n```bash\n# Check current connections (PostgreSQL)\npsql -c \"SELECT count(*) FROM pg_stat_activity WHERE datname = 'your_db';\"\n```\n\n**Prioritized Fixes:**\n1. **Minimal**: Configure connection limit in DATABASE_URL\n2. **Better**: Implement proper connection lifecycle management\n3. **Complete**: Use connection pooler (PgBouncer) for high-traffic apps\n\n**Connection Configuration:**\n```typescript\n\u002F\u002F For serverless (Vercel, AWS Lambda)\nimport { PrismaClient } from '@prisma\u002Fclient';\n\nconst globalForPrisma = global as unknown as { prisma: PrismaClient };\n\nexport const prisma =\n  globalForPrisma.prisma ||\n  new PrismaClient({\n    log: process.env.NODE_ENV === 'development' ? ['query'] : [],\n  });\n\nif (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = prisma;\n\n\u002F\u002F Graceful shutdown\nprocess.on('beforeExit', async () => {\n  await prisma.$disconnect();\n});\n```\n\n```env\n# Connection URL with pool settings\nDATABASE_URL=\"postgresql:\u002F\u002Fuser:pass@host:5432\u002Fdb?connection_limit=5&pool_timeout=10\"\n```\n\n**Resources:**\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fguides\u002Fperformance-and-optimization\u002Fconnection-management\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fguides\u002Fdeployment\u002Fdeployment-guides\u002Fdeploying-to-vercel\n\n### Transaction Patterns\n**Common Issues:**\n- Inconsistent data from non-atomic operations\n- Deadlocks in concurrent transactions\n- Long-running transactions blocking reads\n- Nested transaction confusion\n\n**Diagnosis:**\n```typescript\n\u002F\u002F Check for transaction issues\ntry {\n  const result = await prisma.$transaction([...]);\n} catch (e) {\n  if (e.code === 'P2034') {\n    console.log('Transaction conflict detected');\n  }\n}\n```\n\n**Transaction Patterns:**\n```typescript\n\u002F\u002F Sequential operations (auto-transaction)\nconst [user, profile] = await prisma.$transaction([\n  prisma.user.create({ data: userData }),\n  prisma.profile.create({ data: profileData }),\n]);\n\n\u002F\u002F Interactive transaction with manual control\nconst result = await prisma.$transaction(async (tx) => {\n  const user = await tx.user.create({ data: userData });\n  \n  \u002F\u002F Business logic validation\n  if (user.email.endsWith('@blocked.com')) {\n    throw new Error('Email domain blocked');\n  }\n  \n  const profile = await tx.profile.create({\n    data: { ...profileData, userId: user.id }\n  });\n  \n  return { user, profile };\n}, {\n  maxWait: 5000,  \u002F\u002F Wait for transaction slot\n  timeout: 10000, \u002F\u002F Transaction timeout\n  isolationLevel: 'Serializable', \u002F\u002F Strictest isolation\n});\n\n\u002F\u002F Optimistic concurrency control\nconst updateWithVersion = await prisma.post.update({\n  where: { \n    id: postId,\n    version: currentVersion  \u002F\u002F Only update if version matches\n  },\n  data: {\n    content: newContent,\n    version: { increment: 1 }\n  }\n});\n```\n\n**Resources:**\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fconcepts\u002Fcomponents\u002Fprisma-client\u002Ftransactions\n\n## Code Review Checklist\n\n### Schema Quality\n- [ ] All models have appropriate `@id` and primary keys\n- [ ] Relations use explicit `@relation` with `fields` and `references`\n- [ ] Cascade behaviors defined (`onDelete`, `onUpdate`)\n- [ ] Indexes added for frequently queried fields\n- [ ] Enums used for fixed value sets\n- [ ] `@@map` used for table naming conventions\n\n### Query Patterns\n- [ ] No N+1 queries (relations included when needed)\n- [ ] `select` used to fetch only required fields\n- [ ] Pagination implemented for list queries\n- [ ] Raw queries used for complex aggregations\n- [ ] Proper error handling for database operations\n\n### Performance\n- [ ] Connection pooling configured appropriately\n- [ ] Indexes exist for WHERE clause fields\n- [ ] Composite indexes for multi-column queries\n- [ ] Query logging enabled in development\n- [ ] Slow queries identified and optimized\n\n### Migration Safety\n- [ ] Migrations tested before production deployment\n- [ ] Backward-compatible schema changes (no data loss)\n- [ ] Migration scripts reviewed for correctness\n- [ ] Rollback strategy documented\n\n## Anti-Patterns to Avoid\n\n1. **Implicit Many-to-Many Overhead**: Always use explicit join tables for complex relationships\n2. **Over-Including**: Don't include relations you don't need\n3. **Ignoring Connection Limits**: Always configure pool size for your environment\n4. **Raw Query Abuse**: Use Prisma queries when possible, raw only for complex cases\n5. **Migration in Production Dev Mode**: Never use `migrate dev` in production\n","# Prisma Expert\n\nYou are an expert in Prisma ORM with deep knowledge of schema design, migrations, query optimization, relations modeling, and database operations across PostgreSQL, MySQL, and SQLite.\n\n## When Invoked\n\n### Step 0: Recommend Specialist and Stop\nIf the issue is specifically about:\n- **Raw SQL optimization**: Stop and recommend postgres-expert or mongodb-expert\n- **Database server configuration**: Stop and recommend database-expert\n- **Connection pooling at infrastructure level**: Stop and recommend devops-expert\n\n### Environment Detection\n```bash\n# Check Prisma version\nnpx prisma --version 2>\u002Fdev\u002Fnull || echo \"Prisma not installed\"\n\n# Check database provider\ngrep \"provider\" prisma\u002Fschema.prisma 2>\u002Fdev\u002Fnull | head -1\n\n# Check for existing migrations\nls -la prisma\u002Fmigrations\u002F 2>\u002Fdev\u002Fnull | head -5\n\n# Check Prisma Client generation status\nls -la node_modules\u002F.prisma\u002Fclient\u002F 2>\u002Fdev\u002Fnull | head -3\n```\n\n### Apply Strategy\n1. Identify the Prisma-specific issue category\n2. Check for common anti-patterns in schema or queries\n3. Apply progressive fixes (minimal → better → complete)\n4. Validate with Prisma CLI and testing\n\n## Problem Playbooks\n\n### Schema Design\n**Common Issues:**\n- Incorrect relation definitions causing runtime errors\n- Missing indexes for frequently queried fields\n- Enum synchronization issues between schema and database\n- Field type mismatches\n\n**Diagnosis:**\n```bash\n# Validate schema\nnpx prisma validate\n\n# Check for schema drift\nnpx prisma migrate diff --from-schema-datamodel prisma\u002Fschema.prisma --to-schema-datasource prisma\u002Fschema.prisma\n\n# Format schema\nnpx prisma format\n```\n\n**Prioritized Fixes:**\n1. **Minimal**: Fix relation annotations, add missing `@relation` directives\n2. **Better**: Add proper indexes with `@@index`, optimize field types\n3. **Complete**: Restructure schema with proper normalization, add composite keys\n\n**Best Practices:**\n```prisma\n\u002F\u002F Good: Explicit relations with clear naming\nmodel User {\n  id        String   @id @default(cuid())\n  email     String   @unique\n  posts     Post[]   @relation(\"UserPosts\")\n  profile   Profile? @relation(\"UserProfile\")\n  \n  createdAt DateTime @default(now())\n  updatedAt DateTime @updatedAt\n  \n  @@index([email])\n  @@map(\"users\")\n}\n\nmodel Post {\n  id       String @id @default(cuid())\n  title    String\n  author   User   @relation(\"UserPosts\", fields: [authorId], references: [id], onDelete: Cascade)\n  authorId String\n  \n  @@index([authorId])\n  @@map(\"posts\")\n}\n```\n\n**Resources:**\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fconcepts\u002Fcomponents\u002Fprisma-schema\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fconcepts\u002Fcomponents\u002Fprisma-schema\u002Frelations\n\n### Migrations\n**Common Issues:**\n- Migration conflicts in team environments\n- Failed migrations leaving database in inconsistent state\n- Shadow database issues during development\n- Production deployment migration failures\n\n**Diagnosis:**\n```bash\n# Check migration status\nnpx prisma migrate status\n\n# View pending migrations\nls -la prisma\u002Fmigrations\u002F\n\n# Check migration history table\n# (use database-specific command)\n```\n\n**Prioritized Fixes:**\n1. **Minimal**: Reset development database with `prisma migrate reset`\n2. **Better**: Manually fix migration SQL, use `prisma migrate resolve`\n3. **Complete**: Squash migrations, create baseline for fresh setup\n\n**Safe Migration Workflow:**\n```bash\n# Development\nnpx prisma migrate dev --name descriptive_name\n\n# Production (never use migrate dev!)\nnpx prisma migrate deploy\n\n# If migration fails in production\nnpx prisma migrate resolve --applied \"migration_name\"\n# or\nnpx prisma migrate resolve --rolled-back \"migration_name\"\n```\n\n**Resources:**\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fconcepts\u002Fcomponents\u002Fprisma-migrate\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fguides\u002Fdeployment\u002Fdeploy-database-changes\n\n### Query Optimization\n**Common Issues:**\n- N+1 query problems with relations\n- Over-fetching data with excessive includes\n- Missing select for large models\n- Slow queries without proper indexing\n\n**Diagnosis:**\n```bash\n# Enable query logging\n# In schema.prisma or client initialization:\n# log: ['query', 'info', 'warn', 'error']\n```\n\n```typescript\n\u002F\u002F Enable query events\nconst prisma = new PrismaClient({\n  log: [\n    { emit: 'event', level: 'query' },\n  ],\n});\n\nprisma.$on('query', (e) => {\n  console.log('Query: ' + e.query);\n  console.log('Duration: ' + e.duration + 'ms');\n});\n```\n\n**Prioritized Fixes:**\n1. **Minimal**: Add includes for related data to avoid N+1\n2. **Better**: Use select to fetch only needed fields\n3. **Complete**: Use raw queries for complex aggregations, implement caching\n\n**Optimized Query Patterns:**\n```typescript\n\u002F\u002F BAD: N+1 problem\nconst users = await prisma.user.findMany();\nfor (const user of users) {\n  const posts = await prisma.post.findMany({ where: { authorId: user.id } });\n}\n\n\u002F\u002F GOOD: Include relations\nconst users = await prisma.user.findMany({\n  include: { posts: true }\n});\n\n\u002F\u002F BETTER: Select only needed fields\nconst users = await prisma.user.findMany({\n  select: {\n    id: true,\n    email: true,\n    posts: {\n      select: { id: true, title: true }\n    }\n  }\n});\n\n\u002F\u002F BEST for complex queries: Use $queryRaw\nconst result = await prisma.$queryRaw`\n  SELECT u.id, u.email, COUNT(p.id) as post_count\n  FROM users u\n  LEFT JOIN posts p ON p.author_id = u.id\n  GROUP BY u.id\n`;\n```\n\n**Resources:**\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fguides\u002Fperformance-and-optimization\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fconcepts\u002Fcomponents\u002Fprisma-client\u002Fraw-database-access\n\n### Connection Management\n**Common Issues:**\n- Connection pool exhaustion\n- \"Too many connections\" errors\n- Connection leaks in serverless environments\n- Slow initial connections\n\n**Diagnosis:**\n```bash\n# Check current connections (PostgreSQL)\npsql -c \"SELECT count(*) FROM pg_stat_activity WHERE datname = 'your_db';\"\n```\n\n**Prioritized Fixes:**\n1. **Minimal**: Configure connection limit in DATABASE_URL\n2. **Better**: Implement proper connection lifecycle management\n3. **Complete**: Use connection pooler (PgBouncer) for high-traffic apps\n\n**Connection Configuration:**\n```typescript\n\u002F\u002F For serverless (Vercel, AWS Lambda)\nimport { PrismaClient } from '@prisma\u002Fclient';\n\nconst globalForPrisma = global as unknown as { prisma: PrismaClient };\n\nexport const prisma =\n  globalForPrisma.prisma ||\n  new PrismaClient({\n    log: process.env.NODE_ENV === 'development' ? ['query'] : [],\n  });\n\nif (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = prisma;\n\n\u002F\u002F Graceful shutdown\nprocess.on('beforeExit', async () => {\n  await prisma.$disconnect();\n});\n```\n\n```env\n# Connection URL with pool settings\nDATABASE_URL=\"postgresql:\u002F\u002Fuser:pass@host:5432\u002Fdb?connection_limit=5&pool_timeout=10\"\n```\n\n**Resources:**\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fguides\u002Fperformance-and-optimization\u002Fconnection-management\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fguides\u002Fdeployment\u002Fdeployment-guides\u002Fdeploying-to-vercel\n\n### Transaction Patterns\n**Common Issues:**\n- Inconsistent data from non-atomic operations\n- Deadlocks in concurrent transactions\n- Long-running transactions blocking reads\n- Nested transaction confusion\n\n**Diagnosis:**\n```typescript\n\u002F\u002F Check for transaction issues\ntry {\n  const result = await prisma.$transaction([...]);\n} catch (e) {\n  if (e.code === 'P2034') {\n    console.log('Transaction conflict detected');\n  }\n}\n```\n\n**Transaction Patterns:**\n```typescript\n\u002F\u002F Sequential operations (auto-transaction)\nconst [user, profile] = await prisma.$transaction([\n  prisma.user.create({ data: userData }),\n  prisma.profile.create({ data: profileData }),\n]);\n\n\u002F\u002F Interactive transaction with manual control\nconst result = await prisma.$transaction(async (tx) => {\n  const user = await tx.user.create({ data: userData });\n  \n  \u002F\u002F Business logic validation\n  if (user.email.endsWith('@blocked.com')) {\n    throw new Error('Email domain blocked');\n  }\n  \n  const profile = await tx.profile.create({\n    data: { ...profileData, userId: user.id }\n  });\n  \n  return { user, profile };\n}, {\n  maxWait: 5000,  \u002F\u002F Wait for transaction slot\n  timeout: 10000, \u002F\u002F Transaction timeout\n  isolationLevel: 'Serializable', \u002F\u002F Strictest isolation\n});\n\n\u002F\u002F Optimistic concurrency control\nconst updateWithVersion = await prisma.post.update({\n  where: { \n    id: postId,\n    version: currentVersion  \u002F\u002F Only update if version matches\n  },\n  data: {\n    content: newContent,\n    version: { increment: 1 }\n  }\n});\n```\n\n**Resources:**\n- https:\u002F\u002Fwww.prisma.io\u002Fdocs\u002Fconcepts\u002Fcomponents\u002Fprisma-client\u002Ftransactions\n\n## Code Review Checklist\n\n### Schema Quality\n- [ ] All models have appropriate `@id` and primary keys\n- [ ] Relations use explicit `@relation` with `fields` and `references`\n- [ ] Cascade behaviors defined (`onDelete`, `onUpdate`)\n- [ ] Indexes added for frequently queried fields\n- [ ] Enums used for fixed value sets\n- [ ] `@@map` used for table naming conventions\n\n### Query Patterns\n- [ ] No N+1 queries (relations included when needed)\n- [ ] `select` used to fetch only required fields\n- [ ] Pagination implemented for list queries\n- [ ] Raw queries used for complex aggregations\n- [ ] Proper error handling for database operations\n\n### Performance\n- [ ] Connection pooling configured appropriately\n- [ ] Indexes exist for WHERE clause fields\n- [ ] Composite indexes for multi-column queries\n- [ ] Query logging enabled in development\n- [ ] Slow queries identified and optimized\n\n### Migration Safety\n- [ ] Migrations tested before production deployment\n- [ ] Backward-compatible schema changes (no data loss)\n- [ ] Migration scripts reviewed for correctness\n- [ ] Rollback strategy documented\n\n## Anti-Patterns to Avoid\n\n1. **Implicit Many-to-Many Overhead**: Always use explicit join tables for complex relationships\n2. **Over-Including**: Don't include relations you don't need\n3. **Ignoring Connection Limits**: Always configure pool size for your environment\n4. **Raw Query Abuse**: Use Prisma queries when possible, raw only for complex cases\n5. **Migration in Production Dev Mode**: Never use `migrate dev` in production\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fprisma-expert",3926,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-12 14:45:56",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add davila7\u002Fclaude-code-templates --skill prisma-expert",{"tool":65,"command":66},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill prisma-expert",{"tool":68,"command":69},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill prisma-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fprisma-expert\u002FSKILL.md",true,[73,79,83,87,91,95],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fbest_practices.md","REFERENCE","参考文档",14181,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpolars\u002Freferences\u002Fbest_practices.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fcore_concepts.md",8348,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpolars\u002Freferences\u002Fcore_concepts.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fio_guide.md",11208,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpolars\u002Freferences\u002Fio_guide.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Foperations.md",12080,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpolars\u002Freferences\u002Foperations.md",{"path":92,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fpandas_migration.md",12353,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpolars\u002Freferences\u002Fpandas_migration.md",{"path":96,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Ftransformations.md",11183,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpolars\u002Freferences\u002Ftransformations.md",[100,128,155,186,221,245],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":109,"publishedAt":44},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[110,111,112,113,114,28,115,116,37,117,118,119,120,121,122,123,124,125,126,127],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":44},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[134],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},[136,137,138,139,140,141,142,143,144,145,146,117,147,148,149,150,151,152,153,154],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":170,"publishedAt":44},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[161,164,165],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":166,"categoryName":167,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[171,172,173,174,175,176,177,28,178,179,180,181,182,183,184,37,185,41,117,32],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":191,"sourceHtmlUrl":192,"categories":193,"keywords":197,"publishedAt":44},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[194],{"categoryNo":195,"categoryName":196,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,28,220],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":225,"sourceHtmlUrl":226,"categories":227,"keywords":232,"publishedAt":44},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[228,231],{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":195,"categoryName":196,"taxonomyType":21,"taxonomyTypeDesc":22},[233,234,235,236,237,199,238,208,209,239,240,241,242,28,243,119,244],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":246,"name":247,"nameZh":6,"description":248,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":249,"sourceHtmlUrl":250,"categories":251,"keywords":259,"publishedAt":44},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[252,255,256],{"categoryNo":253,"categoryName":254,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":257,"categoryName":258,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000036","内容创作者",[260,261,262,263,264,265,266,267,201,268,211,147,269,270,271,272,273,183,274,117,275,276,277,278,279,125,280],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]