dilcore-architecture

Document the Dilcore Platform's modular architecture and layer dependency matrix.

1|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/aytymchuk/Dilcore-Platform --skill dilcore-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dilcore-architecture
Source: https://github.com/aytymchuk/Dilcore-Platform/tree/main/.cursor/skills/dilcore-architecture
Command: npx skills add https://github.com/aytymchuk/Dilcore-Platform --skill dilcore-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive understanding of the Dilcore Platform's project structure, layer dependencies, and architectural rules, ensuring code consistency and maintainability.

Core Features & Use Cases

  • Architectural Guidance: Details the 7-layer structure within each module and the specific dependency rules between layers.
  • Dependency Enforcement: Explains how ArchUnitNET tests enforce these rules, including cross-module dependencies.
  • Use Case: When adding new code or refactoring existing modules, consult this Skill to ensure adherence to the established architectural patterns and avoid introducing dependency violations.

Quick Start

Use the dilcore-architecture skill to understand the layer dependency matrix for the Dilcore Platform.

Frequently Asked Questions about dilcore-architecture

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

FAQPage Schema
How do I enforce layer dependencies in a .NET modular architecture?

You can enforce layer dependencies in modular architecture by defining a strict 7-layer pattern per module and validating the dependency matrix using ArchUnitNET tests to prevent structural violations.

What is the 7-layer architecture pattern used for code structure?

The 7-layer architecture pattern structures each module with specific dependency rules, ensuring code consistency by dictating exactly how layers interact and restricting unauthorized cross-module or downward dependencies.

How do I add new code to a modular platform without breaking dependency rules?

To add new code without breaking dependency rules, consult the project structure guidelines to place code in the correct layer, verify the dependency matrix, and run ArchUnitNET tests to validate constraints.

Does ArchUnitNET support enforcing cross-module dependency constraints?

Yes, ArchUnitNET supports enforcing cross-module dependency constraints by running automated tests that validate WebApi.Client restrictions and ensure no illegal references exist between separate platform modules.

Why does my architecture test fail when adding new project references?

Architecture tests fail when adding project references because the new dependency violates the established layer dependency matrix, introducing an unauthorized connection that ArchUnitNET detects and blocks.