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

View on GitHub
# GitHub Actions — Tests

Docs: <https://docs.github.com/en/actions> · <https://github.com/astral-sh/setup-uv>

The workflow below runs `uv run pytest`. If pytest wasn't picked at foundation time, swap `uv run pytest` for `uv run manage.py test` (the workflow itself stays the same). Test runner setup — `pytest`, `pytest-django`, `pytest.ini` — lives in `references/pytest.md`.

## .github/workflows/test.yml

```yaml
name: test

on:
  push:
    branches: [main]   # bare `push:` + `pull_request:` double-runs every PR commit
  pull_request:
  workflow_call:       # lets deploy.yml run this workflow as its test gate

jobs:
  test:
    runs-on: ubuntu-latest

    services:
      # Drop this block when DB=SQLite — the sqlite `DATABASE_URL` below
      # needs no service container.
      postgres:
        image: postgres:17
        env:
          POSTGRES_PASSWORD: postgres
        ports:
          - 5432:5432
        options: >-
          --health-cmd pg_isready
          --health-interval 5s
          --health-timeout 5s
          --health-retries 5
      # Add this block only when Redis is wired (cache or Celery).
      redis:
        image: redis:8
        ports:
          - 6379:6379
        options: >-
          --health-cmd "redis-cli ping"
          --health-interval 5s
          --health-timeout 5s
          --health-retries 5

    env:
      # For SQLite, swap the URL — never drop the var. `base.py` requires
      # DATABASE_URL once `DJANGO_DEBUG=False`, so the workflow fails import
      # at the first `manage.py` / `pytest` step without it.
      DATABASE_URL: postgres://postgres:postgres@localhost:5432/postgres
      # DATABASE_URL: sqlite:////tmp/ci.sqlite3
      # 50+ chars, 5+ unique, no `django-insecure-` prefix — a short key or
      # that prefix trips security.W009 at the `check --deploy` step below.
      DJANGO_SECRET_KEY: ci-placeholder-secret-key-not-a-real-secret-0123456789-abcxyz
      DJANGO_DEBUG: "False"
      DJANGO_ALLOWED_HOSTS: "*"
      # `DEBUG=False` triggers the gated `env.NOTSET` branch on every
      # required env var. Provide safe placeholders so settings load:
      DJANGO_MAIL_HOST: localhost
      DEFAULT_FROM_EMAIL: test@example.com
      SERVER_EMAIL: test@example.com
      REDIS_URL: redis://localhost:6379       # only when Redis or Celery is wired
      POSTMARK_SERVER_TOKEN: ci-placeholder   # only when django-anymail[postmark] is wired
      ANYMAIL_WEBHOOK_SECRET: ci-placeholder  # only when the Anymail webhook URL is wired
      AWS_ACCESS_KEY_ID: ci-placeholder       # only when django-dbbackup is wired
      AWS_SECRET_ACCESS_KEY: ci-placeholder   # only when django-dbbackup is wired
      DBBACKUP_BUCKET: ci-placeholder         # only when django-dbbackup is wired

    steps:
      - uses: actions/checkout@v7

      - uses: astral-sh/setup-uv@v10
        with:
          enable-cache: true

      - run: uv sync --frozen

      # Only when security settings were applied (`references/security.md`).
      # Catches security-setting regressions (SSL_REDIRECT without proxy,
      # missing HSTS, etc.) at CI time instead of first-deploy. Without those
      # settings the check fails with security.W004/W008/W011/W016 — swap this
      # step for a plain `uv run manage.py check` then.
      - run: uv run manage.py check --deploy --fail-level WARNING
        env:
          DJANGO_SETTINGS_MODULE: config.settings.production

      # Fails when a model change landed without its migration.
      - run: uv run manage.py makemigrations --check --dry-run

      - run: uv run pytest        # or `uv run manage.py test` if pytest wasn't chosen
```

Don't add a `manage.py migrate` step before tests. `pytest-django` and Django's own test runner each build a `test_<dbname>` database from migrations on every run — a pre-step migrate touches the service DB, doesn't affect the test DB at all, and pollutes state for any later step that reuses the same connection.
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