improve-codebase-architecture

Identify codebase deepening opportunities and produce candidate proposals aligned with ADRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill surfaces architectural friction and identifies deepening opportunities to convert shallow modules into deep ones, improving testability and AI-navigability.

Core Features & Use Cases

  • Explore domain glossary references and ADR constraints to ground deepening opportunities.
  • Present a prioritized list of candidates with files involved, problem, solution, and benefits.
  • Guided grilling loop to refine choices with user input and ADR context.

Quick Start

Run the agent to explore the codebase and present high-value deepening opportunities.

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 shallow modules into deep codebase architecture?

Refactor shallow modules into deep codebase architecture by identifying deepening opportunities that convert them into testable interfaces, aligning outputs with domain language and ADR constraints to improve navigability.

What is a deepening opportunity when improving codebase modularity?

A deepening opportunity is an architectural friction point where shallow modules are converted into deep, testable interfaces, producing candidates that detail involved files, the problem, the solution, and expected benefits.

How do I use ADRs and domain language to guide a codebase refactor?

Use ADRs and domain glossary references to ground codebase refactoring by surfacing candidates that align with architecture principles, highlighting conflicts with existing ADRs during a guided grilling loop.

Does this architectural refactoring approach require specific documentation files?

Yes, this architectural refactoring approach requires codebases with domain language references like CONTEXT.md and ADRs to ground deepening opportunities and surface conflicts with established architecture principles.

What's the best way to prioritize codebase refactoring candidates for testability?

Prioritize codebase refactoring candidates by evaluating expected benefits and involved files, refining choices through a guided grilling loop that incorporates user input and ADR context to target testability improvements.