architecture-review

Audit project structure and map dependencies to plan incremental refactors.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/zagarlucas/zagarlucas.github.io --skill architecture-review-zagarlucas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/zagarlucas/zagarlucas.github.io/tree/main/.continue/skills/architecture-review
Command: npx skills add https://github.com/zagarlucas/zagarlucas.github.io --skill architecture-review-zagarlucas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve project structure, identify bottlenecks, and plan incremental refactors to improve maintainability and reduce complexity.

Core Features & Use Cases

  • Map current structure and dependencies to surface module boundaries.
  • Enforce clear boundaries between UI, logic, and data layers to reduce coupling.
  • Promote co-location of related code and support incremental migrations with tests.

Quick Start

Map current structure, dependency graph, and module boundaries, then draft a phased migration plan and validation tests.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I audit project structure to identify module boundaries and dependency hotspots?

A project structure audit maps current dependencies and module boundaries to reveal hotspots. It identifies bottlenecks and coupling between UI, logic, and data layers, enabling targeted refactoring and incremental migrations.

What is the best way to plan incremental architecture refactoring without breaking existing features?

Plan incremental architecture refactoring by drafting a phased migration plan with test-backed guardrails. Enforce clear module boundaries and co-locate related code to reduce complexity and maintain feature stability.

How does dependency analysis help improve code quality and reduce coupling?

Dependency analysis improves code quality by mapping the dependency graph to enforce clear boundaries between core layers. This reduces coupling, surfaces structural bottlenecks, and supports maintainable incremental migrations.

Can I use this approach to migrate a feature-based architecture to enforce layer separation?

Yes, you can migrate feature-based architectures by mapping current layers and enforcing clear boundaries between UI, logic, and data. The process supports incremental migrations with measurable impact and validation tests.

What are the limitations of refactoring project structure without test-backed guardrails?

Refactoring without test-backed guardrails risks unsafe structural changes and broken dependencies. Architecture review requires validation tests and documentation to ensure safe, maintainable changes and reduce complexity.