From aiup-alfresco
Validates ActiveMQ topic names, consumer groups, event types, and configurations in Alfresco Spring Boot Out-of-Process SDK against event API conventions. Triggered during /events code generation.
npx claudepluginhub aborroy/aiup-alfrescoThis skill is limited to using the following tools:
Validate **Out-of-Process** event-driven code against Alfresco Java Event API conventions.
Guides event-driven architecture: assesses infrastructure, selects brokers (Kafka, RabbitMQ, SQS, NATS), designs schemas with versioning, configures DLQ/retries, implements idempotency.
Provides Event-Driven Architecture patterns, antipatterns, and PHP-specific guidelines for EDA audits including messaging, pub/sub, sagas, and brokers like RabbitMQ/Kafka.
Implements Event-Driven Architecture patterns in Spring Boot: domain events, ApplicationEventPublisher, @TransactionalEventListener, Kafka producers/consumers, Spring Cloud Stream, and transactional outbox for reliable messaging.
Share bugs, ideas, or general feedback.
Validate Out-of-Process event-driven code against Alfresco Java Event API conventions.
This skill applies exclusively to the Spring Boot Out-of-Process SDK (
alfresco-java-sdk). In-Process extensions (behaviours, actions) run inside the ACS JVM and do not use this event bus — use behaviours/policies instead.
alfresco.repo.event2{extension-prefix}.{purpose}Valid event types from org.alfresco.event.sdk.model.v1:
NodeCreatedEvent, NodeUpdatedEvent, NodeDeletedEventContentCreatedEvent, ContentUpdatedEvent, ContentDeletedEventChildAssocCreatedEvent, ChildAssocDeletedEventPeerAssocCreatedEvent, PeerAssocDeletedEventspring.activemq.broker-url is setReport topology issues, naming violations, and missing error handling.