'prisma' 검색 결과

ORM patterns for NestJS: TypeORM, Prisma, Mongoose. Covers entities, repositories, transactions, migrations, common pitfalls (N+1, cascade deletes, transaction boundaries). Use this skill to: - Detect which ORM the project uses and apply matching patterns. - Define entities/schemas with the right decorators. - Inject repositories or Prisma client correctly. - Run transactions at the service boundary. - Write migrations that round-trip cleanly. Do NOT use this skill for: - Module/DI patterns (see nest-conventions). - Decorator usage broadly (see decorator-patterns). - Non-ORM raw SQL (rare; flag in BLOCKERS if needed).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

NestJS testing patterns: Test.createTestingModule for unit/integration, mocking providers, e2e tests with INestApplication + supertest, ORM mocking (TypeORM/Prisma/Mongoose), test fixtures. Use this skill to: - Write unit tests for services with mocked dependencies. - Write integration tests with real DI but mocked external services. - Write e2e tests for HTTP endpoints via supertest. - Mock repositories/Prisma client correctly. - Cover services and controllers to ≥80%. Do NOT use this skill for: - Test framework setup (Jest/Vitest config — usually already in place). - Frontend tests. - Load testing (out of QA scope).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prisma ORM, type-safe queries, migrations, relations

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

スキーマ/データ移行の安全性を framework 非依存で審査する。破壊的スキーマ変更・ロック誘発・backfill・ロールバック可逆性・expand-contract の段階適用を、prisma / typeorm / Rails / Django / Alembic / 生 SQL などに横断適用する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cuts the next minor release of Prisma Composer: bumps the root package.json version, propagates it to every workspace package in lockstep, and opens a PR titled "chore(release): v<next-version>". When a maintainer merges the PR, the `Publish to npm` workflow runs automatically and ships the new version to npm under dist-tag `latest`, plus a matching GitHub Release with auto-generated notes. Use when a maintainer asks to "cut the next minor", "bump to the next version", "open a release PR", or "prepare a publish PR".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert en migrations de base de données (Flyway, Liquibase, Prisma Migrate, zero-downtime)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Backend Node.js Specialist IA — Expert en développement backend Node.js (Express, Fastify, NestJS, Prisma, real-time, WebSockets)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use Neon serverless Postgres with branching, connection pooling, and instant scalability for modern applications with Prisma or Drizzle ORM integration. Use when setting up serverless Postgres databases, implementing database branching for preview environments, configuring connection pooling, optimizing for serverless cold starts, using Prisma with Neon, implementing database migrations, scaling databases automatically, or building applications on Vercel/Netlify with Postgres.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PostgreSQL、MySQL、および一般的なORM（Prisma、Drizzle、Kysely、Django、TypeORM、golang-migrate）にわたるスキーマ変更、データマイグレーション、ロールバック、ゼロダウンタイムデプロイメントのためのデータベースマイグレーションベストプラクティス。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

トレーニングデータの代わりにContext7 MCPを使用して最新のライブラリやフレームワークのドキュメントを取得。セットアップの質問、APIリファレンス、コード例、またはユーザーがフレームワーク名（React、Next.js、Prismaなど）を指定した場合にアクティベート。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review database schema design and detect anti-patterns. Based on common RDB design knowledge and best practices. Supports Prisma, Drizzle, Rails, Django, Laravel, TypeORM, Sequelize, SQLAlchemy, and raw SQL (DDL). Use when the user says "review DB design", "check schema", "review table design", "review migration", "check for anti-patterns", "DB設計をレビューして", "スキーマを見て", "テーブル設計を確認して", "マイグレーションをレビューして", "アンチパターンがないか調べて", "この設計で問題ないか見て".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a systematic, scoping, or rapid review needs a reproducible pipeline: protocol framing (PICO/SPIDER/PCC), a logged search string, title/abstract and full-text screening with recorded exclusion reasons, and PRISMA flow counts, with the human as the deciding screener.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for the search-planning stage of a literature review, when database lanes and language layers must be chosen, when DOI coverage policy is unclear, or when inclusion and exclusion criteria need drafting before any source is read; not for running the screening and PRISMA pipeline of a formal review, which is prisma-scoping-review-pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

NestJS의 API와 서비스를 설계하고 검토합니다. 기능별 코드 구조, 입력 검증, 인증, 예외 처리, 환경 설정과 테스트를 정리해 실제 운영을 위한 구현을 돕습니다.

• NestJS API 구조 설계
• 입력 검증과 접근 제어 구현
• 예외 처리와 환경 설정 검토

코드 변경 시 테스트, 타입 검사, 빌드를 자동 실행해 배포 전 품질 확인 절차를 마련합니다. GitHub Actions 설정부터 단계적 배포와 롤백 절차까지 다룹니다.

• 새 프로젝트에 CI 도입하기
• 테스트와 품질 검사 자동화하기
• 단계적 배포와 롤백 설계하기

Find current documentation and code examples through the Context7 MCP server. Look up library setup, API usage, migration steps, and library-specific problems, using documentation for the requested version when available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Looking up documentation for a specific version
• Finding library setup and configuration steps
• Finding examples for code that uses external libraries

Search current library documentation and code examples with Context7 CLI, a command-line tool. Find API usage and configuration guidance, select available version-specific documentation, and prioritize examples in the programming language you use.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking current API usage and configuration
• Finding documentation for a requested version
• Prioritizing code examples in a chosen language

Develop a research question, search and verify literature, and combine findings into an academic report. Modes also support guided research discussions, claim checking, paper comparisons, and systematic reviews with optional meta-analysis, which statistically combines study results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarify a research direction through guided questions
• Search literature and compare findings across sources
• Check specific claims against supporting sources

Refactor TypeScript code that handles several variants in multiple places using frozen classes and a Visitor interface, which defines a handler for each variant. This helps type checking expose missing handlers when new variants are added.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Refactor a union type with repeated switch statements
• Design commands or nodes that need several kinds of processing
• Catch missing handlers when adding a new variant

Collect and validate the review state of a GitHub pull request, then generate a readable Markdown report, a text summary, and a list of items to address before review triage begins.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Collecting the current review state of a pull request
• Summarizing unresolved threads and review comments
• Preparing review items for subsequent triage

Write or revise system architecture documents, design decision records, and engineering references. Use concrete examples and clear explanations of design choices to make documents useful both to newcomers and to developers needing precise details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting how a subsystem works
• Rewriting design documents for new team members
• Explaining architecture decisions within the document

Update Biome packages with pnpm, align configuration filenames and schema versions across the repository, and run the configured checks and fixes. Receive a report of remaining issues, with optional further fixes subject to agreement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Updating Biome to a specified version
• Aligning configuration files after dependency updates
• Checking for issues introduced by a Biome update

Review and rewrite architecture decision records, documents that explain design choices, from a newcomer’s perspective. Identify missing context, buried decisions, and temporary details, then reorganize each document so future readers can follow the reasoning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing design decisions from a new team member’s perspective
• Making an ADR’s decision and reasoning easier to follow
• Removing temporary project context from long-lived records