Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Patterns for background task processing with Celery, ARQ, and Redis. Covers task queues, canvas workflows, scheduling, retry strategies, rate limiting, and production monitoring. Each category has individual rule files in references/ loaded on-demand.
Production Celery app configuration with secure defaults and worker tuning.
Key Patterns
JSON serialization with task_serializer="json" for safety
Late acknowledgment with task_acks_late=True to prevent task loss on crash
Time limits with both task_time_limit (hard) and task_soft_time_limit (soft)
Fair distribution with worker_prefetch_multiplier=1
Reject on lost with task_reject_on_worker_lost=True
Key Decisions
Decision
Recommendation
Serializer
JSON (never pickle)
Ack mode
Late ack (task_acks_late=True)
Prefetch
1 for fair, 4-8 for throughput
Time limit
soft < hard (e.g., 540/600)
Timezone
UTC always
Task Routing
Priority queue configuration with multi-queue workers and dynamic routing.
Key Patterns
Named queues for critical/high/default/low/bulk separation
Redis priority with queue_order_strategy: "priority" and 0-9 levels
Task router classes for dynamic routing based on task attributes
Per-queue workers with tuned concurrency and prefetch settings
Content-based routing for dynamic workflow dispatch
Key Decisions
Decision
Recommendation
Queue count
3-5 (critical/high/default/low/bulk)
Priority levels
0-9 with Redis x-max-priority
Worker assignment
Dedicated workers per queue
Prefetch
1 for critical, 4-8 for bulk
Routing
Router class for 5+ routing rules
Canvas Workflows
Celery canvas primitives for sequential, parallel, and fan-in/fan-out workflows.
Key Patterns
Chain for sequential ETL pipelines with result passing
Group for parallel execution of independent tasks
Chord for fan-out/fan-in with aggregation callback
Immutable signatures (si()) for steps that ignore input
Nested workflows combining groups inside chains
Link error callbacks for workflow-level error handling
Key Decisions
Decision
Recommendation
Sequential
Chain with s()
Parallel
Group for independent tasks
Fan-in
Chord (all must succeed for callback)
Ignore input
Use si() immutable signature
Error in chain
Reject stops chain, retry continues
Partial failures
Return error dict in chord tasks
Retry Strategies
Retry patterns with exponential backoff, idempotency, and dead letter queues.
Key Patterns
Exponential backoff with retry_backoff=True and retry_backoff_max
Jitter with retry_jitter=True to prevent thundering herd
Idempotency keys in Redis to prevent duplicate processing
Dead letter queues for failed tasks requiring manual review
Task locking to prevent concurrent execution of singleton tasks
Base task classes with shared retry configuration
Key Decisions
Decision
Recommendation
Retry delay
Exponential backoff with jitter
Max retries
3-5 for transient, 0 for permanent
Idempotency
Redis key with TTL
Failed tasks
DLQ for manual review
Singleton
Redis lock with TTL
Scheduling
Celery Beat periodic task configuration with crontab, database-backed schedules, and overlap prevention.
Key Patterns
Crontab for time-based schedules (daily, weekly, monthly)
Interval for fixed-frequency tasks (every N seconds)
Database scheduler with django-celery-beat for dynamic schedules
Schedule locks to prevent overlapping long-running scheduled tasks
Adaptive polling with self-rescheduling tasks
Key Decisions
Decision
Recommendation
Schedule type
Crontab for time-based, interval for frequency
Dynamic
Database scheduler (django-celery-beat)
Overlap
Redis lock with timeout
Beat process
Separate process (not embedded)
Timezone
UTC always
Monitoring
Production monitoring with Flower, custom signals, health checks, and Prometheus metrics.
Key Patterns
Flower dashboard for real-time task monitoring
Celery signals (task_prerun, task_postrun, task_failure) for metrics
Health check endpoint verifying broker connection and active workers
Queue depth monitoring for autoscaling decisions
Beat monitoring for scheduled task dispatch tracking
Key Decisions
Decision
Recommendation
Dashboard
Flower with persistent storage
Metrics
Prometheus via celery signals
Health
Broker + worker + queue depth
Alerting
Signal on task_failure
Autoscale
Queue depth > threshold
Result Backends
Task result storage, custom states, and progress tracking patterns.
Key Patterns
Redis backend for task status and small results
Custom task states (VALIDATING, PROCESSING, UPLOADING) for progress
update_state() for real-time progress reporting
S3/database for large result storage (never Redis)
AsyncResult for querying task state and progress
Key Decisions
Decision
Recommendation
Status storage
Redis result backend
Large results
S3 or database (never Redis)
Progress
Custom states with update_state()
Result query
AsyncResult with state checks
ARQ Patterns
Lightweight async Redis Queue for FastAPI and simple background tasks.
Key Patterns
Native async/await with arq for FastAPI integration
Worker lifecycle with startup/shutdown hooks for resource management
Job enqueue from FastAPI routes with enqueue_job()
Job status tracking with Job.status() and Job.result()
Delayed tasks with _delay=timedelta() for deferred execution
Key Decisions
Decision
Recommendation
Simple async
ARQ (native async)
Complex workflows
Celery (chains, chords)
In-process quick
FastAPI BackgroundTasks
LLM workflows
LangGraph (not Celery)
Tool Selection
Tool
Best For
Complexity
ARQ
FastAPI, simple async jobs
Low
Celery
Complex workflows, enterprise
High
RQ
Simple Redis queues
Low
Dramatiq
Reliable messaging
Medium
FastAPI BackgroundTasks
In-process quick tasks
Minimal
Anti-Patterns (FORBIDDEN)
# NEVER run long tasks synchronously in request handlers@router.post("/api/v1/reports")asyncdefcreate_report(data: ReportRequest):
pdf = await generate_pdf(data) # Blocks for minutes!# NEVER block on results inside tasks (causes deadlock)@celery_app.taskdefbad_task():
result = other_task.delay()
return result.get() # Blocks worker!# NEVER store large results in Redis@shared_taskdefprocess_file(file_id: str) -> bytes:
return large_file_bytes # Store in S3/DB instead!# NEVER skip idempotency for retried tasks@celery_app.task(max_retries=3)defcreate_order(order):
Order.create(order) # Creates duplicates on retry!# NEVER use BackgroundTasks for distributed work
background_tasks.add_task(long_running_job) # Lost if server restarts# NEVER ignore task acknowledgment settings
celery_app.conf.task_acks_late = False# Default loses tasks on crash# ALWAYS use immutable signatures in chords
chord([task.s(x) for x in items], callback.si()) # si() prevents arg pollution
Temporal Workflows
Durable execution engine for reliable distributed applications with Temporal.io.
Key Patterns
Workflow definitions with @workflow.defn and deterministic code
Saga pattern with compensation for multi-step transactions
Signals and queries for external interaction with running workflows
Timers with workflow.wait_condition() for human-in-the-loop
Parallel activities via asyncio.gather inside workflows
Key Decisions
Decision
Recommendation
Workflow ID
Business-meaningful, idempotent
Determinism
Use workflow.random(), workflow.now()
I/O
Always via activities, never directly
Temporal Activities
Activity and worker patterns for Temporal.io I/O operations.
Key Patterns
Activity definitions with @activity.defn for all I/O
Heartbeating for long-running activities (> 60s)
Error classification with ApplicationError(non_retryable=True) for business errors
