improve-codebase-architecture

Analyze .NET codebases to identify architectural friction and propose refactor opportunities.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/LeeSanderson/OpinionatedDotNetCodingStandards --skill improve-codebase-architecture-leesanderson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/LeeSanderson/OpinionatedDotNetCodingStandards/tree/main/.claude/skills/improve-codebase-architecture
Command: npx skills add https://github.com/LeeSanderson/OpinionatedDotNetCodingStandards --skill improve-codebase-architecture-leesanderson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies architectural friction in a codebase, suggesting improvements to make the codebase more testable and maintainable.

Core Features & Use Cases

  • Identify architectural friction: Detects shallow modules, tightly-coupled components, and integration risks.
  • Explore codebase: Navigates the codebase like an AI, identifying areas for improvement.
  • Propose refactor opportunities: Suggests module-deepening refactors as local issue RFCs.
  • Design interfaces: Generates multiple interface designs for deepened modules, considering different constraints.
  • Write issue file: Creates a markdown file in the issues/ directory with a refactor RFC template.

Quick Start

Use the improve-codebase-architecture skill to explore architectural improvements in your codebase.

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 tightly-coupled components in my codebase?▼

This Skill identifies architectural friction by analyzing your codebase structure to detect shallow modules, tightly-coupled components, and integration risks that reduce testability and maintainability.

What is the best way to refactor shallow modules into deep modules?▼

The best way to refactor shallow modules is using this Skill to propose module-deepening refactors and generate multiple interface designs that consider different constraints for improved codebase architecture.

How do I improve testability and maintainability in a .NET solution?▼

You can improve testability and maintainability in a .NET solution by analyzing dependency categories and testing strategies to pinpoint friction, then proposing targeted refactor opportunities and deepened module interfaces.

Can I automatically generate RFC documentation for codebase refactoring?▼

Yes, you can automatically generate RFC documentation because this Skill writes a markdown file into the issues directory using a dedicated refactor RFC template for each proposed module-deepening improvement.

Does this architecture refactoring approach work without specific testing frameworks?▼

This architecture refactoring approach works without external dependencies, but requires an existing codebase structure to analyze dependency categories and testing strategies before proposing interface designs and refactor opportunities.