Async message handling with Symfony Messenger; configure transports (RabbitMQ, Redis, Doctrine); implement handlers, middleware, and retry strategies
Scanned 8/31/2026
Install to Claude Code
npx -y skills add dev-toolings/superpowers-symfony --skill symfony-messenger --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Symfony Messenger?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dev-toolings-symfony-messenger)More formats (shields.io, HTML) on the badges page.
---
name: symfony:symfony-messenger
allowed-tools:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
description: Async message handling with Symfony Messenger; configure transports (RabbitMQ, Redis, Doctrine); implement handlers, middleware, and retry strategies
---
# 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.
3. Configure retries, failure transport, and observability.
4. 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.md`
- `docs/complexity-tiers.md`
No comments yet. Be the first to comment!
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.