improve-codebase-architecture

Scan a codebase for module deepening opportunities and present them as a visual HTML report.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/salomepoulain/makery-stations --skill improve-codebase-architecture-salomepoulain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/salomepoulain/makery-stations/tree/main/stations/claude/workbench/pantry/skills/improve-codebase-architecture
Command: npx skills add https://github.com/salomepoulain/makery-stations --skill improve-codebase-architecture-salomepoulain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate shallow modules whose interfaces are nearly as complex as their implementations, making them hard to test and navigate. This Skill surfaces that architectural friction and proposes concrete deepening refactors, presented visually rather than as a wall of prose. ## Core Features & Use Cases - Hot-spot-driven exploration: Scopes the scan using git history and user direction, then applies the deletion test to find shallow modules, seam leakage, and poor locality. - Visual HTML report: Generates a self-contained report in the OS temp directory using Tailwind and Mermaid via CDN, with before/after diagrams, recommendation-strength badges, and ADR conflict callouts for each candidate. - Guided decision loop: After the user picks a candidate, it grills through constraints and dependencies, updates CONTEXT.md domain vocabulary, and offers ADRs for load-bearing rejections. - Use Case: Point it at a subsystem where bugs keep recurring; it identifies that pricing logic leaks across a seam, renders a before/after diagram of the deepened module, and walks you through the refactor decision. ## Quick Start Ask the assistant to review the architecture of the order intake subsystem and show deepening opportunities as an HTML report.

Frequently Asked Questions about improve-codebase-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I not use automated architecture review?

Skip it when the codebase has no clear change history to scope the scan, or when the friction is purely stylistic rather than structural. The Skill targets module depth, seams, and testability, not formatting or naming preferences.