improve-codebase-architecture

Identify architectural smells in .NET codebases and draft RFCs for module refactors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify architectural friction in a .NET codebase, such as shallow modules, anemic models, fat controllers, EF Core leakage, and other smells, to surface opportunities for deep-module refactors.

Core Features & Use Cases

  • Surface architecture smells and friction signals across the codebase
  • Propose RFCs for deep-module refactors with an actionable plan
  • Assist teams during architecture reviews and RFC drafting, including HITL governance

Quick Start

Scan the repository for architectural smells and draft a HITL RFC for each finding.

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 architecture smells in a .NET codebase?

To identify architecture smells in a .NET codebase, scan the repository to surface friction signals like shallow modules, anemic models, fat controllers, and EF Core leakage. This reveals opportunities for deep-module refactors.

What is the best way to plan a deep module refactor?

The best way to plan a deep module refactor is to frame architecture friction and propose an actionable RFC. This outlines deep module boundaries and structural changes ready for human-in-the-loop review.

How do I draft an RFC for codebase refactoring?

You draft an RFC for codebase refactoring by enumerating friction signals and architecture smells, then outlining an actionable plan. The RFC is generated ready for human-in-the-loop review using reference documentation guidance.

Can I use this for an architecture review on an existing project?

Yes, you can use this during architecture reviews and codebase health assessments across existing projects. It evaluates your codebase to surface deep module boundaries and enumerate friction signals.

What are common .NET architecture smells to look for?

Common .NET architecture smells include shallow modules, anemic models, fat controllers, and EF Core leakage. Surfacing these friction signals across the codebase helps identify areas requiring deep refactoring.