Review Software Architecture
Skill Verifiziert AktivReview software architecture for coupling, cohesion, SOLID principles, API design, scalability, and technical debt. Covers system-level evaluation, architecture decision record review, and improvement recommendations. Use when evaluating a proposed architecture before implementation, assessing an existing system for scalability or security, reviewing ADRs, performing a technical debt assessment, or evaluating readiness for significant scale-up.
To provide a systematic and expert-level review of software architecture, ensuring quality, maintainability, and readiness for scale.
Funktionen
- Evaluate coupling and cohesion
- Assess adherence to SOLID principles
- Review API design and consistency
- Analyze system scalability and reliability
- Catalog and prioritize technical debt
- Review Architecture Decision Records (ADRs)
Anwendungsfälle
- Evaluating proposed architectures before implementation
- Assessing existing systems for scalability or security
- Reviewing Architecture Decision Records (ADRs)
- Performing technical debt assessments
- Evaluating system readiness for significant scale-up
Nicht-Ziele
- Performing line-level code review or focusing on PR-level changes
- Prescribing specific technologies without clear technical justification
- Evaluating team structure or project management practices
Invocation
- info:Scoped toolsThe skill lists `Read`, `Grep`, `Glob`, `Bash`, and `WebFetch` as allowed tools. While `Bash` and `WebFetch` can be broad, the skill's procedure outlines specific commands like `npx madge` and `grep`, suggesting focused usage rather than arbitrary execution.
Practical Utility
- info:Usage examplesThe SKILL.md provides command examples for specific analysis steps (e.g., `npx madge`), but does not offer full end-to-end examples of the complete review process with claimed output.
Installation
/plugin install agent-almanac@pjt222-agent-almanacQualitätspunktzahl
VerifiziertVertrauenssignale
Ähnliche Erweiterungen
Architecture Decision Records
99Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
Backend Api Design
99Design RPC-style APIs with layered architecture (Controller → Manager → Repository). Use when creating new API endpoints, designing API contracts, or reviewing API patterns.
System Design
99Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.
Architecture Designer
95Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.
Sdk Dx
100Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: "SDK design", "developer experience", "API design", "SDK DX", "error messages", "type safety", "IDE integration", "SDK versioning", "migration guides", "client library design", "making SDKs feel native", "SDK best practices"
V3 Ddd Architecture
100Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.