entity-design

Design domain entities with consistent structure, relationships, and audit fields.

53|27|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/andresharpe/dotbot-v3 --skill entity-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: entity-design
Source: https://github.com/andresharpe/dotbot-v3/tree/main/profiles/dotnet/prompts/skills/entity-design
Command: npx skills add https://github.com/andresharpe/dotbot-v3 --skill entity-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes the design and documentation of domain entities, ensuring consistency in structure, relationships, and audit fields across a project.

Core Features & Use Cases

  • Consistent Entity Modeling: Enforces a uniform structure for all domain entities.
  • Detailed Documentation: Generates comprehensive documentation including fields, types, enums, relationships, and design decisions.
  • Use Case: When building a new feature that requires defining user profiles, this Skill can guide the creation of the User entity, ensuring it includes necessary fields like Id, Username, Email, audit fields, and relationships to other entities like Roles.

Quick Start

Use the entity-design skill to create a new entity called 'Product' with fields 'Name' (string), 'Price' (decimal), and a foreign key to 'Category'.

Frequently Asked Questions about entity-design

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

FAQPage Schema
How do I standardize domain entity structure and audit fields across a software project?

Design domain entities by defining fields, types, enums, and relationships while enforcing conventions like PascalCase naming and UTC timestamps to ensure consistent domain modeling and detailed documentation.

How do I document database schema relationships and design decisions for new features?

Document database schema relationships by generating comprehensive entity documentation that details fields, types, enums, relationship mappings, and specific design decisions to facilitate clear software architecture modeling.

What is the best way to model complex data types in a domain entity?

Model complex data types in a domain entity by using JSONB fields to store unstructured or nested information while maintaining standard audit fields and integer primary keys for consistent database schema design.

Does consistent entity modeling require soft deletes and integer primary keys?

Consistent entity modeling in this context requires soft deletes and integer primary keys, alongside UTC timestamps and PascalCase naming, to strictly follow project conventions for domain modeling and architecture.

Can I use domain modeling conventions for defining user profiles and role relationships?

Use domain modeling conventions to define user profiles by structuring entities with necessary fields like Username and Email, while mapping relationships to other entities like Roles to ensure consistent database schema architecture.