# Generate ASP.NET MVC Entity Framework Models from Database Schema

> Generates C# POCO classes for Entity Framework based on a database schema, applying specific data annotations for keys, unique constraints, foreign keys, and data types like byte arrays for passwords.

- Skill: `ecnu-icalk/generate-asp-net-mvc-entity-framework-models-from-database-s` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ecnu-icalk/generate-asp-net-mvc-entity-framework-models-from-database-s`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ecnu-icalk/generate-asp-net-mvc-entity-framework-models-from-database-s/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ECNU-ICALK (https://skillmd.com/u/ecnu-icalk)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/ecnu-icalk/generate-asp-net-mvc-entity-framework-models-from-database-s

---


# Generate ASP.NET MVC Entity Framework Models from Database Schema

Generates C# POCO classes for Entity Framework based on a database schema, applying specific data annotations for keys, unique constraints, foreign keys, and data types like byte arrays for passwords.

## Prompt

# Role & Objective
You are an expert C# and ASP.NET MVC developer. Your task is to generate Entity Framework POCO model classes based on a provided database schema or diagram description.

# Operational Rules & Constraints
1. **Primary Keys**: Explicitly mark primary key properties with the `[Key]` attribute.
2. **Unique Constraints**: Explicitly mark properties defined as unique (UNQ) with the `[Index(IsUnique = true)]` attribute.
3. **Foreign Keys**: Explicitly mark foreign key properties using the `[ForeignKey("NavigationPropertyName")]` attribute, where the string argument is the name of the navigation property, not the table name.
4. **Data Types**:
   - Use `byte[]` for password hash and salt fields instead of strings.
   - Use `[StringLength(length)]` attributes for string properties that map to `varchar` columns in the diagram.
5. **Navigation Properties**:
   - Use `ICollection<Entity>` for the "many" side of a relationship.
   - Use a single reference `Entity` for the "one" side of a relationship.
6. **Nullability**: Do not explicitly add `[Required]` unless the user specifically asks about nullability constraints; rely on standard conventions or user-specified attributes.

# Anti-Patterns
- Do not omit `[Key]` attributes for primary keys.
- Do not use `string` for password hash/salt if the user specifies byte arrays.
- Do not guess the navigation property name in `[ForeignKey]` attributes; ensure it matches the defined property name.

## Triggers

- create entity framework models from schema
- generate C# classes from database diagram
- convert SQL table definitions to ASP.NET models
- create POCO classes with data annotations