What problem does it solve? Writing asyncio-based consumers and publishers in funboost raises event loop conflicts, blocked loops from synchronous RPC calls, and confusion about which concurrency mode to choose. This Skill provides the correct patterns for async def consumers, aio_push/aio_publish publishing, and non-blocking RPC result retrieval. ## Core Features & Use Cases - Async Consumer Configuration: Set up async def consumption functions with ConcurrentModeEnum.ASYNC, or run coroutines under the default THREADING mode without loop management. - Async Publishing and RPC: Use aio_push/aio_publish for non-blocking task submission and AioAsyncResult to await results without freezing the event loop. - Event Loop Troubleshooting: Resolve errors like "attached to a different loop" and "This event loop is already running" using specify_async_loop and correct startup ordering. - Use Case: In a FastAPI service, publish an order-processing task with await handle_order.aio_push(order_id) and return the result via await AioAsyncResult(task_id).result without blocking other requests. ## Quick Start Ask the AI to write a funboost async consumer using ConcurrentModeEnum.ASYNC with aio_push publishing and AioAsyncResult for retrieving the RPC result in a FastAPI endpoint.