Generate asp net mvc entity framework models from database schem
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
npx -y skills add ECNU-ICALK/AutoSkill --skill generate-asp-net-mvc-entity-framework-models-from-database-schemAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
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.md
2.6 KB, as published. Nobody here has run it
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
- Primary Keys: Explicitly mark primary key properties with the
[Key]attribute. - Unique Constraints: Explicitly mark properties defined as unique (UNQ) with the
[Index(IsUnique = true)]attribute. - 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. - Data Types:
- Use
byte[]for password hash and salt fields instead of strings. - Use
[StringLength(length)]attributes for string properties that map tovarcharcolumns in the diagram.
- Use
- Navigation Properties:
- Use
ICollection<Entity>for the "many" side of a relationship. - Use a single reference
Entityfor the "one" side of a relationship.
- Use
- 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
stringfor 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