architecture-guardian

Review architecture decisions and code changes against documented principles.

1|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/JoeCotellese/rpggame --skill architecture-guardian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-guardian
Source: https://github.com/JoeCotellese/rpggame/tree/main/.claude/skills/architecture-guardian
Command: npx skills add https://github.com/JoeCotellese/rpggame --skill architecture-guardian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as an automated architect, preventing architectural drift and technical debt. It ensures that all proposed code changes and new features adhere to established design principles, layer boundaries, and design patterns, saving development time and reducing future refactoring efforts.

Core Features & Use Cases

  • Proactive Design Review: Evaluate proposed changes before coding to catch architectural violations early in the development cycle.
  • Compliance Check: Verify code against documented architectural rules, such as layer boundaries, combat action patterns, and context assembly, ensuring consistency and maintainability.
  • Technical Debt Prevention: Guides developers to maintain a clean, extensible, and testable codebase, reducing long-term maintenance costs.
  • Use Case: Before implementing a new 'Dash' combat action, invoke this skill to ensure the design correctly uses the middleware pattern and avoids introducing game logic into the UI layer, thereby maintaining architectural integrity.

Quick Start

Review the proposed design for the new 'Dash' combat action, ensuring it adheres to the game's architectural principles and layer boundaries.

Frequently Asked Questions about architecture-guardian

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

FAQPage Schema
How do I review code changes against architectural principles before committing?

Architecture review evaluates proposed code against documented design principles, layer boundaries, and patterns to catch violations early. This skill consults architecture documentation and verifies compliance with established rules like separation of concerns and design patterns, preventing drift before code is merged.

What's the best way to prevent architectural drift in a codebase?

Preventing architectural drift requires proactive design review of new features and refactoring against documented architecture principles. This skill applies before coding to verify layer boundaries, adherence to patterns, and cross-cutting concerns, reducing technical debt and future refactoring costs.

How do I ensure new features comply with existing design patterns?

Design pattern compliance is enforced by reviewing proposed changes against documented patterns and layer architecture before implementation. This skill verifies that features like new combat actions use middleware correctly, avoid logic in UI layers, and maintain separation of concerns.

Can I use architecture review for refactoring decisions?

Yes, architecture review applies to refactoring and subsystem modifications to ensure changes maintain layer boundaries and design patterns. It evaluates proposed refactoring against documented principles to guide developers toward clean, extensible, testable code.

What documentation does an architecture review require?

Architecture review consults documented rules in ARCHITECTURE.md, DESIGN_PATTERNS.md, and project configuration files. These documents define layer boundaries, design patterns, and compliance rules that the review validates against proposed code changes.

How does architecture review reduce technical debt?

Technical debt prevention happens by catching architectural violations early through proactive review before coding. By enforcing layer boundaries and pattern adherence upfront, this skill guides developers to maintain clean, maintainable code and reduces long-term refactoring and maintenance costs.