Symfony:symfony Messenger Skill
- 476 installs
- 190 repo stars
- Updated August 6, 2026
- makfly/superpowers-symfony
symfony:symfony-messenger is a Claude Code skill that offloads emails, webhooks, imports, and domain events from Symfony controllers to async Messenger transports with retries and failure handling for developers building
About
symfony:symfony-messenger is a backend skill from makfly/superpowers-symfony that guides Symfony Messenger component setup for asynchronous job processing in PHP applications. The skill covers message classes, handler registration, transport configuration for Redis, RabbitMQ, or Doctrine, retry strategies, failure transport routing, and decoupling controller logic from long-running emails, webhooks, CSV imports, and domain event dispatch. Developers reach for symfony:symfony-messenger when Symfony controllers become slow or timeout on side effects and need reliable background processing with dead-letter handling. Output includes messenger.yaml transport config, message and handler PHP classes, retry and failure middleware setup, and console worker commands for production queue consumers.
- Message and handler class design
- Transport and routing configuration
- Retry and failure transport strategies
- Middleware for logging and validation
- Sync vs async dispatch patterns
Symfony:Symfony Messenger by the numbers
- 476 all-time installs (skills.sh)
- Ranked #875 of 4,492 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 11, 2026 (Skillselion catalog sync)
npx skills add https://github.com/makfly/superpowers-symfony --skill symfonysymfony-messengerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 476 |
|---|---|
| repo stars | ★ 190 |
| Last updated | August 6, 2026 |
| Repository | makfly/superpowers-symfony ↗ |
How do you async offload work with Symfony Messenger?
Offload emails, webhooks, imports, and domain events from Symfony controllers to async Messenger transports with retries and failure handling.
Who is it for?
PHP backend engineers decoupling Symfony controller side effects into Redis, RabbitMQ, or Doctrine async queues.
Skip if: Laravel Horizon queue setup or Node.js BullMQ workers outside the Symfony PHP ecosystem.
When should I use this skill?
User asks about Symfony Messenger, async message handlers, failure transport, or offloading emails and webhooks from controllers.
What you get
Messenger transport config, message handlers, retry rules, and failure transport setup
- messenger.yaml config
- message handler PHP classes
Files
Symfony Messenger (Symfony)
Use when
- Implementing asynchronous workflows with Messenger/Scheduler/Cache.
- Stabilizing retries and failure transports.
Default workflow
1. Define async contract and delivery semantics. 2. Implement idempotent handlers and routing strategy. 2. Configure retries, failure transport, and observability. 2. Validate success/failure replay scenarios.
Guardrails
- Assume at-least-once delivery, not exactly-once.
- Keep handlers deterministic and side-effect aware.
- Surface poison-message handling strategy.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- Async config/handlers updated.
- Retry/failure policy decisions.
- Operational validation evidence.
References
reference.mddocs/complexity-tiers.md
Symfony Messenger Reference (Symfony)
Use this reference for implementation details and review criteria specific to symfony-messenger.
Skill Operating Checklist
Design checklist
- Confirm operation boundaries and invariants first.
- Minimize scope while preserving contract correctness.
- Test both happy path and negative path behavior.
Validation commands
- php bin/console messenger:consume --limit=1
- php bin/console messenger:failed:show
- ./vendor/bin/phpunit --filter=Messenger
Failure modes to test
- Invalid payload or forbidden actor.
- Boundary values / not-found cases.
- Retry or partial-failure behavior for async flows.
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.541k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.399k16.3kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.398k16.3kLark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.247k16.3k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k45
SupabaseGet accurate, up-to-date Supabase implementation guidance across database, auth, realtime, storage, edge functions and vector search without relying on outd204k2.5kHow it compares
Pick symfony:symfony-messenger for Symfony PHP async messaging; use Laravel queue skills when the framework is Laravel instead of Symfony.
FAQ
What does symfony:symfony-messenger configure?
symfony:symfony-messenger configures Symfony Messenger transports, message handlers, retries, and failure routing to offload emails, webhooks, imports, and domain events from HTTP controllers into background workers.
Which queue backends does symfony:symfony-messenger support?
symfony:symfony-messenger supports Redis, RabbitMQ, and Doctrine transports configured in messenger.yaml. The skill also sets up failure transports and retry middleware for dead-letter handling in production PHP APIs.