dimensional

Maps conceptual entities to physical star schema dimensions, facts, and bridges.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Semprini/md-ddl --skill dimensional
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dimensional
Source: https://github.com/Semprini/md-ddl/tree/main/agents/agent-artifact/skills/dimensional
Command: npx skills add https://github.com/Semprini/md-ddl --skill dimensional

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps translate conceptual and logical data models into physical dimensional models, addressing the complexities of star schema, fact/dimension design, and temporal tracking.

Core Features & Use Cases

  • Physical Design Mapping: Guides the conversion of entities and relationships into dimensional structures (dimensions, facts, bridges).
  • History and Temporal Strategy: Provides clear rules for handling data mutability and temporal tracking (SCD types, valid/transaction time).
  • Inheritance and Enum Handling: Offers patterns for modeling inheritance and managing enumerations within dimensional models.
  • Use Case: A data architect needs to design a star schema for customer orders. This Skill will guide them on how to model customers, products, and order events as dimensions and facts, including how to handle slowly changing dimensions for customer attributes.

Quick Start

Use the dimensional skill to design a physical dimensional model for customer and order data.

Frequently Asked Questions about dimensional

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

FAQPage Schema
How do I map conceptual entities to a physical dimensional model for a star schema?

Dimensional modeling maps conceptual entities and relationships into star schema components like fact tables, dimension tables, and bridges. This enforces decision frameworks for existence and mutability to ensure accurate physical realization of data warehousing structures.

What is the best way to handle slowly changing dimensions in data warehousing?

Handling slowly changing dimensions requires applying specific SCD types and temporal tracking strategies like valid or transaction time. This enforces clear rules for data mutability and history retention within your dimensional model design.

How do you model inheritance and subtypes in a dimensional model?

Modeling inheritance and subtypes in a dimensional model involves applying specific inheritance patterns for subtypes. This guides the physical design mapping of conceptual entities to handle structural hierarchies within your data warehousing architecture.

When do I need temporal tracking strategies for fact table design?

Temporal tracking strategies for fact table design are needed when addressing data mutability and existence constraints over time. Enforcing decision frameworks for these temporal factors ensures accurate physical realization of transactional and historical data.

Does this approach support bridge tables for many-to-many relationships in star schemas?

Yes, physical design mapping supports bridge tables to resolve many-to-many relationships in star schemas. It guides the conversion of conceptual entities and relationships into dimensional structures including dimensions, facts, and bridges.