archetypes

Plugin archetypes from marketplace claude-night-market in athola/claude-night-market. Commands read from the repo's manifest — 6 days ago.

Skills (15)

• architecture-paradigm-client-server

  Applies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.

• architecture-paradigm-cqrs-es

  Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.

• architecture-paradigm-domain-driven

  Models a business in its own language. Use when the domain has real business rules to capture.

• architecture-paradigm-event-driven

  Applies event-driven async messaging to decouple producers and consumers. Use when designing real-time or multi-subscriber systems needing loose coupling.

• architecture-paradigm-functional-core

  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.

• architecture-paradigm-hexagonal

  Applies hexagonal architecture isolating domain from infrastructure. Use when designing systems where testability and port/adapter separation are priorities.

• architecture-paradigm-layered

  Applies layered n-tier architecture with enforced boundaries. Use when designing moderate systems needing clear presentation, domain, and persistence layers.

• architecture-paradigm-microkernel

  Applies microkernel architecture with minimal core and plugin extensibility. Use when building platforms where third parties extend core functionality.

• architecture-paradigm-microservices

  Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.

• architecture-paradigm-modular-monolith

  Applies modular monolith with enforced internal boundaries. Use when teams want service-level autonomy without distributed system overhead.

• architecture-paradigm-pipeline

  Applies pipes-and-filters for sequential data transformations. Use when data flows through discrete stages like ETL, streaming analytics, or CI/CD pipelines.

• architecture-paradigm-serverless

  Applies serverless FaaS patterns for event-driven workloads. Use when designing bursty workloads with minimal infrastructure and pay-per-execution cost model.

• architecture-paradigm-service-based

  Applies coarse-grained service architecture for deployment independence. Use when independent deployment is needed but shared databases rule out microservices.

• architecture-paradigm-space-based

  Applies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.

• architecture-paradigms

  Selects and routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing trade-offs before making architecture decisions.

Similar plugins