Architecture Coherence

Detect architecture drift by comparing declared architecture with actual code structure and dependencies.

Updated Feb 9, 2026

Search Tags:#architecture #dependencies #audit #modularity #drift #boundaries #code-structure

Ready to run

npx skills add https://github.com/nsalvacao/nsalvacao-claude-code-plugins --skill architecture-coherence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Architecture Coherence
Source: https://github.com/nsalvacao/nsalvacao-claude-code-plugins/tree/main/plugins/solution-audit/skills/architecture-coherence
Command: npx skills add https://github.com/nsalvacao/nsalvacao-claude-code-plugins --skill architecture-coherence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture drift between declared architecture and actual code structure creates maintenance nightmares and runaway complexity. This skill helps teams verify that module boundaries, dependencies, and abstractions align with the intended design.

Core Features & Use Cases

Audit architecture intent vs. actual code boundaries by analyzing directory structure, exports, and public APIs.
Detect cross-boundary imports, wrong-direction dependencies, and layering violations to surface structural debt.
Generate concrete remediation recommendations to restore architectural coherence in multi-language repos or monorepos.

Quick Start

Analyze a project to identify where declared architecture diverges from the real code organization and provide actionable fixes.

Frequently Asked Questions about Architecture Coherence

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

FAQPage Schema

How do I detect architecture drift in a monorepo?▼

To detect architecture drift in a monorepo, compare the declared architecture against actual code structure by analyzing module boundaries, import graphs, and dependencies to identify structural deviations and boundary violations.

What is architecture drift in software engineering?▼

Architecture drift occurs when a project's declared design diverges from its actual code structure and dependencies, creating maintenance nightmares and runaway complexity due to cross-boundary imports and layering violations.

How can I audit module boundaries and import graphs in a multi-language codebase?▼

You can audit module boundaries and import graphs in a multi-language codebase by tracing dependencies and analyzing directory structures and public APIs to detect wrong-direction dependencies and assess coupling.

Does this architecture audit approach work for multi-language codebases and monorepos?▼

Yes, this approach explicitly supports multi-language codebases and monorepos by mapping module boundaries and tracing import graphs to surface structural debt across different languages within the same repository.

How do I fix boundary violations and architectural deviations in my project?▼

To fix boundary violations and architectural deviations, generate concrete remediation recommendations that restore architectural coherence by realigning module boundaries and correcting wrong-direction dependencies.