architecture-dependency-guard

Enforce the mandatory layer dependency matrix across TpIDS .NET projects.

Updated Aug 24, 2026
One-click install
npx skills add https://github.com/aggutierrez98/TP-TD --skill architecture-dependency-guard-aggutierrez98
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-dependency-guard
Source: https://github.com/aggutierrez98/TP-TD/tree/main/.agents/skills/architecture-dependency-guard
Command: npx skills add https://github.com/aggutierrez98/TP-TD --skill architecture-dependency-guard-aggutierrez98

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams working on the TpIDS codebase risk introducing illegal project references between layers (UI, BLL, REPOSITORIO, DAL, BE, SERVICIOS, ABSTRACCIONES), which breaks the 7-layer architecture and creates hidden coupling that is hard to undo later. ## Core Features & Use Cases - Dependency Matrix Enforcement: Validates every change against a strict allowed-reference matrix between .csproj projects, treating any violation as blocking. - Layer Placement Guidance: Verifies the correct target layer before moving classes or creating services, repositories, entities, or contracts. - Automated Verification Script: Runs a PowerShell script (verify-architecture-dependencies.ps1) whenever .csproj files are touched or code moves between projects. - Use Case: When adding a new business service, the Skill confirms BLL may reference ABSTRACCIONES, REPOSITORIO, BE, and SERVICIOS, blocks any BLL -> DAL reference, and requires the guard script plus a green build before closing the task. ## Quick Start Use the architecture-dependency-guard skill to verify that my new service and project references comply with the TpIDS layer dependency matrix.

Frequently Asked Questions about architecture-dependency-guard

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

FAQPage Schema
How do I verify layer dependencies in a layered .NET architecture?▼

Check each .csproj reference against the allowed dependency matrix, then run the verify-architecture-dependencies.ps1 PowerShell script to detect violations automatically. Any reference not explicitly listed in the matrix is prohibited and must be treated as blocking.

What project references are allowed in the TpIDS architecture?▼

TpIDS (UI) may reference ABSTRACCIONES, BLL, BE, and SERVICIOS; BLL may reference ABSTRACCIONES, REPOSITORIO, BE, and SERVICIOS; REPOSITORIO may reference DAL; BE and SERVICIOS may only reference ABSTRACCIONES, which depends on nothing.

Can the UI layer call DAL or BLL call DAL directly?▼

No, direct DAL invocation from UI or BLL is forbidden. All persistence must flow through the REPOSITORIO layer, and functional flows from the UI must enter through BLL even though UI holds references to SERVICIOS and BE.

When should the architecture verification script be run?▼

Run verify-architecture-dependencies.ps1 whenever a .csproj file is modified, code is moved between projects, or there is doubt about the correct layer for a class. The task should only close after the guard and the build are both green.

What is the difference between architecture-dependency-guard and composition-root-guard?▼

architecture-dependency-guard enforces the reference matrix between .csproj projects, while composition-root-guard covers how instances are constructed and injected inside those layers, such as Composition Root and avoiding hidden Service Locator. Both apply when adding BLLs or services.