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

View on GitHub
# Health check endpoint

Reverse proxies, container platforms, and uptime monitors expect `/healthz` (or similar) to return 200 cheaply. Stock Django doesn't ship one — every prod-ready deploy needs to expose this themselves.

We don't pull in `django-health-check`. Two trivial views beat a dependency that adds 8 backends and a settings block.

Put the views in `config/views.py`. If a suitable app already exists (a `core` app, an existing landing-page app), put them there instead — don't add a new app just for these views.

## `config/views.py`

```python
from django.db import connection
from django.db.utils import OperationalError
from django.http import HttpResponse


def liveness(_request):
    """Process is alive. No external checks — must never block."""
    return HttpResponse('ok', content_type='text/plain')


def readiness(_request):
    """Process can serve traffic — DB reachable."""
    try:
        with connection.cursor() as cur:
            cur.execute('SELECT 1')
    except OperationalError:
        return HttpResponse('db down', status=503, content_type='text/plain')
    return HttpResponse('ready', content_type='text/plain')
```

## `config/urls.py`

```python
from django.urls import path
from config.views import liveness, readiness

urlpatterns = [
    # ...
    path('healthz', liveness, name='healthz'),
    path('readyz', readiness, name='readyz'),
]
```

No trailing slash — kubelets / Caddy / Fly probes call exactly `/healthz`.

## Deploy wiring

- **Caddy / nginx** (`references/deploy-vps.md`): `health_uri /healthz` block on the upstream.
- **Fly.io** (`references/deploy-managed.md`): a `[[services.http_checks]]` block in `fly.toml` with `path = "/readyz"`.
- **GitHub Actions deploy** (`references/deploy-github-ssh.md`): post-deploy curl `/readyz` before declaring success.

If any deploy reference is applied, **also** add the matching probe wiring there. Don't leave the endpoint dangling.

## Allowed hosts gotcha

Probes hit the container by IP, not hostname. Either:

- Add the platform's probe IP / `*` to `ALLOWED_HOSTS` (Fly does this automatically; check before adding).
- Or run probes against the public hostname (slower path, more failure modes).

Don't strip the `Host`-header check globally to make probes work. Scope the bypass to the probe view if needed.
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