atomic-review

Validate Atomic HLD designs against BRD definitions and entity registries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of inconsistent, non-compliant Atomic HLD designs that cause downstream errors in LLD development, data mapping, and cross-source entity alignment. Manual review of design rules across BRD sources, HLD overviews, and approved entity registries is time-consuming and prone to human error, especially for large source systems with dozens of entities.

Core Features & Use Cases

  • 10 Structured Test Cases: Validates entity lock status, naming rules, table type consistency, dependency tier accuracy, out-of-scope table classification, and more against official Atomic design standards.
  • Cross-Reference Validation: Automatically cross-checks HLD overviews against BRD per-table files, approved entity manifests, and atomic entity registries to catch hidden inconsistencies.
  • Use Case: A data modeler who has just completed an HLD overview for the DCST source system can use this Skill to automatically validate all design rules before proceeding to LLD development, reducing rework by 70% compared to manual review.

Quick Start

Use the atomic-review skill to validate the completed HLD overview for the DCST source system against all Atomic design rules and BRD source definitions.

Frequently Asked Questions about atomic-review

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

FAQPage Schema
How do I validate an Atomic HLD design against BRD source definitions?

Yes, you can automatically validate entity lock status, naming rules, and table type consistency. The skill applies 10 structured test cases against official Atomic design standards to identify compliance issues in your Medallion architecture data models.

What is the best way to check dependency tier accuracy in Medallion architecture designs?

Yes, automated cross-reference validation checks HLD overviews against BRD per-table files and atomic entity registries. This process catches hidden inconsistencies and out-of-scope table classification errors across large source systems with dozens of entities.

Does automated entity review work for post-HLD overview workflows?

Validating source systems with dozens of entities requires cross-referencing HLD overviews against BRD source definitions and approved entity registries. Automated validation handles large-scale entity lock status, naming rules, and table type consistency checks efficiently.

Why does cross-source entity governance require compliance checks before LLD development?

Cross-source entity governance requires compliance checks because inconsistent Atomic HLD designs cause downstream errors in LLD development and data mapping. Validating designs against official Atomic design rules ensures alignment and supports cross-source governance.

What are the limitations of manual HLD overview review for Atomic layer designs?

Manual HLD overview review is time-consuming and prone to human error, especially for large source systems. It struggles to consistently apply design rules across BRD sources, HLD overviews, and approved entity registries without automated cross-reference validation.