skills.rest
valentinmathey
valentinmatheyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bb-access-data

Centralizes Prisma usage and shared DTOs for standardized database access across services.

Updated Apr 16, 2026
Search Tags:#typescript#architecture#code-quality#prisma#dto#centralization#db-access
One-click install
npx skills add https://github.com/valentinmathey/Skills-Back-Automation --skill bb-access-data
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bb-access-data
Source: https://github.com/valentinmathey/Skills-Back-Automation/tree/main/skills/bb-access-data
Command: npx skills add https://github.com/valentinmathey/Skills-Back-Automation --skill bb-access-data

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes the way applications access the database by centralizing Prisma usage and shared DTOs through the access-data package.

Core Features & Use Cases

  • Centralized database access: prevents direct PrismaClient instantiation across services and enforces a single data access layer.
  • Re-export and shared models: ensures all generated types, models, enums, and DTOs are exported from the access-data index.
  • Prisma schema discipline: all schema changes are made in the official prisma schema file to maintain consistency.

Quick Start

Use bb-access-data to align all services with a single, typed data access layer across projects.

Frequently Asked Questions about bb-access-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I centralize Prisma database access across multiple services?▼

Centralizing Prisma database access requires routing all queries through a single PrismaClient instance and re-exporting generated types from a shared access-data index package.

What is the best way to share Prisma DTOs and generated types between APIs?▼

The best way to share Prisma DTOs is to re-export all generated types, models, and enums from a centralized access-data index, ensuring APIs import shared models from one location.

Where should I manage Prisma schema changes in a microservices architecture?▼

You should manage Prisma schema changes in a single official schema file within the centralized access-data package to maintain consistency and prevent schema drift across services.

Why does centralizing database access improve TypeScript code quality?▼

Centralizing database access improves TypeScript code quality by enforcing a single typed data access layer, eliminating scattered PrismaClient instances, and standardizing shared DTOs across projects.

Do I need a single PrismaClient instance for standardizing database access?▼

Yes, standardizing database access requires a single PrismaClient instance to prevent direct instantiation across services and maintain a centralized data access layer.

Can I update the Prisma schema directly within individual API services?▼

No, you should not update the Prisma schema within individual API services; all schema changes must be managed in the official prisma schema file located in the centralized access-data package.

Related Skills

Explore More Software Engineering Skills→
SomtoUgehSomtoUgeh

prisma-connection-pool-exhaustion

Configure Prisma connection pooling for serverless PostgreSQL or MySQL deployments.

Community
Advanced
flaming-codesflaming-codes
18

web-backend

Create static service classes with typed Supabase queries and Zod validation.

Community
Advanced
nguyenthienthanhnguyenthienthanh
24

nodejs-expert

Provide Node.js backend patterns for Express, NestJS, Fastify APIs with error handling and validation.

Community
Advanced
quanngynxquanngynx

prisma-database-setup

Configure Prisma ORM v7 database connectivity with driver adapters and schema wiring.

Community
Intermediate