skills.rest
mikeleppane
mikeleppaneCOMMUNITY
Explore all skills by this author →
GitHub

improve-architecture

Analyze Rust module boundaries and categorize dependencies for refactor plans.

10|Updated Mar 20, 2026
Search Tags:#architecture#testability#rust#refactor#code-analysis#module-boundaries
One-click install
npx skills add https://github.com/mikeleppane/tursotui --skill improve-architecture-mikeleppane
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-architecture
Source: https://github.com/mikeleppane/tursotui/tree/main/.claude/skills/improve-architecture
Command: npx skills add https://github.com/mikeleppane/tursotui --skill improve-architecture-mikeleppane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify architectural friction in a codebase and surface opportunities to deepen module boundaries to improve testability and maintainability.

Core Features & Use Cases

  • Surface candidates for deepening, analyze coupling signals (visibility leaks, god enums, trait bloat, scattered impls), categorize dependencies according to the four categories, and propose actionable refactor plan templates.
  • Provide boundary-test recommendations and mapping to Rust-specific friction signals to guide deepening decisions.
  • Use cases include consolidating tightly-coupled modules and creating AI-navigable boundaries for testable architecture.

Quick Start

Explore the codebase with the Agent tool to surface architectural friction and deepening opportunities.

Frequently Asked Questions about improve-architecture

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

FAQPage Schema
How do I identify architectural friction in a Rust codebase to improve testability?▼

Identify architectural friction by analyzing Rust-specific signals like visibility leaks, scattered impls, and god enums to surface module deepening opportunities. This process categorizes dependencies and produces actionable refactor plan templates to improve testability and maintainable boundaries.

What are common Rust friction signals that indicate unclear module boundaries?▼

Common Rust friction signals for unclear module boundaries include visibility leaks, god enums, trait bloat, and scattered impls. Recognizing these coupling signals helps surface candidates for deepening shallow modules to establish more testable and maintainable architecture.

How do I analyze module coupling to create a structured dependency analysis in Rust?▼

Analyze module coupling by mapping Rust-specific friction signals to structured dependency categories like In-process, Local-substitutable, Ports & adapters, and Mock. This analysis surfaces architectural friction and provides boundary-test recommendations to guide deepening decisions.

When should I deepen shallow Rust modules to fix testability issues?▼

Deepen shallow Rust modules when architectural friction like visibility leaks and trait bloat scatter implementation logic and hinder testability. Deepening establishes clear module boundaries, enabling effective boundary tests and reducing dependency coupling.

Related Skills

Explore More Software Engineering Skills→
DIO0550DIO0550
1

file-search

Search Rust source files and symbols across a codebase.

Community
Intermediate
malinskibeniaminmalinskibeniamin
3

improve-codebase-architecture

Analyze module coupling and depth to identify architecture deepening opportunities.

Community
Intermediate
Luohao-YanLuohao-Yan
6

add-telemetry

Implement trait-based telemetry with enums for Rust event tracking.

Community
Advanced
EstebanForgeEstebanForge
4

improve-codebase-architecture

Analyze codebases to identify tightly coupled modules and dependency categories.

Community
Advanced