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/existing-project.md

View on GitHub
# Extending an existing Django project

Use this workflow when the working directory already contains a Django project and the user wants to add or update components — not bootstrap from scratch. Skip §2–§4 of `SKILL.md`; this file replaces them.

## 1. Inventory pass

Before asking any §5/§6 question, build a map of what's already wired. Read each source and note what you find — don't ask the user about anything you can read directly.

**Stack basics**

- `pyproject.toml` — Python version pin, declared deps and `--dev` deps. Notable signals: `ruff`, `pytest`, `pytest-django`, `pyright`, `django-stubs`, `pre-commit`, `django-extensions`, `structlog`, `django-allauth`, `django-axes`, `dj-stripe`, `stripe`, `django-modern-rest`, `django-bolt`, `celery`, `django-redis`, `whitenoise`, `django-storages`, `django-cors-headers`, `sentry-sdk`, `django-dbbackup`. Django CSP is built in: detect `ContentSecurityPolicyMiddleware`, `SECURE_CSP`, or `SECURE_CSP_REPORT_ONLY` in settings instead of a package.
- `manage.py` — confirms Django, surfaces the settings module path.
- Settings — locate the active module (single `settings.py`, split `base/local/production`, or custom). Read `INSTALLED_APPS`, `MIDDLEWARE`, `AUTH_USER_MODEL`, `DATABASES`, `CACHES`, `STORAGES`, email backend, `LANGUAGES`, security flags, `ContentSecurityPolicyMiddleware`, `SECURE_CSP`, and `SECURE_CSP_REPORT_ONLY`.
- `.env.example` and `.env` — which env vars are wired.
- `Dockerfile`, `docker-compose.yml`, `deploy/docker-compose.prod.yml`, `.devcontainer/` — which deploy artefacts already exist.
- `.pre-commit-config.yaml` — existing hook set.
- `.github/workflows/` — CI presence and shape.
- Deploy artefacts — `fly.toml`, `Caddyfile`, deploy scripts, GitHub-SSH workflow, `dbbackup` settings.

**Map findings to the eight groups**

For each group in the Reference files section of `SKILL.md`, mark each component as:

- **detected** — already installed and wired. Confirm with the user, then skip the question.
- **partial** — package present in deps but not fully wired (e.g. `django-axes` in `pyproject.toml` but missing from `INSTALLED_APPS`/`MIDDLEWARE`, or `LANGUAGES` set but no `LocaleMiddleware`). Surface the gap and ask if the user wants the wiring completed.
- **missing** — not present. Ask the §5/§6 question normally.

## 2. Derive foundation answers — don't replay §2

Don't ask Foundation questions. Read them off the repo:

- **Database engine** → `DATABASES['default']['ENGINE']`.
- **Local Postgres** → `db` service in `docker-compose.yml` → Postgres-in-Docker; otherwise host Postgres (or SQLite per the engine above).
- **Settings layout** → single `settings.py` vs `settings/` package with `base.py` / `local.py` / `production.py`. When it's split, settings added by any add-on follow the delta rule in `references/new-project.md`.
- **Custom user** → `AUTH_USER_MODEL` set to anything other than `auth.User`.
- **Request handling** → `channels` in `INSTALLED_APPS` (or an `asgi.py` wrapping `ProtocolTypeRouter`) → `asgi+channels`; a `uvicorn` / `UvicornWorker` command in the Dockerfile or deploy artefacts → `asgi`; otherwise `wsgi`. SKILL.md §5.7 and `references/async.md` both branch on this value, so record it even when no question follows.

If a downstream reference needs a foundation answer, use the detected value. Don't surprise the user with a layout change (e.g. don't split a single `settings.py` into a package unless they asked).

## 3. Report back to the user

Send one message structured as a bulleted list per group:

```
**Developer Experience**
- detected: ruff, pytest, pre-commit
- partial: django-extensions in deps but not in INSTALLED_APPS
- missing: typecheck, devcontainer, debug, db-safety, structlog

**Auth & Accounts**
- detected: django-allauth + axes
- missing: 2FA
…
```

Then ask which gaps they want to fill. Treat `none` as a valid answer for any group.

## 4. Boot check — replace §4

Skip the new-project boot check (no `createsuperuser`, the user already has accounts). Instead, after applying any reference that touches migrations, settings, or Docker, ask the user to confirm the existing project still boots cleanly:

- `uv run manage.py migrate` — runs new migrations, including any added by the new component.
- `uv run manage.py runserver` (or compose `up`) — confirm the dev server still starts and `/admin/` still loads.
- If pytest is wired: `uv run pytest` to catch regressions.

Wait for confirmation before moving to the next add-on.

## 5. README updates

Same rule as new projects: append decisions to `README.md` as you apply each reference, finalise at the end. For existing projects, don't rewrite the existing README — append a section like `## Added by seedkit (<date>)` with the new components and any new commands.
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