Software architecture patterns and design principles. Use when designing systems, making architectural decisions, reviewing code structure, or creating design documents. Provides SOLID, DDD, Clean Architecture, and API design guidance.
Provides software architecture guidance using SOLID principles and design patterns.
/plugin marketplace add curphey/bosun/plugin install curphey-bosun@curphey/bosunThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/api-quality-patterns.mdreferences/architect-research.mdreferences/architecture/microservices/grpc-communication.mdreferences/architecture/microservices/http-clients.mdreferences/architecture/microservices/message-queues.mdreferences/architecture/microservices/service-discovery.mdreferences/architecture/system-design-reference.mdreferences/backend-engineering/api-design-reference.mdArchitecture knowledge base for system design and code structure decisions.
| Principle | Description | Violation Sign |
|---|---|---|
| Single Responsibility | One reason to change | Class does too much |
| Open/Closed | Open for extension, closed for modification | Changing existing code for new features |
| Liskov Substitution | Subtypes substitutable for base types | Overrides that break contracts |
| Interface Segregation | Specific interfaces over general | Clients implement unused methods |
| Dependency Inversion | Depend on abstractions | High-level modules import low-level |
| Pattern | Best For | Avoid When |
|---|---|---|
| Monolith | Small teams, simple domains | Scaling concerns |
| Microservices | Large teams, complex domains | Simple applications |
| Hexagonal | Testability, port/adapter isolation | Quick prototypes |
| Event-Driven | Loose coupling, async workflows | Simple CRUD |
| CQRS | Read/write optimization | Simple domains |
┌─────────────────────────────────────┐
│ Frameworks & UI │ ← External (Web, DB, etc.)
├─────────────────────────────────────┤
│ Interface Adapters │ ← Controllers, Gateways
├─────────────────────────────────────┤
│ Application Logic │ ← Use Cases
├─────────────────────────────────────┤
│ Domain Entities │ ← Business Rules (innermost)
└─────────────────────────────────────┘
Dependencies point INWARD only
/users, /orders/api/v1/users# ADR-001: [Decision Title]
## Status
[Proposed | Accepted | Deprecated | Superseded]
## Context
[What is the issue? Why does this decision need to be made?]
## Decision
[What is the change being proposed?]
## Consequences
[What are the positive and negative results?]
src/
├── users/
│ ├── user.controller.ts
│ ├── user.service.ts
│ ├── user.repository.ts
│ └── user.entity.ts
├── orders/
│ └── ...
src/
├── controllers/
├── services/
├── repositories/
├── entities/
See references/ directory for detailed documentation:
architect-research.md - Comprehensive architecture patternsActivates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Activates when the user asks about Agent Skills, wants to find reusable AI capabilities, needs to install skills, or mentions skills for Claude. Use for discovering, retrieving, and installing skills.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.