improve-codebase-architecture

Identify deepening opportunities in codebases using ADRs and CONTEXT.md vocabulary.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface architectural friction and propose deepening opportunities — refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability.

Core Features & Use Cases

  • Read domain glossary and ADRs to identify friction points
  • Propose concrete deepening opportunities to improve locality and leverage
  • Conduct grilling loop to refine designs and surface decisions

Quick Start

Begin by reading CONTEXT.md, ADRs, and start an exploration with the Agent tool.

Frequently Asked Questions about improve-codebase-architecture

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

FAQPage Schema
How do I refactor a tangled codebase to improve module depth and testability?

To refactor a tangled codebase, identify shallow modules and surface deepening opportunities using CONTEXT.md vocabulary and ADRs. This approach validates refactors with tests and guides architecture decisions to improve testability and AI-navigability.

What is a deepening opportunity in software architecture?

A deepening opportunity is a refactor that turns shallow modules into deep ones to improve locality and leverage. It addresses architectural friction in tangled codebases, aiming to enhance testability and AI-navigability.

How do I use ADRs to guide codebase refactoring decisions?

ADRs guide refactoring by aligning deepening opportunities with documented architecture decisions. Reading ADRs alongside a domain glossary identifies friction points and validates proposed refactors through a grilling workflow.

Can I use this approach for large codebases with tangled modules?

Yes, this approach specifically targets large codebases with tangled modules. It leverages CONTEXT.md vocabulary and a grilling workflow to surface actionable deepening candidates and ADR-aligned refactors for complex architectures.

What's the best way to surface architectural friction in a shallow codebase?

The best way to surface architectural friction is reading a domain glossary and ADRs to identify friction points, then conducting a grilling loop. This refines designs and proposes concrete deepening opportunities for shallow modules.

When should I not use deepening refactors for architecture improvements?

Deepening refactors target large codebases with tangled modules and shallow architectures. If your codebase is small, already deeply structured, or lacks ADRs and CONTEXT.md documentation, this grilling workflow approach may not apply.