accessibility-patterns
WCAG 2.2 AA compliance, ARIA patterns, keyboard navigation, screen reader optimization
Message queue patterns with BullMQ, Kafka, RabbitMQ - saga, outbox, dead letter queue, exactly-once semantics.
$ npx -y skills add vibeeval/vibecosystem --skill event-driven-patterns --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/event-driven-patternsContext preview
The summary Claude sees to decide when to auto-load this skill.
Message queue patterns with BullMQ, Kafka, RabbitMQ - saga, outbox, dead letter queue, exactly-once semantics.
name: event-driven-patterns description: Message queue patterns with BullMQ, Kafka, RabbitMQ - saga, outbox, dead letter queue, exactly-once semantics.
Message queue and event bus patterns for decoupled, reliable async processing.
import { Queue, Worker, QueueEvents } from 'bullmq'
import Redis from 'ioredis'
const connection = new Redis(process.env.REDIS_URL!, { maxRetriesPerRequest: null })
// Producer: define queue
const emailQueue = new Queue('email', { connection })
const marketQueue = new Queue('market-resolution', { connection })
// Add job with options
await emailQueue.add(
'send-welcome',
{ userId: 'abc', email: 'user@example.com' },
{
attempts: 3,
backoff: { type: 'exponential', delay: 1000 },
removeOnComplete: { count: 1000 },
removeOnFail: { count: 5000 }
}
)
// Delayed job (send after 1 hour)
await emailQueue.add('send-reminder', { userId: 'abc' }, { delay: 3_600_000 })
// Consumer: named processor
const emailWorker = new Worker(
'email',
async (job) => {
if (job.name === 'send-welcome') {
await sendWelcomeEmail(job.data.email)
} else if (job.name === 'send-reminder') {
await sendReminderEmail(job.data.userId)
}
// Return value stored in job.returnvalue
return { sent: true, at: new Date().toISOString() }
},
{
connection,
concurrency: 10
}
)
emailWorker.on('completed', (job, result) => {
console.log(`Job ${job.id} completed:`, result)
})
emailWorker.on('failed', (job, err) => {
console.error(`Job ${job?.id} failed after ${job?.attemptsMade} attempts:`, err.message)
})import { Queue, Worker, QueueEvents } from 'bullmq'
const dlqQueue = new Queue('dead-letter', { connection })
const processingWorker = new Worker(
'orders',
async (job) => {
// Attempt processing
await processOrder(job.data)
},
{
connection,
concurrency: 5
}
)
// Move failed jobs to DLQ after all retries exhausted
processingWorker.on('failed', async (job, err) => {
if (!job) return
const isExhausted = job.attemptsMade >= (job.opts.attempts || 1)
if (isExhausted) {
await dlqQueue.add('order-failed', {
originalJob: job.name,
data: job.data,
error: err.message,
failedAt: new Date().toISOString(),
attempts: job.attemptsMade
})
console.error(`Job moved to DLQ: ${job.id}`)
}
})
// DLQ consumer: alert + manual review
const dlqWorker = new Worker('dead-letter', async (job) => {
await alertOpsTeam({
message: `Job failed permanently: ${job.data.originalJob}`,
data: job.data
})
}, { connection })// Problem: write to DB and publish event atomically (no lost messages)
// Solution: write event to outbox table in same transaction, relay worker reads and publishes
// DB schema
// CREATE TABLE outbox (
// id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
// aggregate_type TEXT NOT NULL,
// aggregate_id TEXT NOT NULL,
// event_type TEXT NOT NULL,
// payload JSONB NOT NULL,
// published_at TIMESTAMPTZ,
// created_at TIMESTAMPTZ DEFAULT now()
// );
async function createMarketWithOutbox(data: CreateMarketDto): Promise<Market> {
return db.$transaction(async (tx) => {
// 1. Write domain entity
const market = await tx.market.create({ data })
// 2. Write outbox event in SAME transaction
await tx.outbox.create({
data: {
aggregateType: 'Market',
aggregateId: market.id,
eventType: 'MarketCreated',
payload: { marketId: market.id, name: market.name, createdAt: market.createdAt }
}
})
return market
})
}
// Relay worker: poll outbox and publish (runs separately)
async function outboxRelay(): Promise<void> {
const unpublished = await db.outbox.findMany({
where: { publishedAt: null },
orderBy: { createdAt: 'asc' },
take: 100
})
for (const event of unpublished) {
try {
await publishToQueue(event.eventType, event.payload)
await db.outbox.update({
where: { id: event.id },
data: { publishedAt: new Date() }
})
} catch (err) {
console.error(`Outbox relay failed for ${event.id}:`, err)
}
}
}
// Poll every second
setInterval(outboxRelay, 1000)// Orchestrator drives the saga steps and handles compensation
interface SagaStep<T> {
name: string
execute: (ctx: T) => Promise<Partial<T>>
compensate: (ctx: T) => Promise<void>
}
class SagaOrchestrator<T extends Record<string, unknown>> {
constructor(private steps: SagaStep<T>[]) {}
async run(initialContext: T): Promise<T> {
const ctx = { ...initialContext }
const completed: SagaStep<T>[] = []
for (const step of this.steps) {
try {
const result = await step.execute(ctx)
Object.assign(ctx, result)
completed.push(step)
console.log(`Saga step '${step.name}' succeeded`)
} catch (err) {
console.error(`Saga step '${step.name}' failed, compensating...`)
// Compensate in reverse order
for (const done of completed.reverse()) {
try {
await done.compensate(ctx)
console.log(`Compensated '${done.name}'`)
} catch (compensateErr) {
console.error(`Compensation '${done.name}' failed:`, compensateErr)
// Log to manual intervention queue
}
}
throw err
}
}
return ctx
}
}
// Order fulfillment saga
interface OrderContext {
orderId: string
userId: string
amount: number
paymentId?: string
reservationId?: string
}
const orderSaga = new SagaOrchestrator<OrderContext>([
{
name: 'reserve-inventory',
execute: async (ctx) => {
const reservationId = await inventory.reserve(ctx.orderId)
return { reservationId }
},
compYour AI software team. Built on Claude Code. vibecosystem turns Claude Code into a full AI software team — 138 specialized agents that plan, build, review, test, and learn from every mistake. No configuration needed — just install and code.
Repo: vibeeval/vibecosystem
WCAG 2.2 AA compliance, ARIA patterns, keyboard navigation, screen reader optimization
axe-core integration, WCAG 2.2 AA checklist, keyboard navigation testing, screen reader testing, and ARIA pattern validation.
Steam-style achievement system with XP, levels, streaks, and skill trees. Gamifies the development workflow. 25 achievements across 5 categories.
Framework for measuring and tracking agent response quality over time. Detects regressions before they reach production. Use when evaluating agent changes,…
Agent ve skill dosyalarinin yapisal dogrulamasi. Frontmatter kontrol, naming convention, zorunlu bolum kontrolu, tutarlilik denetimi. Yeni agent/skill…