How does the skill distinguish between minor and major issues?

It uses a P1-P3 severity scale: P1 for critical pattern violations and circular dependencies, P2 for layering concerns, and P3 for minor organizational improvements.

Which architectural patterns does this skill understand?

The Architecture Strategist is proficient in evaluating Layered, Hexagonal (Clean), Microservices, Event-Driven, and CQRS architectures.

Does it provide code examples in its findings?

Every architectural finding includes a 'Current Architecture' snippet highlighting the issue and a 'Recommended Approach' showing the architecturally sound implementation.

Can it help with refactoring legacy code?

Yes, it excels at identifying tight coupling and 'leaky' abstractions, providing clear recommendations on how to separate concerns into proper layers.

Architecture Strategist

Name: Architecture Strategist
Author: jovermier

byjovermier

Collaboration Tools

Evaluates code changes through an architectural lens to ensure system design integrity, proper layering, and component boundaries.

About

The Architecture Strategist is a specialized Claude Code skill designed for senior-level system analysis. It functions as an automated architect that reviews code for structural health, identifying layering violations, circular dependencies, and improper coupling. By applying industry-standard frameworks like Clean or Hexagonal Architecture, this skill helps development teams prevent architectural debt and ensures that every code change aligns with the long-term design goals of the project.

Key Features

Detailed coupling and cohesion assessments
Standardized reporting with P1-P3 severity guidelines and recommended fixes
Automated identification of architectural debt and boundary violations
Comprehensive layering and dependency direction analysis
0 GitHub stars
Support for Hexagonal, Clean, Microservices, and Event-Driven patterns

Use Cases

Identifying tight coupling between business logic and external frameworks
Reviewing complex pull requests to ensure they follow established system patterns
Generating Architectural Decision Records (ADRs) for significant design shifts

About

Key Features

Detailed coupling and cohesion assessments
Standardized reporting with P1-P3 severity guidelines and recommended fixes
Automated identification of architectural debt and boundary violations
Comprehensive layering and dependency direction analysis
0 GitHub stars
Support for Hexagonal, Clean, Microservices, and Event-Driven patterns

Use Cases

Identifying tight coupling between business logic and external frameworks
Reviewing complex pull requests to ensure they follow established system patterns
Generating Architectural Decision Records (ADRs) for significant design shifts