improve-codebase-architecture

Identify codebase deepening opportunities aligned with ADR decisions.

356|59|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/amazingloft999-droid/mattpocock-skills --skill improve-codebase-architecture-amazingloft999-droid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/amazingloft999-droid/mattpocock-skills/tree/main/skills/engineering/improve-codebase-architecture
Command: npx skills add https://github.com/amazingloft999-droid/mattpocock-skills --skill improve-codebase-architecture-amazingloft999-droid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find deepening opportunities in a codebase to improve architecture, align with domain language, and avoid regressions by consolidating tightly-coupled modules and making the codebase more AI-navigable.

Core Features & Use Cases

  • Explore the codebase to surface shallow modules and seams that constrain testability and AI navigability.
  • Present actionable deepening candidates with files involved, the current friction, a plain-English solution, and expected locality and leverage.
  • Support ADR awareness by surfacing conflicts and documenting decisions when deepening candidates contradict existing ADRs.

Quick Start

Inspect a repository to identify deepening opportunities, then select a candidate to grill and refine with the user.

Frequently Asked Questions about improve-codebase-architecture

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

FAQPage Schema
How do I find deepening opportunities to improve codebase architecture?

To improve codebase architecture, explore the repository to surface shallow modules and seams that constrain testability and AI navigability, returning a prioritized, actionable list of proposed changes with involved files and current friction.

What are architectural seams and how do they affect testability and modularity?

Architectural seams are shallow modules or tightly-coupled points in a codebase that constrain testability and modularity by making the codebase less AI-navigable and harder to refactor without regressions.

How do I refactor tightly-coupled modules without causing domain misalignment?

Refactor tightly-coupled modules by framing deepening candidates using CONTEXT.md vocabulary and ADR decisions, ensuring domain alignment and traceability by documenting decisions when candidates contradict existing ADRs.

Can I analyze a codebase for friction points and get actionable refactoring steps?

Yes, you can inspect a repository to identify deepening opportunities and receive a prioritized list of candidates detailing involved files, current friction, plain-English solutions, and expected locality and leverage.

What is the best way to prioritize codebase refactoring tasks by leverage and locality?

Prioritize refactoring tasks by evaluating actionable deepening candidates that explicitly outline expected locality and leverage, allowing you to target tightly-coupled modules that maximize architectural improvement and AI navigability.

When should I document ADR conflicts during a codebase architecture refactor?

Document ADR conflicts during a refactor when identified deepening candidates contradict existing ADR decisions, ensuring that architectural changes maintain domain alignment and traceability within the codebase.