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/dev-tasks.md

View on GitHub
# Dev task runner

One short name per workflow step so the README can show `mise run dev` instead of `uv run manage.py runserver`, `just test` instead of `uv run pytest`, etc.

## Pick the runner

Ask the user. Default: **mise** (recommended). If unsure what's installed, detect with `command -v mise just make poe` and offer the first hit.

| Runner | File written | Install |
| --- | --- | --- |
| mise | `mise.toml` | `curl https://mise.run \| sh` |
| just | `justfile` | `brew install just` |
| make | `Makefile` | ships with most systems |
| poe | `[tool.poe.tasks]` in `pyproject.toml` | `uv add --dev poethepoet` |
| none | — | skip the whole reference |

Mise is the recommended pick because it also pins the Python toolchain (`[tools] python = "3.13"`), so the project gets one tool instead of `pyenv` + `just`.

## Task list

Generate one task per command the README would otherwise spell out. Include only the tasks for add-ons the project actually applied. The bodies below assume the host dev loop; for the container loop see "Container dev loop" further down.

| Task | Command |
| --- | --- |
| `install` | `uv sync` |
| `dev` | `uv run manage.py runserver` |
| `migrate` | `uv run manage.py migrate` |
| `makemigrations` | `uv run manage.py makemigrations` |
| `shell` | `uv run manage.py shell` |
| `superuser` | `uv run manage.py createsuperuser` |
| `test` | `uv run pytest` *(or `uv run manage.py test`)* |
| `lint` | `uv run ruff check .` *(ruff = yes)* |
| `fmt` | `uv run ruff format .` *(ruff = yes)* |
| `typecheck` | `uv run pyright` *(pyright = yes)* |
| `collectstatic` | `uv run manage.py collectstatic --noinput` |
| `worker` | `DJANGO_SETTINGS_MODULE=config.settings.local uv run celery -A config worker -l info` *(celery)* |
| `tailwind` | `uv run manage.py tailwind runserver` *(tailwind)* |
| `deploy-migrate` | one-shot `docker compose … run --rm web python manage.py migrate` *(deploy=vps / github-ssh)* |
| `deploy` | `deploy-migrate` then `docker compose --env-file deploy/.env.prod -f deploy/docker-compose.prod.yml up -d` *(deploy=vps / github-ssh)* or `fly deploy` *(deploy=managed/fly)* |

Deploy tasks: only generate when §6.6 deploy target was picked. `--env-file deploy/.env.prod` is required on every compose call — compose auto-loads only `./.env`, and the image line's `${GITHUB_REPOSITORY}` interpolates from that file (`references/deploy-github-ssh.md`).
- `vps` / `github-ssh`: `deploy` depends on `deploy-migrate` so the one-shot migrate always precedes `up -d` — that's the gap a bare `docker compose up -d --build` hits on first boot against an empty DB.
  - Exception: the SQLite + Litestream pattern (`references/database.md`) runs `migrate --noinput` inside `entrypoint.sh` on every boot, so skip `deploy-migrate` — `deploy` is a bare `up -d`.
- `managed` (Fly.io): single `deploy = fly deploy` task — Fly's release command runs migrations, no separate `deploy-migrate` needed.
- `managed` (Railway / Render): skip — those platforms deploy on `git push`, no task to alias.

## Container dev loop

When `manage.py` runs in a `web` container (`references/docker.md`), every task body changes: `uv run <cmd>` becomes `docker compose exec -T web <cmd>`, and `python` replaces `uv run` inside the container. Three tasks change shape rather than prefix — `install` builds the image, `dev` runs the stack in the foreground, and `worker` / `tailwind` disappear because those are sibling services the stack already starts.

```just
dc := "docker compose exec -T web"

install:
    docker compose build

dev:
    docker compose up

migrate:
    {{dc}} python manage.py migrate

test:
    {{dc}} pytest

shell:
    docker compose exec web python manage.py shell

superuser:
    docker compose exec web python manage.py createsuperuser
```

`-T` on every scripted task: without it `exec` demands a TTY and fails wherever there is none — CI, a hook, a `just` recipe run from an editor. `shell` and `createsuperuser` are the exceptions; both need the TTY they would otherwise be denied.

mise, make and poe take the same bodies. Neither mise nor make has `just`'s variable interpolation, so write the prefix out in each task, or set it once — `[env] DC = "docker compose exec -T web"` in `mise.toml`, `DC = docker compose exec -T web` in a `Makefile` — and use `$DC`.

## mise.toml

```toml
[tools]
python = "3.13"

[tasks.install]
run = "uv sync"

[tasks.dev]
run = "uv run manage.py runserver"

[tasks.migrate]
run = "uv run manage.py migrate"

[tasks.test]
run = "uv run pytest"

[tasks.deploy-migrate]
run = "docker compose --env-file deploy/.env.prod -f deploy/docker-compose.prod.yml run --rm web python manage.py migrate"

[tasks.deploy]
depends = ["deploy-migrate"]
run = "docker compose --env-file deploy/.env.prod -f deploy/docker-compose.prod.yml up -d"
```

Run with `mise run dev`. First-time setup: `mise trust && mise install`.

## justfile

```just
install:
    uv sync

dev:
    uv run manage.py runserver

migrate:
    uv run manage.py migrate

test:
    uv run pytest

deploy-migrate:
    docker compose --env-file deploy/.env.prod -f deploy/docker-compose.prod.yml run --rm web python manage.py migrate

deploy: deploy-migrate
    docker compose --env-file deploy/.env.prod -f deploy/docker-compose.prod.yml up -d
```

Run with `just dev`. `just --list` enumerates tasks.

## Makefile

Indent with **tabs**, not spaces. Every target is `.PHONY` because none produce a file matching the target name.

```make
.PHONY: install dev migrate test deploy-migrate deploy

install:
	uv sync

dev:
	uv run manage.py runserver

migrate:
	uv run manage.py migrate

test:
	uv run pytest

deploy-migrate:
	docker compose --env-file deploy/.env.prod -f deploy/docker-compose.prod.yml run --rm web python manage.py migrate

deploy: deploy-migrate
	docker compose --env-file deploy/.env.prod -f deploy/docker-compose.prod.yml up -d
```

## poethepoet

```sh
uv add --dev poethepoet
```

```toml
[tool.poe.tasks]
install = "uv sync"
dev     = "python manage.py runserver"
migrate = "python manage.py migrate"
test    = "pytest"
deploy-migrate = { shell = "docker compose --env-file deploy/.env.prod -f deploy/docker-compose.prod.yml run --rm web python manage.py migrate" }
deploy = { sequence = ["deploy-migrate", { shell = "docker compose --env-file deploy/.env.prod -f deploy/docker-compose.prod.yml up -d" }] }
```

Poe strips `uv run` because it executes inside the venv. Run with `uv run poe dev`.

## README

Replace the `uv run …` block in the README with the chosen runner's commands. Keep one fallback line at the bottom for users who don't want to install the runner — point them at `uv run manage.py <cmd>`.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated 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