skills.rest
shouqitao
shouqitaoCOMMUNITY
Explore all skills by this author →
GitHub

lybtzyzs-arch-compliance

Verify codebase compliance with three-tier architecture, DDD aggregate roots, and Repository patterns.

Updated Jun 16, 2025
Search Tags:#code quality#architecture#code review#compliance#dependency analysis#technical debt#DDD
One-click install
npx skills add https://github.com/shouqitao/LYBTZYZS --skill lybtzyzs-arch-compliance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lybtzyzs-arch-compliance
Source: https://github.com/shouqitao/LYBTZYZS/tree/main/.claude/skills/lybtzyzs-arch-compliance
Command: npx skills add https://github.com/shouqitao/LYBTZYZS --skill lybtzyzs-arch-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically verifies that the project's codebase strictly adheres to its defined three-tier aligned architecture, DDD aggregate root principles, and Repository patterns. It proactively identifies and reports architectural violations, preventing technical debt and ensuring system maintainability and scalability.

Core Features & Use Cases

  • Three-Tier Architecture Validation: Uses serena to analyze project dependencies, ensuring correct flow (e.g., Presentation → Application → Infrastructure) and flagging any reverse or cross-layer dependencies.
  • DDD Aggregate Root Boundary Check: Scans code for direct modifications of aggregate root internal collections (e.g., medicalCase.Prescription.Items.Add(item)), recommending encapsulation through aggregate root public methods to maintain consistency.
  • Repository Pattern Enforcement: Verifies that repositories adhere to best practices, such as being interface-driven, having a single responsibility per aggregate root, and containing only data access logic (no business calculations).
  • Use Case: During a code review or CI/CD pipeline, this Skill scans the codebase. If it finds a Service layer directly modifying a Prescription entity's internal collection without going through the MedicalCase aggregate root, it flags this as a DDD boundary violation and suggests the correct encapsulated approach.

Quick Start

Check the current codebase for architectural compliance.