skills.rest
anonymousminati
anonymousminatiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

improve-codebase-architecture

Analyze codebases to identify architectural friction and refactoring opportunities.

Updated May 31, 2026
Search Tags:#architecture#refactoring#testability#coupling#seams#leverage#locality
One-click install
npx skills add https://github.com/anonymousminati/Res-POS --skill improve-codebase-architecture-anonymousminati
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/anonymousminati/Res-POS/tree/main/.claude/skills/improve-codebase-architecture
Command: npx skills add https://github.com/anonymousminati/Res-POS --skill improve-codebase-architecture-anonymousminati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you find architectural friction in a codebase and turn it into concrete refactoring opportunities that improve testability, locality, and AI navigability.

Core Features & Use Cases

  • Explore the codebase to surface shallow modules, tight coupling, and hard-to-test seams.
  • Compare candidate refactors using depth, leverage, and locality to decide what to deepen first.
  • Guide architecture conversations with domain-aware language, ADR awareness, and interface design follow-up.
  • Use case: Ask it to review a repository and propose the best modules to consolidate before you rewrite tests or split services.

Quick Start

Ask the skill to analyze this repository and list the top architectural deepening opportunities with files, problems, solutions, and test benefits.

Frequently Asked Questions about improve-codebase-architecture

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

FAQPage Schema
How do I find architectural friction and shallow modules in my codebase?▼

To find architectural friction, analyze the codebase to surface shallow modules, tight coupling, and hard-to-test seams. This identifies refactoring opportunities that improve testability, locality, and AI navigability.

What is the best way to reduce module coupling and improve testability?▼

The best way to reduce coupling and improve testability is to compare candidate refactors using depth, leverage, and locality metrics to decide which shallow modules to deepen first.

How do I prioritize which modules to consolidate before rewriting tests or splitting services?▼

Prioritize modules to consolidate by analyzing the repository and listing top architectural deepening opportunities, comparing them by depth, leverage, and locality to maximize test benefits.

Can I use dependency-aware seam analysis to guide architecture redesign discussions?▼

Yes, you can use dependency-aware seam analysis to guide architecture conversations with domain-aware language, ADR awareness, and interface design follow-up for deeper, more testable modules.

When should I turn shallow modules into deep ones during a refactoring process?▼

Turn shallow modules into deep ones when architectural friction surfaces tight coupling and hard-to-test seams, requiring deeper module redesigns to improve leverage and locality before rewriting tests.

Related Skills

Explore More Software Engineering Skills→
malinskibeniaminmalinskibeniamin
3

improve-codebase-architecture

Analyze module coupling and depth to identify architecture deepening opportunities.

Community
Intermediate
haryelramalhoharyelramalho

codebase-design

Design deep modules with small interfaces and clean seams for complex codebases.

Community
Intermediate
notquenotque
415

feature-design

Facilitate collaborative feature design discussions and generate design documents.

Community
Intermediate
berkcangumusisikberkcangumusisik
11

complexity-report

Identify cyclomatic complexity hotspots in TypeScript or JavaScript codebases.

Community
Intermediate