improve-codebase-architecture

Identify shallow modules and propose prioritized refactor paths using CONTEXT.md and ADR guidance.

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

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

  • Identify shallow modules and surface opportunities to increase leverage.
  • Align with CONTEXT.md vocabulary and ADR decisions to guardrails changes.
  • Prioritize candidates by locality and leverage to minimize risk.

Quick Start

Run the Agent tool to explore the codebase and surface deepening opportunities for high-leverage refactors.

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 my codebase for refactoring?

Identify shallow modules by analyzing your codebase to surface deepening opportunities, applying CONTEXT.md vocabulary and ADR guidance to rank refactor candidates by leverage and locality for improved testability.

What is a deepening opportunity in software architecture?

A deepening opportunity is a refactoring path that turns shallow modules into deep ones, increasing their leverage and locality to improve overall codebase testability and AI-navigability while minimizing breaking changes.

How do I prioritize codebase refactors to minimize the risk of breaking changes?

Prioritize codebase refactors by ranking candidates based on leverage and locality, ensuring proposed safe refactor paths align with LANGUAGE.md terminology and ADR decisions to yield minimal risk of breaking changes.

Can I use CONTEXT.md vocabulary to guide architectural refactoring?

Yes, you can use CONTEXT.md vocabulary to guide architectural refactoring by applying its terminology to surface shallow modules, propose safe refactor paths, and ensure recommendations align with project-specific ADR guidance.

When do I need to refactor a codebase for AI-navigability?

Refactor a codebase for AI-navigability when architectural friction prevents efficient code exploration, requiring the identification of deepening opportunities to transform shallow modules into deep, testable structures.

What is the best way to improve codebase testability through architecture refactoring?

The best way to improve codebase testability is to surface architectural friction and apply deepening opportunities, transforming shallow modules into deep ones while prioritizing changes by leverage and locality to minimize risk.