[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DXVB7WRKG63QS3WF2CCW4G":3,"skill-same:01M6DXVB7WRKG63QS3WF2CCW4G":70},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6DXVB7WRKG63QS3WF2CCW4G","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.","EthanSheehan\u002FGrid-Sentinel","EthanSheehan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F174215275?v=4","01M6DX9589ENESB2AYW9YK4Y50","Ethan Sheehan","01M6DX95P06JXASASFQZRFQ1NM",0,"MIT","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\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],"prisma","prisma expert","expert","schema","database operations","modeling","query","migrations","schema design","query optimization","migration","design","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","33d99efaac9ea5758fc27120b467eca96ad020d9",".agent\u002Fskills\u002Fprisma-expert","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel","https:\u002F\u002Fgithub.com\u002FEthanSheehan","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fethan-sheehan\u002F","Aerospace Engineering Student at the University of Bristol \u002F\u002F Propulsion Lead at HyPower Bristol","2026-05-22 21:19:23",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add EthanSheehan\u002FGrid-Sentinel --skill prisma-expert",{"tool":62,"command":63},"bunx","bunx skills add EthanSheehan\u002FGrid-Sentinel --skill prisma-expert",{"tool":65,"command":66},"pnpm","pnpm dlx skills add EthanSheehan\u002FGrid-Sentinel --skill prisma-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fprisma-expert\u002FSKILL.md",true,[],[71,100,133,153,167,192],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":80,"publishedAt":43},"01M6DY3X97YDSKHCCZG9KMASHA","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[81,82,83,84,85,86,87,88,89,90,91,92,36,93,94,95,96,97,98,99],"zapier make patterns","patterns","workflow","integrations","how to","apps","platform","but","build","complexity","power","simplicity","business","automate","how","apache","code","automation","writing",{"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":112,"publishedAt":43},"01M6DY3SVP128ZZPF2478H9JYZ","Cross-Site Scripting and HTML Injection Testing","This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection vulnerabilities\", \"steal cookies via XSS\", or \"bypass content security policies\". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fxss-html-injection\u002FSKILL.md",[106,109],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"html injection testing","Cross Site Scripting and HTML Injection Testing","injection","scripting","site","html","testing","exploit","user","applications","xss","cookies","content","web","test","vectors","via","steal","security","vulnerabilities",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":148,"publishedAt":43},"01M6DY3D694G80Y5N79CD1J575","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[139,140,143],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[99,149,150,36,151,152],"writing skills","deployment","editing","work",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":161,"publishedAt":43},"01M6DY3A7BM31W5Q2QARW00JHS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[159,160],{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},[162,99,163,164,165,36,97,166],"writing plans","plans","requirements","task","spec",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":43},"01M6DY36NSATM95HR7HMVZJYB3","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fworkflow-automation\u002FSKILL.md",[173],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},[175,98,83,176,177,178,96,179,180,181,182,183,184,185,186,187,188,189,190,191],"Workflow Automation","Production","flow","network","workflows","accessibility","ai agents","execution","scripts","worker","payment","n8n","money","resume","orchestrator","parallel","inngest",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"publishedAt":43},"01M6DY32QTGD80MQHJ8TPDH53H","WordPress Penetration Testing","This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fwordpress-penetration-testing\u002FSKILL.md",[198],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},[119,194,200,201,202,203,204,205,120,36,121,206,207,132,131],"penetration testing","wordpress","security assessment","sites","scan","pentest","plugins","assessment"]