LogoClawIndex
CasesSkillsAbout
LogoClawIndex

ClawIndex

OpenClaw Skills & Use Case Index

ClawIndex is an ecosystem-driven index of OpenClaw skills and real-world use cases.

Index

Skills·
Cases

Meta

About·
Disclaimer·
Email·
GitHub
© 2026 ClawIndex All Rights Reserved.

Skills tagged: event-driven architecture

Browse skills that share this tag.

  • event-driven-expert - Design and troubleshoot event-driven systems
    event-driven architectureKafkaRabbitMQmessage queues

    ★ 12 · Updated 2026-10-08

    Provides expert guidance for designing, implementing, and troubleshooting event-driven systems, messaging, event sourcing, CQRS, and asynchronous workflows.

    ⚙ Design event schemas⚙ Configure Kafka producers⚙ Implement Kafka consumers
  • excalidash-event-driven-diagrammer - Event-Driven Architecture Diagrammer
    event-driven architecturepub-subevent streamingmessage broker

    ★ 2 · Updated 2026-10-07

    Create or review event-driven architecture diagrams with producers, brokers, consumers, event stores, and distinct synchronous and asynchronous edges.

    ⚙ Create event-driven diagrams⚙ Review event-driven diagrams⚙ Map producers and consumers
  • microservices-patterns - Design microservice architectures with established patterns
    microservicesdistributed systemsservice decompositionevent-driven architecture

    ★ 6 · Updated 2026-10-05

    Design microservice architectures using service boundaries, inter-service communication, data management, event-driven communication, and resilience patterns.

    ⚙ Decompose monoliths by business capability⚙ Map subdomains to services⚙ Design service boundaries and contracts
  • backend-architect - Design scalable backend systems and APIs
    backend architectureAPI designmicroservicesdistributed systems

    ★ 0 · Updated 2026-10-05

    Design scalable, resilient, and maintainable backend systems, APIs, microservices, and distributed architectures.

    ⚙ Capture domain requirements⚙ Define service boundaries⚙ Design API contracts
  • backend-architect - Design scalable and resilient backend systems
    backend architectureAPI designmicroservicesdistributed systems

    ★ 0 · Updated 2026-10-05

    Designs scalable backend services and APIs, including service boundaries, integration patterns, resilience, security, and observability.

    ⚙ Capture domain requirements⚙ Define service boundaries⚙ Design API contracts
  • backend-architect - Design scalable backend systems and APIs
    backend architectureAPI designmicroservicesdistributed systems

    ★ 22 · Updated 2026-10-05

    Designs scalable backend services and APIs, including service boundaries, contracts, integration patterns, resilience, and observability.

    ⚙ Capture domain requirements⚙ Define service boundaries⚙ Design API contracts
  • backend-architect - Design scalable backend systems and APIs
    backend architectureAPI designmicroservicesdistributed systems

    ★ 0 · Updated 2026-10-04

    Designs scalable, resilient, and maintainable backend systems, APIs, microservices, and distributed architectures.

    ⚙ Design RESTful APIs⚙ Define API contracts⚙ Decompose services by domain
  • backend-architect - Design scalable backend systems and APIs
    backend architectureAPI designmicroservicesdistributed systems

    ★ 0 · Updated 2026-10-04

    Designs scalable backend services and APIs, including service boundaries, contracts, integration patterns, resilience, and observability.

    ⚙ Define service boundaries⚙ Design API contracts⚙ Choose architecture patterns
  • backend-architect - Design scalable backend systems and APIs
    backend architectureAPI designmicroservicesdistributed systems

    ★ 0 · Updated 2026-10-04

    Designs scalable backend services and APIs, including service boundaries, data contracts, integration patterns, resilience, scaling, and observability.

    ⚙ Design backend APIs⚙ Define service boundaries⚙ Specify data contracts
  • backend-architect - Design scalable backend architectures and APIs
    backend architectureAPI designmicroservicesdistributed systems

    ★ 0 · Updated 2026-10-04

    Designs scalable backend services and APIs, including service boundaries, contracts, integration patterns, resilience, security, and observability.

    ⚙ Capture domain requirements⚙ Define service boundaries⚙ Design API contracts
  • backend-development - Backend DDD Development Patterns
    backend developmentdomain-driven designhexagonal architectureREST API

    ★ 666 · Updated 2026-10-04

    Provides guidance for implementing backend features with DDD, hexagonal architecture, event-driven integration, REST APIs, and HATEOAS.

    ⚙ Apply DDD architecture patterns⚙ Design aggregate roots⚙ Define domain entities
  • microservices-patterns - Design resilient microservices architectures
    microservicesdistributed systemsservice architectureevent-driven architecture

    ★ 0 · Updated 2026-10-04

    Design microservices architectures using service boundaries, event-driven communication, data management, and resilience patterns.

    ⚙ Decompose monoliths into services⚙ Define service boundaries⚙ Design service contracts
  • event-driven-architect - Design event-driven systems with domain events
    event-driven architectureevent sourcingCQRSpub/sub

    ★ 22 · Updated 2026-10-03

    Designs event-driven architectures using event sourcing, CQRS, pub/sub, event buses, and domain events for decoupled systems.

    ⚙ Define domain events⚙ Design event schemas⚙ Implement event buses
  • orthogonality-principle - Design independent, loosely coupled components
    software architecturemodular designseparation of concernsdependency injection

    ★ 666 · Updated 2026-09-30

    Guides module, API, and system architecture design toward independent, non-overlapping components whose changes do not unexpectedly affect others.

    ⚙ Separate unrelated responsibilities⚙ Define focused interfaces⚙ Inject dependencies
  • arch-cross-service-integration - Cross-Service Integration Workflow
    microservicesservice communicationdata synchronizationmessage bus

    ★ 666 · Updated 2026-05-28

    Design and implement cross-service communication, data synchronization, and service boundary patterns

    ⚙ Identify source and target services⚙ Determine data ownership⚙ Choose communication pattern