django-seedkit

## How this skill works Two paths: - **New project** (empty dir, only `.git/` or stub README): run §2 → §8 in order. - **Existing project** (has `pyproject.toml` and Django code): skip §2–§4. Read `references/existing-project.md` for the inventory workflow, then jump to §5/§6 and ask only about missing components. Before either path, run `uv --version` to confirm uv is installed (`references/uv.md`). Every question below names the reference that answers it — read that one file before applying the step, and no others. For every question that involves a third-party package: 1–2 sentences from the reference's intro on what it adds beyond stock Django, then ask. `none` (or `no`) is always a valid answer. **Use answers already given.** Before asking any question, scan the user's initial request (and anything they've said since) for the answer. If it's there — explicit ("use PostgreSQL", "with Celery", "no auth") or unambiguous from context — take it as given, note the decision in one line, and move on. Don't re-ask to confirm. Only ask when the answer is genuinely missing or ambiguous. **Preflight — read these before the first tool call of a new-project run:** `references/new-project.md`, `references/database.md`, and `references/conventions.md` (the cross-file contract: env var names, Redis DB map, prod compose service shape, SameSite rule, Python pins). ## Instructions ### 1. Open the conversation Name the groups you'll walk through — Project Foundation (§2), then Deve...