Archetypes

Archetypes from athola/claude-night-market.

by @athola 15 skills

Skills in this plugin

15
  1. ▌
    Architecture Paradigms · athola
    Routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing architecture trade-offs.
    350 repo stars
  2. ▌
    Architecture Paradigm Cqrs Es · athola
    CQRS and Event Sourcing. Use when reads and writes need separate models or every state change needs an audit trail.
    350 repo stars
  3. ▌
    Architecture Paradigm Layered · athola
    Layered n-tier architecture. Use for moderate systems needing presentation, domain, and persistence layers.
    350 repo stars
  4. ▌
    Architecture Paradigm Pipeline · athola
    Pipes-and-filters architecture. Use when data flows through discrete stages such as ETL, streaming, or CI/CD.
    350 repo stars
  5. ▌
    Architecture Paradigm Hexagonal · athola
    Hexagonal ports-and-adapters architecture. Use when the domain must stay testable apart from infrastructure.
    350 repo stars
  6. ▌
    Architecture Paradigm Serverless · athola
    Serverless FaaS patterns. Use for bursty event-driven workloads with pay-per-execution cost and little infrastructure.
    350 repo stars
  7. ▌
    Architecture Paradigm Microkernel · athola
    Microkernel architecture with a minimal core and plugins. Use when third parties extend a platform's core.
    350 repo stars
  8. ▌
    Architecture Paradigm Space Based · athola
    Applies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.
    350 repo stars
  9. ▌
    Architecture Paradigm Event Driven · athola
    Event-driven async messaging. Use when real-time or multi-subscriber systems need producers decoupled from consumers.
    350 repo stars
  10. ▌
    Architecture Paradigm Client Server · athola
    Applies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.
    350 repo stars
  11. ▌
    Architecture Paradigm Domain Driven · athola
    Models a business in its own language. Use when the domain has real business rules to capture.
    350 repo stars
  12. ▌
    Architecture Paradigm Microservices · athola
    Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
    350 repo stars
  13. ▌
    Architecture Paradigm Service Based · athola
    Applies coarse-grained service architecture for deployment independence. Use when independent deployment is needed but shared databases rule out microservices.
    350 repo stars
  14. ▌
    Architecture Paradigm Functional Core · athola
    Applies 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.
    350 repo stars
  15. ▌
    Architecture Paradigm Modular Monolith · athola
    Modular monolith with enforced internal boundaries. Use for service-level autonomy without a distributed system.
    350 repo stars