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

View on GitHub
# Analytics

Docs: <https://www.goatcounter.com/help/start> · <https://umami.is/docs> · <https://shynet.r1ke.io/> · <https://developers.google.com/analytics/devguides/collection/ga4>

Privacy-respecting site analytics. Pick one backend at setup time — only that snippet ships in templates. Empty `ANALYTICS_ID` disables tracking (e.g. in dev).

| Backend | Hosting | Cookies | Consent banner |
|---|---|---|---|
| GoatCounter (recommended) | self-host or SaaS | no | no |
| Umami | self-host or SaaS | no | no |
| Shynet | self-host | no | no |
| Google Analytics 4 | SaaS (US) | yes | **yes (EU)** |

GDPR / consent specifics — `references/gdpr.md`.

## Django wiring (shared)

Apply once for any chosen backend, then drop in the matching backend snippet below.

### .env

```sh
ANALYTICS_ID=
ANALYTICS_HOST=     # only for self-hosted GoatCounter / Umami / Shynet
```

### Settings

In `config/settings.py` (or `config/settings/base.py`):

```python
ANALYTICS_ID   = env("ANALYTICS_ID", default="")
ANALYTICS_HOST = env("ANALYTICS_HOST", default="")   # omit for GA4
```

### Context processor

`config/context_processors.py`:

```python
from django.conf import settings

def analytics(request):
    return {
        "ANALYTICS_ID":   settings.ANALYTICS_ID,
        "ANALYTICS_HOST": settings.ANALYTICS_HOST,
        "DEBUG":          settings.DEBUG,
    }
```

Register in `TEMPLATES[0]["OPTIONS"]["context_processors"]`:

```python
"config.context_processors.analytics",
```

### Template

`templates/_analytics.html` wraps the chosen backend's snippet. The `not DEBUG` gate keeps beacons out of dev. Uppercase `DEBUG` comes from the custom processor above — not Django's built-in `django.template.context_processors.debug`, which only exposes a lowercase `debug` when the request IP is in `INTERNAL_IPS`.

```django
{% if ANALYTICS_ID and not DEBUG %}
  {# GA4 only needs ANALYTICS_ID; self-hosted backends also gate on ANALYTICS_HOST: #}
  {# {% if ANALYTICS_ID and ANALYTICS_HOST and not DEBUG %} #}
  {# backend snippet — see below #}
{% endif %}
```

In `templates/base.html`, before `</body>`:

```django
{% include "_analytics.html" %}
```

If no frontend reference created `templates/base.html` (e.g. `frontend: none`), ship a minimal one so the include resolves — without it the analytics snippet is dead:

```django
<!DOCTYPE html>
<html lang="en">
<head><meta charset="utf-8"><title>{% block title %}{% endblock %}</title></head>
<body>
  {% block content %}{% endblock %}
  {% include "_analytics.html" %}
</body>
</html>
```

Register `BASE_DIR / "templates"` in `TEMPLATES[0]["DIRS"]`.

## Backends

### GoatCounter

Tiny single Go binary, SQLite, cookieless. Lowest ops cost.

**SaaS:** free at goatcounter.com — `ANALYTICS_HOST=https://<code>.goatcounter.com`, `ANALYTICS_ID=<code>`.

**Self-host (docker-compose.prod.yml):**

```yaml
services:
  goatcounter:
    image: arp242/goatcounter:latest
    restart: unless-stopped
    environment:
      GOATCOUNTER_LISTEN: ":8080"
      # Point the DB at the mounted volume explicitly. The image's default
      # path is relative to its workdir, so a volume mounted anywhere else
      # leaves the SQLite file inside the container — gone on recreate.
      GOATCOUNTER_DB: "sqlite+/home/goatcounter/goatcounter-data/goatcounter.sqlite3"
    volumes:
      - goatcounter_data:/home/goatcounter/goatcounter-data

volumes:
  goatcounter_data:
```

Reverse-proxy `stats.example.com` → `goatcounter:8080`.

**Snippet** in `templates/_analytics.html`:

```html
<script data-goatcounter="{{ ANALYTICS_HOST }}/count"
        async src="//gc.zgo.at/count.js"></script>
```

### Umami

Polished UI, cookieless. Node + Postgres.

**SaaS:** umami.is.

**Self-host (docker-compose.prod.yml):**

```yaml
services:
  umami:
    image: ghcr.io/umami-software/umami:postgresql-latest
    restart: unless-stopped
    environment:
      DATABASE_URL: postgres://umami:${UMAMI_DB_PASSWORD}@umami-db:5432/umami
      DATABASE_TYPE: postgresql
      APP_SECRET: ${UMAMI_APP_SECRET}
    depends_on: [umami-db]

  umami-db:
    image: postgres:16-alpine
    environment:
      POSTGRES_DB: umami
      POSTGRES_USER: umami
      POSTGRES_PASSWORD: ${UMAMI_DB_PASSWORD}
    volumes:
      - umami_pgdata:/var/lib/postgresql/data

volumes:
  umami_pgdata:
```

Reverse-proxy `stats.example.com` → `umami:3000`. Create a website in the Umami UI to get the website ID.

**Snippet** in `templates/_analytics.html`:

```html
<script defer src="{{ ANALYTICS_HOST }}/script.js"
        data-website-id="{{ ANALYTICS_ID }}"></script>
```

### Shynet

Django + Postgres. Same stack as the project; cookieless via short-lived heartbeats.

**Self-host (docker-compose.prod.yml):**

```yaml
services:
  shynet:
    image: milesmcc/shynet:latest
    restart: unless-stopped
    environment:
      DATABASE_URL: postgres://shynet:${SHYNET_DB_PASSWORD}@shynet-db:5432/shynet
      DJANGO_SECRET_KEY: ${SHYNET_SECRET_KEY}
      ALLOWED_HOSTS: stats.example.com
    depends_on: [shynet-db]

  shynet-db:
    image: postgres:16-alpine
    environment:
      POSTGRES_DB: shynet
      POSTGRES_USER: shynet
      POSTGRES_PASSWORD: ${SHYNET_DB_PASSWORD}
    volumes:
      - shynet_pgdata:/var/lib/postgresql/data

volumes:
  shynet_pgdata:
```

Reverse-proxy `stats.example.com` → `shynet:8080`. Create a Service in the Shynet admin; it generates the snippet — paste into `_analytics.html`. The service ID is `ANALYTICS_ID`.

### Google Analytics 4

SaaS, US-hosted. Cookies required. **EU users need a consent banner before loading gtag** — see `references/gdpr.md`.

`ANALYTICS_ID=G-XXXXXXX` from analytics.google.com. `ANALYTICS_HOST` unused.

**Snippet** in `templates/_analytics.html`:

```html
<script async src="https://www.googletagmanager.com/gtag/js?id={{ ANALYTICS_ID }}"></script>
<script nonce="{{ csp_nonce }}">
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', '{{ ANALYTICS_ID }}');
</script>
```

The `nonce="{{ csp_nonce }}"` is required when `references/csp.md` is active — `script-src` has no `'unsafe-inline'`, so the inline init block is blocked without a nonce. Pair it with `CSP.NONCE` in `script-src` (`references/csp.md`); the template attribute alone leaves the header without a matching source expression. The attribute is harmless when CSP is off (browsers ignore unknown nonces).
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