architecture-strategist

Analyze code changes for architectural pattern compliance and design integrity.

Updated Jun 28, 2022
One-click install
npx skills add https://github.com/pcasaretto/nix-home --skill architecture-strategist-pcasaretto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-strategist
Source: https://github.com/pcasaretto/nix-home/tree/main/home-manager/modules/common/pi/compound-engineering/skills/architecture-strategist
Command: npx skills add https://github.com/pcasaretto/nix-home --skill architecture-strategist-pcasaretto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain the structural integrity and design principles of a software system by analyzing code changes from an architectural perspective.

Core Features & Use Cases

  • Architectural Review: Analyzes code modifications for compliance with established patterns and design integrity.
  • Pattern Compliance: Verifies adherence to architectural patterns and best practices.
  • Use Case: When reviewing a Pull Request that introduces a new service or refactors an existing one, use this Skill to ensure it aligns with the overall system architecture and doesn't introduce anti-patterns.

Quick Start

Analyze the recent code changes for architectural compliance.

Frequently Asked Questions about architecture-strategist

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

FAQPage Schema
How do I review code changes for architectural compliance during a pull request?

Architectural compliance review analyzes code modifications to verify adherence to established design patterns, SOLID principles, and microservice boundaries before merging changes. It evaluates structural integrity to prevent anti-patterns from entering the system.

What is architectural pattern compliance and when do I need it?

Architectural pattern compliance verifies that code modifications align with established design principles and system boundaries. You need it during pull request reviews, new service additions, or structural refactoring evaluations to maintain system integrity.

How do I ensure microservice boundaries and API stability when adding a new service?

Ensuring microservice boundaries and API stability requires analyzing new service additions against existing architectural principles. This process validates that structural changes maintain design integrity, respect service boundaries, and preserve API contracts.

Can I use architectural review for refactoring evaluations?

Architectural review supports refactoring evaluations by analyzing structural code changes from a design integrity perspective. It verifies that refactored code maintains pattern compliance and adheres to SOLID principles without introducing anti-patterns.

What's the best way to prevent anti-patterns in microservices architecture?

Preventing anti-patterns in microservices architecture involves analyzing code changes against established patterns and design principles. This architectural review process ensures structural modifications maintain system integrity and respect service boundaries.