improve-codebase-architecture

Identifies shallow modules and generates HTML architectural review reports.

63|9|Updated Jun 15, 2025
One-click install
npx skills add https://github.com/willdady/platypus --skill improve-codebase-architecture-willdady
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/willdady/platypus/tree/main/.agents/skills/improve-codebase-architecture
Command: npx skills add https://github.com/willdady/platypus --skill improve-codebase-architecture-willdady

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill addresses architectural friction where shallow, tightly-coupled modules make code difficult to test, understand, and maintain, specifically hindering AI-driven development.

Core Features & Use Cases

  • Architectural Review: Scans the codebase to identify shallow modules and leakage across seams.
  • Visual Reporting: Generates a self-contained HTML report with before/after diagrams to visualize deepening opportunities.
  • Design Vocabulary: Enforces a strict architectural glossary (module, interface, depth, seam, adapter, leverage, locality) to ensure consistent design discussions.

Quick Start

Run the improve-codebase-architecture skill to scan the current repository and generate an architectural review report in your temporary directory.

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 and dependency leakage in my codebase?

Identify shallow modules and dependency leakage by scanning the codebase structure to detect interface complexity across project domains. This architectural analysis highlights tightly-coupled seams that hinder testability and AI navigation.

What is the best way to refactor codebase architecture for AI-driven development?

Refactor codebase architecture by proposing changes that transform shallow modules into deep, testable components. This deepening process reduces friction and improves codebase navigation for AI-driven development.

How does visual reporting help with architectural refactoring decisions?

Visual reporting generates a self-contained HTML report with before and after diagrams. These reports visualize deepening opportunities and architectural seams to facilitate structural decision-making.

Can I enforce a consistent design vocabulary during codebase analysis?

Enforce a consistent design vocabulary by applying a strict architectural glossary during codebase analysis. This ensures standardized discussions around modules, interfaces, depth, seams, adapters, leverage, and locality.

When should I run an architectural review for codebase refactoring?

Run an architectural review when tightly-coupled modules make code difficult to test, understand, and maintain. This scan detects shallow structures and generates a refactoring report in your temporary directory.

Does this codebase analysis require any external dependencies?

This codebase analysis operates without external dependencies. It natively scans the current repository structure to identify architectural friction and generate self-contained visual HTML reports.