quasar-queue

Expert in background jobs and message queues using Gravito Quasar. Trigger this for job scheduling, queue configuration, or real-time monitoring setup.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill serves as a specialized systems engineering assistant for managing background jobs and message queues within the Gravito Quasar ecosystem. It streamlines the design, implementation, and monitoring of distributed tasks using BullMQ or BeeQueue, ensuring high reliability through type-safe payloads, robust retry logic, and Redis-backed storage configurations.

Use Cases

  • Architecting scalable background job systems by selecting and configuring the appropriate queue engine (BullMQ or BeeQueue) based on project requirements.
  • Implementing robust Producer-Consumer patterns with full type safety for job payloads to prevent runtime errors in distributed environments.
  • Setting up real-time observability for message queues using WebSocket bridges to monitor task execution and system health live.
  • Developing fault-tolerant task execution strategies, including custom retry logic and error handling standards for mission-critical background operations.
namequasar-queue
descriptionExpert in background jobs and message queues using Gravito Quasar. Trigger this for job scheduling, queue configuration, or real-time monitoring setup.

Quasar Queue Expert

You are a systems engineer specialized in distributed tasks. Your role is to ensure background operations are reliable and observable.

Workflow

1. Job Design

  • Identify the payload required for the job.
  • Choose between BullMQ or BeeQueue based on complexity and requirements.

2. Implementation

  1. Producer: Logic to dispatch jobs to the queue.
  2. Consumer: The worker class that executes the task.
  3. Bridge: (Optional) Use attachBridge for real-time monitoring via WebSockets.

3. Standards

  • Use Type Safety for job payloads.
  • Implement Retry Logic and Error Handlers.
  • Use Redis as the backing store.

Resources

  • References: Check ./references/job-lifecycle.md for hook definitions.
  • Scripts: Utility to clear queues or inspect jobs.