improve-codebase-architecture

Identify architectural friction and generate visual HTML reports from codebases.

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

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, proposes deepening opportunities, and presents them in a visual HTML report.

Core Features & Use Cases

  • Codebase Scanning: Identifies shallow modules and architectural issues.
  • Visual Report Generation: Creates an HTML report with diagrams and recommendations.
  • Grilling Loop: Provides detailed exploration of selected opportunities.
  • Domain Model Integration: Utilizes project's domain model and design vocabulary.

Quick Start

Run the 'improve-codebase-architecture' skill to scan your codebase and generate a report.

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 modules in my codebase?

To identify architectural friction, a codebase scan detects shallow modules and structural issues. It evaluates your project's domain model and design vocabulary to surface deepening opportunities. The results are presented in a visual HTML report containing diagrams and actionable recommendations.

What is a deepening opportunity when refactoring codebase architecture?

A deepening opportunity is a proposed architectural improvement targeting structural friction to enhance module depth. The scan identifies these opportunities during a codebase review and enables detailed exploration through a grilling loop within the generated visual report.

Can I generate a visual report for my codebase architecture review?

Yes, you can generate a visual HTML report for codebase architecture reviews. The report includes diagrams and specific refactoring recommendations, helping you visualize architectural friction and proposed deepening opportunities within your project.

Do I need to provide a domain model for an architecture review?

Yes, an architecture review requires an understanding of the project's domain model and design vocabulary. This context is necessary to accurately identify architectural friction and propose relevant deepening opportunities during the codebase scanning process.

What is the best way to explore proposed refactoring opportunities after a codebase scan?

The best way to explore proposed refactoring opportunities is by using the grilling loop feature. After scanning the codebase, this feature provides detailed exploration of selected deepening opportunities directly within the generated visual HTML report.

Are there limitations when using automated codebase architecture reviews for refactoring?

A limitation of automated codebase architecture reviews is the dependency on the project's domain model and design vocabulary. Without accurate domain context, the identification of architectural friction and the quality of proposed deepening opportunities may be limited.