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/email.md

View on GitHub
# Email (Django 6.1)

Docs: <https://docs.djangoproject.com/en/6.1/howto/mailers-migration/> · <https://docs.djangoproject.com/en/6.1/topics/email/>

Django 6.1 deprecates `EMAIL_BACKEND` and transport `EMAIL_*` settings; they are removed in Django 7.0. Use `MAILERS`. `DEFAULT_FROM_EMAIL`, `SERVER_EMAIL`, `ADMINS`, `MANAGERS`, and `EMAIL_SUBJECT_PREFIX` are unchanged.

Do not use `env.email_url()`: it creates deprecated Django settings.

## SMTP

```python
DEFAULT_FROM_EMAIL = env(
    "DEFAULT_FROM_EMAIL", default="webmaster@localhost" if DEBUG else env.NOTSET
)
SERVER_EMAIL = env("SERVER_EMAIL", default=DEFAULT_FROM_EMAIL)
ADMINS = [(address.split("@", 1)[0], address) for address in env.list("DJANGO_ADMINS", default=[])]

MAILERS = {
    "default": {
        "BACKEND": (
            "django.core.mail.backends.console.EmailBackend"
            if DEBUG else "django.core.mail.backends.smtp.EmailBackend"
        ),
        "OPTIONS": {} if DEBUG else {
            "host": env("DJANGO_MAIL_HOST", default=env.NOTSET),
            "port": env.int("DJANGO_MAIL_PORT", default=587),
            "use_tls": env.bool("DJANGO_MAIL_USE_TLS", default=True),
            "username": env("DJANGO_MAIL_USERNAME", default=""),
            "password": env("DJANGO_MAIL_PASSWORD", default=""),
            "timeout": env.int("DJANGO_MAIL_TIMEOUT", default=10),
        },
    },
}
```

Local uses the console mailer. Production needs `DJANGO_MAIL_HOST`; set the remaining `DJANGO_MAIL_*` variables as needed. Add them to `.env.example`.

Direct migration:

```python
# Before
EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend"
EMAIL_HOST = "smtp.example.com"
EMAIL_PORT = 587
EMAIL_USE_TLS = True
EMAIL_HOST_USER = "user@example.com"
EMAIL_HOST_PASSWORD = "password"

# After
MAILERS = {
    "default": {
        "BACKEND": "django.core.mail.backends.smtp.EmailBackend",
        "OPTIONS": {
            "host": "smtp.example.com",
            "use_tls": True,  # port 587 is implicit
            "username": "user@example.com",
            "password": "password",
        },
    },
}
```

Map remaining settings as follows: `EMAIL_FILE_PATH` → `file_path`, `EMAIL_USE_SSL` → `use_ssl`, `EMAIL_SSL_CERTFILE` → `ssl_certfile`, `EMAIL_SSL_KEYFILE` → `ssl_keyfile`, and `EMAIL_TIMEOUT` → `timeout`, all inside `OPTIONS`. `use_tls` and `use_ssl` are mutually exclusive.

## Named mailers and APIs

```python
MAILERS["marketing"] = {
    "BACKEND": "django.core.mail.backends.smtp.EmailBackend",
    "OPTIONS": {"host": env("MARKETING_MAIL_HOST"), "use_tls": True},
}

send_mail("Welcome!", "Thanks for signing up.", "hello@example.com", ["user@example.com"], using="marketing")
```

Calls without `using=` use `"default"`. Replace `mail.get_connection()` with `mail.mailers.default`, and replace `connection=`, `auth_user`, and `auth_password` with a named `MAILERS` entry plus `using=`. Do not combine `using` with those arguments or `fail_silently`.

Check dependencies before defining `MAILERS`: packages that read `settings.EMAIL_*` or call `get_connection()` with a backend path are incompatible until updated.

## Anymail

```python
INSTALLED_APPS += ["anymail"]
if not DEBUG:
    MAILERS["default"] = {"BACKEND": "anymail.backends.postmark.EmailBackend"}
ANYMAIL = {"POSTMARK_SERVER_TOKEN": env("POSTMARK_SERVER_TOKEN", default="" if DEBUG else env.NOTSET)}
```

Keep provider credentials in `ANYMAIL`; use `OPTIONS` only for backend-constructor options. Add `path("anymail/", include("anymail.urls"))` and `ANYMAIL["WEBHOOK_SECRET"]` only when webhooks are required.

## Mailpit

In `config/settings/local.py`, replace the inherited console mailer:

```python
MAILERS["default"] = {
    "BACKEND": "django.core.mail.backends.smtp.EmailBackend",
    "OPTIONS": {"host": "localhost", "port": 1025},
}
```

Run a test message with `PYTHONWARNINGS=default uv run manage.py send_test_email you@example.com` to catch remaining deprecated email APIs.
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: 198kUpdated 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