Automate Prisma backend data access with repositories, transactions, and soft deletes.
npx skills add https://github.com/imkdw/imkdw-dev --skill backend-queries-imkdw
Please help me install this Agent Skill. Skill: Backend Queries Source: https://github.com/imkdw/imkdw-dev/tree/main/.claude/skills/backend-queries Command: npx skills add https://github.com/imkdw/imkdw-dev --skill backend-queries-imkdw
Inefficient or improperly managed database queries can lead to slow application performance, resource exhaustion, and data inconsistencies, impacting user experience and system stability. This Skill ensures optimal and reliable database interactions.
prisma.$transaction(), preventing partial updates.deletedAt: null) across all queries, preserving historical data without permanent deletion.CreateArticleUseCase, ensure that the article creation and any related tag associations are wrapped in a single Prisma transaction to guarantee atomicity, and that all read operations automatically filter soft-deleted articles.Guide me in creating a new repository method findBySlug for the ArticleRepository that retrieves an article by its slug, ensuring soft-deleted records are excluded and it accepts an optional Prisma transaction client.
High-intent search queries and answers about installing and using this skill.
Optimize Prisma queries by using eager loading with `include` and `select`, wrapping multiple operations in `prisma.$transaction()` for atomicity, filtering soft-deleted records with `deletedAt: null`, and implementing the repository pattern to centralize and cache efficient data access logic across your application.
Use `prisma.$transaction()` to wrap multiple database operations into a single atomic unit, preventing partial updates and ensuring all changes succeed or fail together. Pass the transaction client to repository methods that participate in the transaction for coordinated execution.
Add a `deletedAt` timestamp field to your schema, then filter `deletedAt: null` consistently in all read queries and repository methods. Soft delete by updating `deletedAt` instead of removing records, preserving historical data while keeping queries automatically exclude deleted rows.
Yes. Place repository classes in `shared/repository/`, use-case classes in `features/{feature}/use-case/`, and read-only query classes alongside them. Each layer maps Prisma results to domain objects, maintaining clean separation and testability across your application's data access tiers.
Repositories centralize query logic, reduce duplication, improve testability through dependency injection, enforce consistent patterns like soft delete filtering and transaction handling, and make switching database implementations easier without rewriting business logic.
Without transactions, partial failures leave your database in an inconsistent state—for example, creating an article succeeds but associating tags fails, orphaning data. Transactions guarantee atomicity: all operations complete or all roll back together.
quanngynxConfigure Prisma ORM v7 database connectivity with driver adapters and schema wiring.
djankiesImplement Redis query caching for Prisma 6 with TTL-based invalidation.
R2W1csOptimize Prisma ORM schemas, migrations, queries, connections, and transactions.
galihcittaConvert ORM calls to raw SQL and analyze query performance.