Background Jobs taste — ChatGPT prompt: what it does, how to install
Background Jobs taste — a prompt for ChatGPT and Claude.ai guides background worker design and queue reliability. Sets clear constraints for idempotency, retry budgets, and payload versioning.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Background Jobs taste does
The prompt directs the model to review and structure background jobs from a reliability engineer's perspective. It requires idempotent handlers, ID-only payloads loaded inside the worker, and explicit timeouts on all job executions and external network calls.
Patterns include enqueuing via outbox tables in the same database transaction, isolating fast tasks from heavy backfills, and handling SIGTERM gracefully. For complex multi-step pipelines, it advises choosing dedicated orchestrators like Temporal instead of chaining hidden task triggers.
What it helps with
- enforce idempotent execution across retries and duplicate events
- isolate latency-sensitive queues from bulk backfill workloads
- handle
SIGTERMclean shutdowns without dropping active work - enqueue tasks within database transactions via an outbox table
Example prompts for the agent
- Design a subscription billing worker that guarantees payments are never charged twice
- Review our background job architecture for email delivery and heavy backfills
How to install Background Jobs taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Background Jobs taste
How to install Background Jobs taste in Claude Code?
Place the file into your repository at .claude/commands/prompts.csv.md or paste its text directly into your chat session.
What does Background Jobs taste do?
It enforces backend reliability patterns for background workers, covering idempotency, queue isolation, retry caps, and correlation logging.
Which queue engines does the prompt favor?
It advises using tested queue systems like Sidekiq, BullMQ, Celery, or Postgres-based Graphile Worker instead of custom in-house implementations.
Source text
prompts.csv · CC0-1.0
# Background Jobs taste of a backend reliability engineer - Make every job idempotent so a retry or duplicate delivery never charges a card or sends an email twice. Confidence: 0.95 - Pass IDs in the job payload and load fresh data inside the worker instead of serializing whole records. Confidence: 0.90 - Enqueue jobs in the same database transaction as the write that triggers them, using an outbox table or a Postgres-backed queue. Confidence: 0.85 - Prefer a boring, well-supported queue such as Sidekiq, BullMQ, Celery or a Postgres queue like Graphile Worker over a home-grown one. Confidence: 0.80 - Retry with exponential backoff and jitter, and cap attempts so poison jobs end up in a dead letter queue. Confidence: 0.95 - Classify errors as retryable or permanent and fail permanent ones immediately instead of burning retries. Confidence: 0.85 - Set an explicit timeout on every job and on every network call it makes. Confidence: 0.90 - Keep jobs small and short, and split long batch work into chunks that can resume from a checkpoint. Confidence: 0.85 - Use separate queues for latency-sensitive and bulk work so a backfill never delays password reset emails. Confidence: 0.90 - Rate limit jobs that call third-party APIs per provider, not per worker process. Confidence: 0.80 - Use unique job keys or locks to prevent the same scheduled job from running twice at once. Confidence: 0.85 - Run cron-style schedules from one scheduler with leader election, never from every app instance. Confidence: 0.80 - Version job payloads and keep workers able to read the previous version during deploys. Confidence: 0.80 - Handle SIGTERM gracefully: stop taking new jobs, finish or requeue the current one, then exit. Confidence: 0.90 - Log a job ID, attempt number and correlation ID on every log line from a job. Confidence: 0.85 - Alert on queue depth, oldest job age and dead letter growth, not just on worker crashes. Confidence: 0.90 - Give the dead letter queue an owner and a documented replay command. Confidence: 0.75 - Test jobs by calling the handler directly in unit tests and run one end-to-end test through the real queue in CI. Confidence: 0.80 - Avoid chaining many jobs into hidden workflows; reach for a workflow engine like Temporal when steps need orchestration. Confidence: 0.70 - Store job results and side-effect markers in the database, not only in the queue backend. Confidence: 0.75
© f · CC0-1.0 · f/prompts.chat