skills.rest
JeromyJSmith
JeromyJSmithCOMMUNITY
Explore all skills by this author →
GitHub

improve-codebase-architecture

Identify shallow modules and propose interface-focused refactoring candidates.

3|Updated May 11, 2026
Search Tags:#testing#architecture#refactoring#interfaces#codebase analysis#adapters#seams
One-click install
npx skills add https://github.com/JeromyJSmith/lattice-platform --skill improve-codebase-architecture-jeromyjsmith
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/JeromyJSmith/lattice-platform/tree/main/.agents/skills/improve-codebase-architecture
Command: npx skills add https://github.com/JeromyJSmith/lattice-platform --skill improve-codebase-architecture-jeromyjsmith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shallow architecture makes refactors risky, tests brittle, and codebase navigation difficult—because complexity spreads across many modules instead of concentrating behind stable interfaces.

Core Features & Use Cases

  • Deepening opportunity discovery: identifies places where modules are shallow, seams are weak, or complexity fails the deletion test.
  • Seam and adapter driven recommendations: classifies dependencies and proposes refactors that create real leverage at the interface.
  • Interface-first grilling loop: after you choose a candidate, iteratively refines constraints, dependencies, seam placement, and the deepened module shape.
  • ADR-aware guidance: surfaces conflicts when existing decisions contradict a worthwhile deepening opportunity.

Quick Start

Ask the skill to explore your lattice-platform codebase and list the top deepening opportunities that would improve locality and interface testability.

Frequently Asked Questions about improve-codebase-architecture

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

FAQPage Schema
How do I refactor a shallow codebase architecture to make modules easier to test?▼

Refactoring shallow architecture requires identifying deepening opportunities that concentrate complexity behind stable interfaces, turning brittle, hard-to-test modules into deep modules with clearer boundaries and improved locality.

What is the deletion test when analyzing codebase architecture?▼

The deletion test is an architectural analysis technique used to identify weak seams and shallow modules by evaluating whether removing a component exposes hidden complexity or fails to create real leverage at the interface.

Can I use architecture refactoring to make my code more AI-navigable?▼

Yes, making code more AI-navigable involves finding deepening opportunities that concentrate complexity at module interfaces and seams, allowing artificial intelligence tools to understand and traverse the codebase with greater clarity.

How do I plan refactors when existing ADRs contradict deepening opportunities?▼

ADR-aware guidance surfaces conflicts when existing architectural decisions contradict a worthwhile deepening opportunity, allowing you to address governance constraints before producing numbered candidate refactors for the interface.

What is the best way to find weak seams and shallow modules in a complex codebase?▼

Finding weak seams requires exploring domain vocabulary and applying seam discipline to classify dependencies, which proposes refactors that create real leverage at the interface rather than spreading complexity across many modules.

Related Skills

Explore More Software Engineering Skills→
jaehun0630jaehun0630

improve-codebase-architecture

Identify shallow modules and generate an HTML deepening report aligned with ADRs and domain language.

Community
Advanced
miptah21miptah21
2

improve-codebase-architecture

Identify architectural friction and propose refactors that deepen module interfaces.

Community
Intermediate
ian-pascoeian-pascoe
1

codebase-design

Design deep modules and clean interfaces for codebases.

Community
Intermediate
CANTAGESTUDIOCANTAGESTUDIO
3

refactor-arch-hotspots

Detect architectural hotspots by analyzing churn, coupling, and layer violations.

Community
Advanced