How do I install the Config Efcore Cs skill?

Run npx skillmds@latest add eskcti/config-efcore-cs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Config Efcore Cs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Config Efcore Cs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Config Efcore Cs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Config Efcore Cs?

EskCti (@eskcti) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Config Efcore Cs by eskcti — Agent Skill

Name: Config Efcore Cs
Author: EskCti

Config Efcore Cs

Inicializar e padronizar a infraestrutura de persistência Entity Framework Core no backend C# com DbContext, configurações Fluent API, migrations EF, appsettings.json com ConnectionStrings, e Docker Compose para Postgres. Usar quando o pedido envolver setup inicial de EF Core, onboarding de módulos com tabelas no banco ou rebootstrap da infraestrutura de dados no .NET.

EskCti Updated Sep 21, 2026

File contents

Config EF Core (C#)

Overview

Executar setup determinístico da infraestrutura EF Core no backend C#, com ConnectionString configurada via appsettings.json, migrations, Docker Compose para Postgres e configurações de mapeamento via Fluent API.

Equivalente ao config-prisma do stack TypeScript e config-jpa-kt do stack Kotlin, adaptado para o ecossistema .NET.

Workflow

Confirmar que o projeto contém .csproj no Backend e Infrastructure.
Configurar dependências EF Core no Infrastructure:
- Microsoft.EntityFrameworkCore
- Npgsql.EntityFrameworkCore.PostgreSQL (provider Postgres)
Criar/Ajustar appsettings.json com ConnectionStrings.
Criar docker-compose.yml para Postgres compatível com as strings de conexão.
Criar classe AppDbContext herdando de DbContext.
Organizar mapeamentos na pasta Persistence/Configurations/ implementando IEntityTypeConfiguration<T>.
Criar migration inicial de bootstrap: dotnet ef migrations add InitialCreate.
Validar que a aplicação inicia e aplica migrations em ambiente de Dev.

O que o setup garante

Dependências no Infrastructure:
- Microsoft.EntityFrameworkCore
- Npgsql.EntityFrameworkCore.PostgreSQL
appsettings.json com:
- ConnectionStrings:DefaultConnection via env DATABASE_URL (se possível mapeado)
docker-compose.yml com Postgres alinhado às credenciais locais.
Pasta Persistence/Migrations/ com a primeira migração.
Injeção de dependência no Program.cs via AddDbContext<AppDbContext>.

Arquivos críticos

src/Project.Infrastructure/Persistence/Contexts/AppDbContext.cs
src/Project.Backend/appsettings.json
src/Project.Infrastructure/Persistence/Configurations/*.Configuration.cs
docker-compose.yml
.env / .env.example

Commands

Instalar o CLI dotnet-ef (requerido para migrations):

dotnet tool install --global dotnet-ef

Gerar migration (no root):

dotnet ef migrations add <MigrationName> --project src/Project.Infrastructure --startup-project src/Project.Backend --output-dir Persistence/Migrations

Aplicar no banco local:

dotnet ef database update --project src/Project.Infrastructure --startup-project src/Project.Backend

Remover última migration:

dotnet ef migrations remove --project src/Project.Infrastructure --startup-project src/Project.Backend

Resources

agents/openai.yaml: Configuração do agente.
scripts/init-efcore-cs.mjs: Script de automação (placeholder).
assets/efcore-template-cs/: Template base para DbContext e mapeamentos.
references/efcore-init-checklist-cs.md: Checklist operacional detalhado.

Global Standards

Consultar ../skills-standards.md para padrões globais de nomenclatura C#.

---name: config-efcore-csdescription: Inicializar e padronizar a infraestrutura de persistência Entity Framework Core no backend C# com DbContext, configurações Fluent API, migrations EF, appsettings.json com ConnectionStrings, e Docker Compose para Postgres. Usar quando o pedido envolver setup inicial de EF Core, onboarding de módulos com tabelas no banco ou rebootstrap da infraestrutura de dados no .NET.---# Config EF Core (C#)## OverviewExecutar setup determinístico da infraestrutura EF Core no backend C#, com ConnectionString configurada via `appsettings.json`, migrations, Docker Compose para Postgres e configurações de mapeamento via Fluent API.Equivalente ao `config-prisma` do stack TypeScript e `config-jpa-kt` do stack Kotlin, adaptado para o ecossistema .NET.## Workflow1. Confirmar que o projeto contém `.csproj` no Backend e Infrastructure.2. Configurar dependências EF Core no Infrastructure: - `Microsoft.EntityFrameworkCore` - `Npgsql.EntityFrameworkCore.PostgreSQL` (provider Postgres)3. Criar/Ajustar `appsettings.json` com `ConnectionStrings`.4. Criar `docker-compose.yml` para Postgres compatível com as strings de conexão.5. Criar classe `AppDbContext` herdando de `DbContext`.6. Organizar mapeamentos na pasta `Persistence/Configurations/` implementando `IEntityTypeConfiguration<T>`.7. Criar migration inicial de bootstrap: `dotnet ef migrations add InitialCreate`.8. Validar que a aplicação inicia e aplica migrations em ambiente de Dev.## O que o setup garante- Dependências no Infrastructure: - `Microsoft.EntityFrameworkCore` - `Npgsql.EntityFrameworkCore.PostgreSQL`- `appsettings.json` com: - `ConnectionStrings:DefaultConnection` via env `DATABASE_URL` (se possível mapeado)- `docker-compose.yml` com Postgres alinhado às credenciais locais.- Pasta `Persistence/Migrations/` com a primeira migração.- Injeção de dependência no `Program.cs` via `AddDbContext<AppDbContext>`.## Arquivos críticos- `src/Project.Infrastructure/Persistence/Contexts/AppDbContext.cs`- `src/Project.Backend/appsettings.json`- `src/Project.Infrastructure/Persistence/Configurations/*.Configuration.cs`- `docker-compose.yml`- `.env` / `.env.example`## CommandsInstalar o CLI `dotnet-ef` (requerido para migrations):```bashdotnet tool install --global dotnet-ef```Gerar migration (no root):```bashdotnet ef migrations add <MigrationName> --project src/Project.Infrastructure --startup-project src/Project.Backend --output-dir Persistence/Migrations```Aplicar no banco local:```bashdotnet ef database update --project src/Project.Infrastructure --startup-project src/Project.Backend```Remover última migration:```bashdotnet ef migrations remove --project src/Project.Infrastructure --startup-project src/Project.Backend```## Resources- `agents/openai.yaml`: Configuração do agente.- `scripts/init-efcore-cs.mjs`: Script de automação (placeholder).- `assets/efcore-template-cs/`: Template base para DbContext e mapeamentos.- `references/efcore-init-checklist-cs.md`: Checklist operacional detalhado.## Global Standards- Consultar `../skills-standards.md` para padrões globais de nomenclatura C#.

Frequently asked questions