Menu
Use when creating or updating Celery tasks, async job logic, or Beat schedules in the backend.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
| name | backend-async-tasks |
| description | Use when creating or updating Celery tasks, async job logic, or Beat schedules in the backend. |
backend/src/backend/apps/**/tasks.py.backend/src/backend/celery_app.py.tasks.py file under the relevant app module.@app.task imported from backend.celery_app.int, None, etc.). Keep task-specific parameters
local unless they must be environment-configured.asyncio.run() to bridge async work.get_task_session() from backend.celery_app.app.conf.beat_schedule in
backend/src/backend/celery_app.py and use celery.schedules.crontab.alchemy_config engine inside a task; it is not fork-safe
for Celery workers.get_task_session() to manage DB connections safely across worker
processes.backend/src/backend/apps/**/tasks.pybackend/src/backend/celery_app.pybackend/tests/apps/users/test_tasks.pyBased on SOC occupation classification
Expert knowledge for Advanced Alchemy / SQLAlchemy ORM patterns. Use when working with models, services, repositories, or database migrations.
Expert knowledge for Litestar Python web framework. Use when working with Litestar routes, plugins, middleware, dependency injection, or configuration.
Use when running installs, dev servers, tests, lint/format, codegen, or Docker lifecycle tasks; Taskfile is the source of truth.
Use when changing GraphQL schema, resolvers, or frontend GraphQL documents so the contract and codegen stay in sync.
Use for change discipline, validation expectations, and safety checks when making repo changes.
