Archetypes
Archetypes from athola/claude-night-market.
Skills in this plugin
15- ▌ Architecture Paradigms · atholaRoutes to the right architecture paradigm. Use when choosing patterns for a new system or comparing architecture trade-offs.
- ▌ Architecture Paradigm Cqrs Es · atholaCQRS and Event Sourcing. Use when reads and writes need separate models or every state change needs an audit trail.
- ▌ Architecture Paradigm Layered · atholaLayered n-tier architecture. Use for moderate systems needing presentation, domain, and persistence layers.
- ▌ Architecture Paradigm Pipeline · atholaPipes-and-filters architecture. Use when data flows through discrete stages such as ETL, streaming, or CI/CD.
- ▌ Architecture Paradigm Hexagonal · atholaHexagonal ports-and-adapters architecture. Use when the domain must stay testable apart from infrastructure.
- ▌ Architecture Paradigm Serverless · atholaServerless FaaS patterns. Use for bursty event-driven workloads with pay-per-execution cost and little infrastructure.
- ▌ Architecture Paradigm Microkernel · atholaMicrokernel architecture with a minimal core and plugins. Use when third parties extend a platform's core.
- ▌ Architecture Paradigm Space Based · atholaApplies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.
- ▌ Architecture Paradigm Event Driven · atholaEvent-driven async messaging. Use when real-time or multi-subscriber systems need producers decoupled from consumers.
- ▌ Architecture Paradigm Client Server · atholaApplies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.
- ▌ Architecture Paradigm Domain Driven · atholaModels a business in its own language. Use when the domain has real business rules to capture.
- ▌ Architecture Paradigm Microservices · atholaApplies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
- ▌ Architecture Paradigm Service Based · atholaApplies coarse-grained service architecture for deployment independence. Use when independent deployment is needed but shared databases rule out microservices.
- ▌ Architecture Paradigm Functional Core · atholaApplies Functional Core, Imperative Shell to isolate logic from side effects. Use when business logic is entangled with I/O or unit tests are slow and brittle.
- ▌ Architecture Paradigm Modular Monolith · atholaModular monolith with enforced internal boundaries. Use for service-level autonomy without a distributed system.