adding skills / agents / other to config
This commit is contained in:
22
ai/skills/architecture_reviewer/SKILL.md
Normal file
22
ai/skills/architecture_reviewer/SKILL.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
name: architecture-reviewer
|
||||
description: Expert skill for reviewing system architecture, design patterns, and scalability using public industry standards.
|
||||
---
|
||||
|
||||
# Architecture Reviewer Skill
|
||||
|
||||
This skill provides high-level design oversight, ensuring systems are resilient, scalable, and follow modern architectural patterns (e.g., Microservices, Event-Driven Architecture, 12-factor apps).
|
||||
|
||||
## Principles
|
||||
|
||||
1. **Public Standard Alignment**: Use world-class architectural principles (e.g., AWS Well-Architected Framework, Google Cloud Architecture Framework - public-facing).
|
||||
2. **Scalability & Resilience**: Evaluate designs for potential bottlenecks, single points of failure, and horizontal scalability.
|
||||
3. **Interface Design**: Favor gRPC/Protocol Buffers (public) or RESTful APIs (standardized) for component communication.
|
||||
4. **Security-First**: Ensure Zero Trust principles and data encryption are considered early in the planning.
|
||||
5. **Simplicity over Complexity**: Strongly favor simple, well-understood patterns over complex, custom solutions.
|
||||
|
||||
## Architecture Review Checklist
|
||||
- Is the system decoupled?
|
||||
- Are the data storage solutions appropriate for the access patterns?
|
||||
- How is observability (monitoring/logging) handled using public tools?
|
||||
- Does the design avoid vendor lock-in where possible?
|
||||
Reference in New Issue
Block a user