datamart-hld-design

Generate compliant Datamart HLD documents with phase-gate approvals and reuse analysis.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/linhlvit/ubck_atomic_design --skill datamart-hld-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datamart-hld-design
Source: https://github.com/linhlvit/ubck_atomic_design/tree/main/.claude/skills/datamart-hld-design
Command: npx skills add https://github.com/linhlvit/ubck_atomic_design --skill datamart-hld-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates inconsistent, non-compliant Datamart high-level design (HLD) documentation for UBCKNN's Lakehouse project built on the Medallion (Bronze/Atomic/Gold) architecture, ensuring all designs align with approved Atomic layer entities, cross-module reuse standards, and mandatory phase-gate approval workflows.

Core Features & Use Cases

  • Structured Phase-Gate Workflow: Enforces a mandatory 2-phase design process (Phase 1: HLD design with human approval checkpoints, Phase 2: Entities file generation) to prevent skipped validation steps and ensure stakeholder alignment.
  • 4-Layer Reuse Analysis: Automates checks across conformed dimension whitelists, classification value mapping, source matching, and partial table reuse to maximize reuse of existing Datamart tables, reducing redundant design work.
  • Built-in Compliance Validation: Includes strict rules for erDiagram syntax, flowchart lineage, naming conventions, KPI tracking, and Atomic entity alignment to eliminate common design errors and ensure consistency with UBCKNN's data model standards.
  • Use Case: Data modelers designing new Datamart modules for UBCKNN (including TT, NHNCK, NDTNN, QLCB, FMS, GSTT, GSDC, QLKD) can use this Skill to generate fully compliant HLD and Entities files that pass review on the first attempt.

Quick Start

Use the datamart-hld-design skill to generate a compliant Phase 1 HLD for the new FMS Datamart module using the provided BA analyst CSV, report screenshot, and Atomic dm_manifest.yaml file.

Frequently Asked Questions about datamart-hld-design

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

FAQPage Schema
How do I create a compliant Datamart high-level design for a Lakehouse project?

To create a compliant Datamart high-level design (HLD), follow a 2-phase workflow: Phase 1 handles HLD design with mandatory phase-gate approvals, and Phase 2 generates Entities files, ensuring alignment with Medallion architecture standards.

What is 4-layer reuse analysis in Datamart data modeling?

4-layer reuse analysis in Datamart data modeling checks conformed dimension whitelists, classification value mapping, source matching, and partial table reuse to maximize existing table reuse and reduce redundant design work.

How do I validate erDiagram syntax and flowchart lineage for Datamart HLDs?

Validate erDiagram syntax and flowchart lineage using built-in compliance rules that enforce naming conventions, KPI tracking, and alignment with approved Atomic layer entities to eliminate common Datamart design errors.

Can I use this workflow to update existing Datamart modules like FMS and QLCB?

Yes, you can use this workflow to update existing Datamart modules including TT, NHNCK, NDTNN, QLCB, FMS, GSTT, GSDC, and QLKD, ensuring updates pass phase-gate approval checkpoints and cross-module standards.

What inputs do I need to generate Datamart HLD and Entities files?

To generate Datamart HLD and Entities files, you need the provided BA analyst CSV, report screenshots, and the Atomic dm_manifest.yaml file to ensure strict alignment with approved Atomic layer entities.