AgentStack
SKILL verified MIT Self-run

Data Model Design

skill-sethdford-claude-skills-data-model-design · by sethdford

Design data models for business domains using entity-relationship or domain-driven design. Use when modeling new domains or refactoring data structures.

No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add skill-sethdford-claude-skills-data-model-design

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Data Model Design? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Data Model Design

Design data models that correctly represent business domains and support required queries efficiently.

Context

You are modeling a business domain in a database. The data model must reflect business semantics and perform well.

Domain Context

Based on relational theory and domain-driven design:

  • Entities: Things with identity (User, Order)
  • Attributes: Properties of entities (name, email)
  • Relationships: How entities connect (User has many Orders)
  • Normalization: Reduce redundancy; improves write performance
  • Denormalization: Intentionally duplicate data; improves read performance

Instructions

  1. Identify Entities: What are the main concepts? List with primary key.
  2. Identify Attributes: For each entity, list properties.
  3. Define Relationships: One-to-one, one-to-many, many-to-many.
  4. Normalize: Remove update anomalies through normal forms.
  5. Denormalize Strategically: Add calculated columns or tables for read performance.

Anti-Patterns

  • Premature Normalization: Third-normal-form everywhere. Result: slow queries. Guard: Design for reads; denormalize if needed.
  • Flat Tables: No normalization; entity data scattered. Result: update anomalies. Guard: At least second-normal-form.

Further Reading

  • Relational Database Design — normalization fundamentals
  • Domain-Driven Design — modeling business domains

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.