typeorm

Enforce TypeORM data access patterns with entities, repositories, and migrations.

16|145|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/devfullcycle/mba-ia-greenfield-project --skill typeorm-devfullcycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typeorm
Source: https://github.com/devfullcycle/mba-ia-greenfield-project/tree/main/.claude/skills/typeorm
Command: npx skills add https://github.com/devfullcycle/mba-ia-greenfield-project --skill typeorm-devfullcycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeORM development guidelines establish a standardized, scalable approach to building data access layers in TypeScript projects, reducing schema drift and inconsistencies across modules.

Core Features & Use Cases

  • Enforces explicit entity definitions, typed columns, and the Data Mapper pattern for clear separation between domain and persistence.
  • Provides migration-first workflows, environment-based configuration, and naming conventions to improve reliability and maintainability.
  • Offers best-practice guidance for relationships (OneToOne, OneToMany, ManyToOne, ManyToMany) and repository patterns in NestJS + TypeORM contexts.
  • Use Case: You’re building a multi-module NestJS application with PostgreSQL and want predictable schemas, migrations, and clean data access layers.

Quick Start

Initialize your TypeORM data layer by configuring a starter DataSource, defining initial entities, and generating a baseline migration.

Frequently Asked Questions about typeorm

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

FAQPage Schema
How do I structure TypeORM entities using the Data Mapper pattern in TypeScript?

Using the Data Mapper pattern in TypeORM keeps domain logic separate from persistence by enforcing explicit entity definitions and typed columns. This approach maintains clear boundaries between database operations and business logic.

What is the best way to manage database migrations in a NestJS TypeORM project?

Managing database migrations in a NestJS TypeORM project requires a migration-first workflow. This ensures predictable schema changes by generating baseline migrations from explicit entity structures before applying them to PostgreSQL.

Can I use TypeORM with PostgreSQL for environment-based DataSource configuration?

TypeORM fully supports PostgreSQL with environment-based DataSource configuration. Externalizing database settings achieves reliable connections across deployment stages without hardcoding sensitive credentials.

How do I configure OneToMany and ManyToOne relationships in TypeORM?

Configuring OneToMany and ManyToOne relationships in TypeORM requires following clear relationship conventions. Applying best-practice guidance for these mappings ensures referential integrity and prevents schema drift across modules.

Does TypeORM work with NestJS to build scalable data access layers?

TypeORM works with NestJS to build scalable data access layers. Combining repository patterns with standardized naming conventions reduces inconsistencies and provides maintainable structures for multi-module PostgreSQL applications.