improve-codebase-architecture

Identify shallow modules and propose deeper designs using ADRs and domain glossary.

Updated May 8, 2026
One-click install
npx skills add https://github.com/mmartinsoliv/dotfiles --skill improve-codebase-architecture-mmartinsoliv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/mmartinsoliv/dotfiles/tree/main/agents/skills/improve-codebase-architecture
Command: npx skills add https://github.com/mmartinsoliv/dotfiles --skill improve-codebase-architecture-mmartinsoliv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you spot architectural friction in a codebase and turn shallow, tightly coupled areas into deeper modules with clearer seams.

Core Features & Use Cases

  • Architecture Review: Explore the codebase, domain glossary, and ADRs to find places where understanding depends on bouncing between too many files.
  • Deepening Opportunities: Identify modules that are shallow, hard to test, or leaking complexity across their interface.
  • Refactoring Guidance: Propose concrete changes that improve locality, increase leverage, and make tests exercise the real interface.
  • Use Case: A team preparing a refactor can use this Skill to prioritize which modules to consolidate first and which seams deserve adapters or new tests.

Quick Start

Ask the skill to review the repository and list the highest-leverage modules to deepen first.

Frequently Asked Questions about improve-codebase-architecture

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

FAQPage Schema
How do I identify shallow modules in a codebase for refactoring?

Identify shallow modules by analyzing architectural friction where understanding requires bouncing between too many files. The Skill surfaces deepening opportunities by examining the domain glossary and ADRs to find modules leaking complexity across their interface.

How do I improve testability in tightly coupled systems?

Improve testability in tightly coupled systems by reasoning about seams and adapters to propose deeper module designs. This approach strengthens locality and leverage, enabling tests to exercise the real interface rather than implementation details.

What is the best way to prioritize modules for consolidation during an architecture review?

Prioritize modules for consolidation by reviewing the repository to list the highest-leverage modules to deepen first. The Skill evaluates shallow modules against the project's domain glossary to determine which refactoring changes yield the strongest architectural improvements.

When do I need to use adapters for codebase refactoring?

Use adapters for codebase refactoring when seams between tightly coupled modules need decoupling to improve testability. The Skill proposes concrete changes introducing adapters where new tests are required to exercise module interfaces effectively.

Can I use this approach for AI-assisted navigation of complex codebases?

Yes, this approach supports AI-assisted navigation of complex codebases by mapping architectural friction and deepening opportunities. It leverages existing project documentation like ADRs and domain glossaries to guide navigation through tightly coupled systems.