Skip to content

viewflow/seedkit / skills/django-seedkit

django-seedkit

Flagged

Bootstrap a new Django project, or add components — auth (allauth, magic-link, axes, 2FA), payments (Stripe, dj-stripe), REST (django-modern-rest, django-bolt), Celery / Django Tasks, async views & WebSockets (ASGI, uvicorn worker, django-channels, channels-redis), Tailwind+DaisyUI, favicon, SEO meta tags + sitemap, HTML email templates, S3 storage, structlog, healthchecks, Docker, CI, deploy (VPS / Fly / GitHub-SSH), dbbackup, Sentry/Bugsink — to an existing Django codebase. Use whenever the user wants to scaffold Django, integrate a Django package, set up async / WebSockets, set up production deploys, wire CI/CD, or extend an existing Django project.

FileKindSize
SKILL.mdskill md17.7 KB
references/analytics.mdmarkdown6.3 KB
references/async.mdmarkdown4.4 KB
references/auth-hardening.mdmarkdown4.3 KB
references/auth.mdmarkdown7.9 KB
references/billing.mdmarkdown10.6 KB
references/ci.mdmarkdown3.9 KB
references/conventions.mdmarkdown2.5 KB
references/cors.mdmarkdown2.3 KB
references/csp.mdmarkdown3.6 KB
references/custom-user.mdmarkdown5.6 KB
references/database.mdmarkdown7.4 KB
references/dbbackup.mdmarkdown5.0 KB
references/deploy-github-ssh.mdmarkdown6.4 KB
references/deploy-managed.mdmarkdown2.9 KB
references/deploy-vps.mdmarkdown7.0 KB
references/dev-tasks.mdmarkdown6.5 KB
references/dev-tools.mdmarkdown14.5 KB
references/devcontainer.mdmarkdown2.1 KB
references/docker.mdmarkdown15.0 KB
references/email.mdmarkdown3.9 KB
references/error-reporting.mdmarkdown3.7 KB
references/existing-project.mdmarkdown4.7 KB
references/favicon.mdmarkdown2.7 KB
references/gdpr.mdmarkdown3.9 KB
references/healthcheck.mdmarkdown2.3 KB
references/i18n.mdmarkdown4.1 KB
references/lint.mdmarkdown2.2 KB
references/logging.mdmarkdown3.9 KB
references/new-project.mdmarkdown7.2 KB
references/pre-commit.mdmarkdown3.0 KB
references/pytest.mdmarkdown2.6 KB
references/realtime.mdmarkdown8.6 KB
references/redis.mdmarkdown2.6 KB
references/rest-bolt.mdmarkdown7.4 KB
references/rest-modern-rest.mdmarkdown3.4 KB
references/rest.mdmarkdown2.7 KB
references/robots.mdmarkdown1.8 KB
references/security.mdmarkdown2.0 KB
references/seo.mdmarkdown3.1 KB
references/storage-s3.mdmarkdown7.7 KB
references/storage-whitenoise.mdmarkdown2.8 KB
references/tailwind.mdmarkdown11.6 KB
references/tasks-celery.mdmarkdown5.3 KB
references/tasks-django-cron.mdmarkdown1012 B
references/tasks-django.mdmarkdown1.2 KB
references/typecheck.mdmarkdown4.3 KB
references/uv.mdmarkdown670 B

references/async.md

View on GitHub
# Request handling — WSGI / ASGI / ASGI + channels

Docs: <https://docs.djangoproject.com/en/6.1/topics/async/> · <https://www.uvicorn.org/> · <https://docs.gunicorn.org/en/stable/settings.html#worker-class>

Three modes the skill supports. Decide at Foundation §2.4 — switching later means rewriting Dockerfile `CMD`, gunicorn worker class, and the `manage.py`/`wsgi.py`/`asgi.py` defaults.

| Mode | Why pick it | What it ships |
|---|---|---|
| **wsgi** *(default)* | Stock Django, no async views, no WebSockets. | `gunicorn config.wsgi`. `manage.py` → `local`, `wsgi.py` → `production`, `asgi.py` left at the `startproject` default. |
| **asgi** | `async def` views, async middleware, `StreamingHttpResponse` over a long-running upstream. No WebSockets. | `gunicorn -k uvicorn_worker.UvicornWorker config.asgi:application`. `asgi.py` → `production`; `wsgi.py` left at the `startproject` default. |
| **asgi+channels** | Real WebSockets / long-lived connections / chat / live notifications. See `references/realtime.md`. | Same gunicorn invocation as `asgi`; channels routing wraps the ASGI app. |

## When to prefer stock ASGI over channels

`django-channels` activity has slowed. For one-shot async work — calling an HTTP API from a view, streaming a generated response, async ORM queries — stock Django 5+ async views are enough and add no dependency. Reach for channels only when you actually need WebSockets, long-lived connections, or out-of-band server pushes via a channel layer.

## Install

```sh
# asgi or asgi+channels
uv add 'uvicorn[standard]' uvicorn-worker gunicorn
```

`uvicorn[standard]` pulls `httptools` + `uvloop` for the fast loop; `uvicorn-worker` provides the `uvicorn_worker.UvicornWorker` class for gunicorn; `gunicorn` stays the process manager so `--workers` / signal handling / preload behave the same as the WSGI path.

## Settings module defaults

| File | wsgi | asgi / asgi+channels |
|---|---|---|
| `manage.py` | `config.settings.local` | `config.settings.local` |
| `wsgi.py` | `config.settings.production` | unchanged (the `startproject` default) — file isn't loaded |
| `asgi.py` | unchanged | `config.settings.production` |

Only one of `wsgi.py` / `asgi.py` gets the production pointer — whichever the deploy actually loads.

## Dockerfile `CMD`

```dockerfile
# wsgi
CMD ["gunicorn", "config.wsgi", "--bind", "0.0.0.0:8000", "--max-requests", "1000", "--max-requests-jitter", "100", "--access-logfile", "-"]

# asgi or asgi+channels
CMD ["gunicorn", "-k", "uvicorn_worker.UvicornWorker", "config.asgi:application", "--bind", "0.0.0.0:8000", "--max-requests", "1000", "--max-requests-jitter", "100", "--access-logfile", "-"]
```

Replace the `gunicorn config.wsgi …` line in `references/docker.md` and `references/deploy-vps.md` with the ASGI variant when the mode is `asgi` or `asgi+channels`.

## Worker count

gunicorn reads `WEB_CONCURRENCY` natively as the worker count (default 1). The `2 * cpu + 1` formula assumes sync workers. For ASGI/uvicorn workers, **start with the CPU count**; each worker already handles many concurrent requests inside its event loop, so multiplying inflates memory without throughput.

```sh
# .env.prod
WEB_CONCURRENCY=4   # cores for uvicorn workers; 2×cores+1 for sync WSGI workers
```

## Healthcheck

The `/healthz` / `/readyz` views in `references/healthcheck.md` work unchanged — gunicorn+uvicorn serves them with the same routing. The Caddyfile / compose healthcheck blocks don't change either.

## Tests

`pytest-django` runs sync tests against ASGI apps the same way it runs them against WSGI. For testing `async def` views, mark with `@pytest.mark.asyncio` and use `async def test_...` — `pytest-asyncio` is the standard plugin.

```sh
uv add --dev pytest-asyncio
```

`pytest.ini` / `pyproject.toml`:

```toml
[tool.pytest.ini_options]
asyncio_mode = "auto"
```

## Pitfalls

- Mixing sync ORM calls in an `async def` view: Django raises `SynchronousOnlyOperation`. Wrap with `sync_to_async(...)` or use the async ORM (`await Model.objects.aget(...)`, `async for obj in Model.objects.filter(...)`).
- `manage.py runserver` uses the WSGI handler regardless of `asgi.py` settings. For local ASGI behaviour parity (WebSocket upgrades, long-lived requests), run `uvicorn config.asgi:application --reload` directly.
- `gunicorn --preload` plus `UvicornWorker` shares the event loop across forks in surprising ways. Don't use `--preload` with the uvicorn worker class unless you've measured the win.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall