Architecture Guardian FAQs

Question 1

How does this skill improve my development workflow?

Accepted Answer

It reduces technical debt by catching structural violations early—before they are merged. By automating the 'architect' persona, it provides instant feedback on whether logic is leaking into the wrong layers (e.g., UI logic in the core engine) and suggests the correct design patterns to use.

Question 2

When should I use the Architecture Guardian skill?

Accepted Answer

You should invoke this skill proactively during the planning phase of a new feature to validate your approach, or reactively before committing significant changes to ensure the implementation doesn't violate separation of concerns or introduce anti-patterns.

Question 3

What does the Architecture Guardian skill do?

Accepted Answer

Architecture Guardian acts as an automated architect within Claude Code. It evaluates proposed code changes against your project's documented architectural principles (like docs/ARCHITECTURE.md) to ensure layer boundaries are respected, design patterns are followed, and structural integrity is maintained.

Question 4

Does Architecture Guardian support custom design patterns?

Accepted Answer

Yes. While it comes configured for modular systems (like RPG engines), it uses your local documentation as the source of truth. By reading your project's ARCHITECTURE.md and DESIGN_PATTERNS.md, it adapts its review criteria to match your specific coding standards and evolution goals.

Question 5

What specific architectural issues can it detect?

Accepted Answer

The skill identifies layer boundary violations, missing middleware for cross-cutting concerns, improper data access patterns, and deviations from established design patterns like Factory, Strategy, or Observer. It provides a clear 'Approved' or 'Rejected' status with actionable improvement steps.

Architecture Guardian

Architecture Guardian

主要功能

使用场景

主要功能

使用场景