ai-architecture

Analyzes codebase architecture for drift, coupling issues, cohesion problems, boundary violations, technical debt, and backwards compatibility risks.

54|3|Updated Feb 4, 2026

Search Tags:#architecture #drift detection #compatibility #dependencies #tech debt #coupling #cohesion

Ready to run

npx skills add https://github.com/arcasilesgroup/ai-engineering --skill ai-architecture-arcasilesgroup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ai-architecture
Source: https://github.com/arcasilesgroup/ai-engineering/tree/main/.claude/skills/ai-architecture
Command: npx skills add https://github.com/arcasilesgroup/ai-engineering --skill ai-architecture-arcasilesgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and rectify issues within software architecture, ensuring it aligns with design specifications and maintains high standards of quality and compatibility.

Core Features & Use Cases

Drift Detection: Compares the implemented code structure against architectural documentation.
Coupling & Cohesion Analysis: Assesses inter-module dependencies and the focus of individual modules.
Technical Debt Identification: Flags architectural issues that can impede future development.
Backwards Compatibility Checks: Analyzes changes for potential breaking impacts on existing systems.
Use Case: Before a major release, use this Skill to scan the codebase for any architectural drift or potential compatibility issues introduced by recent changes.

Quick Start

Run the ai-architecture skill to analyze the current codebase for architectural drift.

Frequently Asked Questions about ai-architecture

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

FAQPage Schema

How do I detect software architecture drift from design specifications?▼

Detect software architecture drift by analyzing your codebase structure, import graphs, and call graphs against documented architecture and ADRs. This process identifies divergence from specifications, boundary violations, and structural issues before a major release.

What is the best way to check backwards compatibility for breaking API changes?▼

Checking backwards compatibility involves analyzing code changes for potential breaking impacts on public APIs, database schemas, and configurations. This analysis assesses whether recent modifications will disrupt existing system integrations.

How do I analyze coupling and cohesion problems in my codebase?▼

Analyze coupling and cohesion by assessing inter-module dependencies and the focus of individual modules. This examination of data flow and module boundaries identifies architectural issues that impede future development and increase technical debt.

Can I assess technical debt by scanning import graphs and call graphs?▼

Yes, you can assess technical debt by scanning import graphs and call graphs to identify architectural issues. This structural analysis flags coupling problems, boundary violations, and cohesion issues that hinder maintainability and future development.

Does this architectural analysis require documented ADRs to work?▼

Yes, this architectural analysis requires documented ADRs and architecture specifications to function effectively. It compares implemented code structure and data flow against these documents to accurately detect drift and boundary violations.