architecture-strategist

Analyze code changes for architectural consistency and design integrity.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill architecture-strategist-jikig-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-strategist
Source: https://github.com/jikig-ai/soleur/tree/main/.openhands/skills/architecture-strategist
Command: npx skills add https://github.com/jikig-ai/soleur --skill architecture-strategist-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that code changes align with established architectural patterns, preserve system integrity, and support scalable, maintainable software.

Core Features & Use Cases

  • Architecture review of changes: Assess alignment with design patterns, component boundaries, and architectural decisions.
  • Dependency and coupling analysis: Map dependencies, detect potential circular dependencies, and evaluate cohesion.
  • Principles and API contract checks: Verify compliance with SOLID, layering, abstraction, and interface stability; assess API contracts and data flow.
  • Use Case: In PR reviews, analyze proposed changes to ensure long-term architecture remains coherent.

Quick Start

Provide a structured architecture review for a proposed change by summarizing design intent, identifying architectural violations, and suggesting improvements.

Frequently Asked Questions about architecture-strategist

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

FAQPage Schema
How do I check code changes for architectural violations during a PR review?

You can review code changes for architectural violations by analyzing proposed modifications against established design patterns, component boundaries, and architectural decisions to ensure long-term system coherence and integrity.

What is dependency and coupling analysis in software architecture?

Dependency and coupling analysis in software architecture maps module dependencies, detects potential circular dependencies, and evaluates component cohesion to preserve system integrity and support scalable, maintainable software.

How do I verify API contracts and SOLID principles compliance in system design?

Verify API contracts and SOLID principles compliance by checking proposed code changes for layering, abstraction, interface stability, and data flow to ensure they align with established architectural patterns.

Can I use architecture review for evaluating microservices boundaries and scalability?

Yes, you can use architecture review for evaluating microservices boundaries and scalability by assessing dependencies, coupling, and component interactions across modules and services to determine impact on future evolution.

What is the best way to assess the impact of code changes on system maintainability?

The best way to assess the impact of code changes on system maintainability is to perform a structured architecture review summarizing design intent, identifying violations, and suggesting improvements for scalable evolution.