skills.rest
cropsgg
cropsggCOMMUNITY
Explore all skills by this author →
GitHub

architecture-improvement

Identify architecture smells and propose prioritized, PR-sized improvements for codebases.

15|5|Updated May 17, 2026
Search Tags:#architecture#refactoring#modularity#domain-driven-design#code-smells#architecture-review#incremental-improvement
One-click install
npx skills add https://github.com/cropsgg/skills --skill architecture-improvement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-improvement
Source: https://github.com/cropsgg/skills/tree/main/skills/engineering/architecture-improvement
Command: npx skills add https://github.com/cropsgg/skills --skill architecture-improvement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finds opportunities to deepen architectural boundaries and fix domain-misalignments in codebases, enabling more maintainable and scalable systems.

Core Features & Use Cases

  • Orient the codebase by surveying CONTEXT.md and repository layout to map boundaries and identify architectural smells.
  • Detect issues such as god modules, circular dependencies, and leaky abstractions, then propose 3–5 concrete, prioritized improvements.
  • Prioritize changes with an incremental, PR-sized plan that preserves behavior while reducing coupling.
  • Provide a clear rationale and implementation path to support multi-team collaboration and faster delivery.

Quick Start

Read CONTEXT.md, run a guided architecture audit on the current repo, and surface 3 concrete, incremental improvements with an implementation plan.

Frequently Asked Questions about architecture-improvement

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

FAQPage Schema
How do I identify code smells and architecture issues in a large codebase?▼

To identify architecture smells in a large codebase, survey the repository layout and CONTEXT.md to map boundaries, detecting god modules, circular dependencies, and leaky abstractions. This reveals concrete improvement opportunities for better modularity and maintainability.

How do I plan an incremental refactoring strategy that preserves existing behavior?▼

Plan incremental refactoring by prioritizing 3 to 5 concrete improvements into PR-sized changes. This approach reduces coupling and fixes domain misalignments while preserving behavior during maintenance or feature growth.

When do I need domain-driven design to fix architectural boundaries?▼

You need domain-driven design to fix architectural boundaries when a mid- to large codebase experiences feature growth, maintenance challenges, or domain misalignments. It helps deepen boundaries and deliver an actionable plan for scalable systems.

Can I use this architecture review approach for a mid-sized codebase with multiple modules?▼

Yes, this architecture review approach is specifically designed for mid- to large-codebases undergoing maintenance, refactoring, or feature growth across multiple modules. It maps boundaries and surfaces prioritized, incremental improvements.

What is the best way to resolve circular dependencies and leaky abstractions during an architecture audit?▼

The best way to resolve circular dependencies and leaky abstractions is conducting a guided architecture audit that proposes a clear implementation path. It delivers prioritized, PR-sized changes to reduce coupling and support multi-team collaboration.

Related Skills

Explore More Software Engineering Skills→
JasonWarrenUKJasonWarrenUK
5

domain-modeller

Map domain entities, relationships, and boundaries into Mermaid diagrams or Cypher structures.

Community
Intermediate
mimulmimul
5

refactor-rust

Identify Rust code smells and generate a prioritized refactoring plan.

Community
Advanced
Destynova2Destynova2
5

cli-audit-tangle

Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.

Community
Advanced
nguyenthienthanhnguyenthienthanh
24

bugfix-quick

Fix software bugs via a four-step TDD workflow with test verification.

Community
Basic