improve-codebase-architecture

Identify architectural friction and module deepening opportunities for RFC planning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineering teams surface friction points between modules, identify shallow vs deep boundaries, and generate RFC-ready improvements to architecture and testability.

Core Features & Use Cases

  • Guided exploration of a codebase to surface architectural friction and boundary complexity.
  • Candidate RFC generation and documentation support for module deepening.
  • Planning and risk assessment for refactors, with testability improvements and traceable recommendations.

Quick Start

Run a guided exploration to surface architectural friction and RFC-ready 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 identify architectural friction and shallow module boundaries in my codebase?

Identify architectural friction by evaluating module interfaces and dependency patterns to surface coupling complexity. This reveals shallow boundaries and highlights opportunities to deepen modules for safer refactoring.

What is the best way to plan a refactor without executing code?

Plan refactors by assessing module boundaries and testability to generate traceable recommendations. This approach frames improvements for architecture reviews without needing to execute the codebase.

How do I generate an RFC for improving codebase architecture and testability?

Generate an RFC by analyzing architectural friction and boundary complexity across your components. This produces candidate RFC documentation and risk assessments for module deepening and testability improvements.

Can I use this approach to evaluate dependency patterns for architecture reviews?

Yes, you can evaluate dependency patterns and module interfaces to inform architecture reviews. This helps assess coupling and boundary depth to guide RFC planning and refactoring decisions.

When do I need to analyze module boundaries for safer refactoring?

You need to analyze module boundaries when understanding coupling and testability across components is necessary. This evaluation informs RFC planning and identifies deepening opportunities to reduce refactor risk.