Name database tables and columns using domain concepts.
npx skills add https://github.com/efoo-team/skills --skill database-design-efoo-team
Please help me install this Agent Skill. Skill: database-design Source: https://github.com/efoo-team/skills/tree/main/skills/database-design Command: npx skills add https://github.com/efoo-team/skills --skill database-design-efoo-team
This Skill helps you design database schemas that accurately reflect real-world concepts and entities, avoiding misleading names based on process or use-case specifics.
Describe how to name a table storing user contact info to ensure the name reflects the domain concept rather than implementation details.
High-intent search queries and answers about installing and using this skill.
Conceptual database naming identifies tables and columns using stable domain entities like 'customers' or 'addresses' rather than transient application processes. This ensures schema names remain valid across different application layers and future modifications.
Database normalization structures schemas to accurately reflect real-world entities, attributes, and relationships. Proper separation and integration of these elements ensures data integrity and reduces redundancy during conceptual design.
Conceptual database design is needed when creating systems like customer management platforms where tables must represent real-world concepts. It prevents misleading names based on temporary use-case specifics or implementation details.
Separating database entities and attributes involves structuring tables to represent distinct real-world objects and their properties. This conceptual clarity ensures proper normalization and accurate relationship mapping across the schema.
Schema naming should avoid process-specific terms because they become invalid when application layers or workflows change. Domain-concept naming ensures the database schema remains stable and accurately reflects the real-world entities.
KentoShimizuProduce conceptual models of entities, relationships, and lifecycle semantics for schema design.
SempriniGenerate 3NF physical database schemas and data contracts from conceptual models.
ortus-boxlangConvert BoxLang dynamic objects to JDBC-compatible Java types via JPA AttributeConverters.
snoodleboot-ioGenerate ERD blueprints from Mermaid syntax descriptions.
