---

name: architecture-patterns version: 1.0.0 type: knowledge description: This skill should be used when designing system architecture, making architectural decisions, or evaluating design patterns. It provides guidance on common patterns, ADR templates, design principles, and tradeoff analysis. keywords: architecture, design, pattern, decision, tradeoffs, adr, system design, scalability, microservices, mvc, design patterns, solid auto_activate: true allowed-tools: [Read]

Architecture Patterns Skill

Architectural design patterns, decision frameworks, and system design principles.

When This Skill Activates

• Designing system architecture
• Writing Architecture Decision Records (ADRs)
• Evaluating design patterns
• Making architectural tradeoffs
• System design questions
• Keywords: "architecture", "design", "pattern", "adr", "system design", "scalability"

---

Core Concepts

Overview

This skill provides comprehensive guidance on architecture patterns. For detailed patterns and implementation examples, see the documentation files in docs/.

Key Topics:

• Detailed methodologies and best practices
• Implementation patterns and examples
• Common pitfalls and anti-patterns
• Cross-references to related skills

See: Documentation files in docs/ directory for complete details

---

Quick Reference

---

Progressive Disclosure

This skill uses progressive disclosure to prevent context bloat:

• Index (this file): High-level concepts and quick reference (<500 lines)
• Detailed docs: docs/*.md files with implementation details (loaded on-demand)

Available Documentation:

• docs/detailed-guide-1.md - Detailed implementation guide
• docs/detailed-guide-2.md - Detailed implementation guide
• docs/detailed-guide-3.md - Detailed implementation guide
• docs/detailed-guide-4.md - Detailed implementation guide

---

Cross-References

Related Skills:

• See PROJECT.md for complete skill dependencies

Related Tools:

• See documentation files for tool-specific guidance

---

Key Takeaways

1. Research existing patterns before implementing
2. Follow established best practices
3. Refer to detailed documentation for implementation specifics
4. Cross-reference related skills for comprehensive understanding