skills.rest
linhlvit
linhlvitCOMMUNITY
Explore all skills by this author →
GitHub

atomic-hld-design

Generates standardized HLD Tier and Overview files for Atomic layer source systems.

1|Updated Apr 7, 2026
Search Tags:#data modeling#medallion architecture#lakehouse#hld design#atomic layer#bcv mapping#metadata aggregation
One-click install
npx skills add https://github.com/linhlvit/ubck_atomic_design --skill atomic-hld-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: atomic-hld-design
Source: https://github.com/linhlvit/ubck_atomic_design/tree/main/.claude/skills/atomic-hld-design
Command: npx skills add https://github.com/linhlvit/ubck_atomic_design --skill atomic-hld-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates inconsistent, non-compliant High-Level Design (HLD) documentation for Atomic layer source systems in the Medallion data architecture, which causes misalignment between source data structures, business concept validation (BCV) mappings, and downstream low-level design (LLD) and ETL development for the UBCK Lakehouse project. It removes manual guesswork from tiered entity design, table type classification, scope categorization, and ensures adherence to project-wide standards to reduce review cycles and metadata errors.

Core Features & Use Cases

  • End-to-end HLD workflow: Guided step-by-step process for designing or updating HLD for new or existing source systems (DCST, FMS, NHNCK, etc.), including input collection from BRD files, table type classification, tiered dependency mapping, BCV term lookup, shared entity review, and out-of-scope table categorization.
  • Standardized output enforcement: Strict formatting and content rules for HLD Tier and Overview files to ensure compatibility with automated aggregation scripts that generate project-wide metadata files (atomic_entities.yaml, atomic_out_of_scope.yaml), reducing manual errors and review cycles.
  • Built-in reference materials: Includes standard classification group lists, file layout rules, and correct/incorrect format examples for out-of-scope tables to help data modelers avoid common mistakes.
  • Use Case: A data modeler tasked with designing HLD for a new FMS source system can follow the skill's process to correctly classify tables, map BCV terms, generate compliant Tier and Overview files, and automatically update project metadata without manual formatting errors.

Quick Start

Use the atomic-hld-design skill to create a compliant HLD Tier 1 file for the new DCST source system, following the provided templates and BCV lookup steps to map source tables to Atomic entities and classify out-of-scope tables correctly.

Frequently Asked Questions about atomic-hld-design

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

FAQPage Schema
How do I create a standardized HLD for Medallion architecture source systems?▼

Creating standardized HLD for Medallion architecture requires classifying table types, designing tiered dependencies, mapping BCV terms, and reviewing shared entities. This enforces strict formatting rules for Tier and Overview files to ensure compatibility with automated aggregation scripts.

What is BCV term mapping in Lakehouse data modeling?▼

BCV term mapping in Lakehouse data modeling aligns source data structures with business concept validations. It ensures source tables correctly map to Atomic entities during the high-level design workflow.

How do I classify out-of-scope tables in an Atomic layer HLD?▼

Classifying out-of-scope tables in an Atomic layer HLD involves applying specific categorization rules and using provided reference examples. Correct classification ensures proper generation of the atomic_out_of_scope.yaml project metadata file.

Does HLD design for the UBCK Lakehouse project support automated metadata aggregation?▼

Yes, HLD design for the UBCK Lakehouse project supports automated metadata aggregation. Enforcing strict file layout rules for Tier and Overview files guarantees compatibility with scripts generating project-wide metadata files.

Why do I need strict formatting rules for HLD Tier files in data projects?▼

You need strict formatting rules for HLD Tier files to ensure compatibility with automated aggregation scripts. Non-compliant documentation causes misalignment between source data structures and downstream ETL development, increasing manual errors and review cycles.

Related Skills

Explore More Data & Analytics Skills→
linhlvitlinhlvit

atomic-review

Validate Atomic HLD designs against BRD definitions and entity registries.

Community
Advanced
saajunaidsaajunaid

architecture-document

Generate HLD and LLD documents from Architecture.md as DOCX or PPTX.

Community
Advanced
hieutrtrhieutrtr
8

system-architecture

Generate architecture.md and ADRs for Python/React full-stack modules.

Community
Advanced
RDEWAIRDEWAI
5

create-dms

Generate compliant Data Model Specification documents from HLD and DRD inputs.

Official
Advanced