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

View on GitHub
# Test runner — pytest

Docs: <https://docs.pytest.org/> · <https://pytest-django.readthedocs.io/> · <https://coverage.readthedocs.io/>

Stock Django ships `manage.py test` (unittest-based). `pytest-django` swaps in pytest: shorter test files, fixtures, parametrization, better failure output. Adds two dev deps; doesn't change production code.

If you skip this, write tests with `django.test.TestCase` and run `uv run manage.py test`.

## Install

```sh
uv add --dev pytest pytest-django
```

## Config

`pytest.ini` (or `[tool.pytest.ini_options]` in `pyproject.toml`):

```ini
[pytest]
DJANGO_SETTINGS_MODULE = config.settings.test
python_files = tests.py test_*.py *_tests.py
```

For a single-settings layout, point at `config.settings`. The split layout already ships `config/settings/test.py` — see `references/new-project.md`.

## Seed a smoke test

`pytest` exits 5 ("no tests collected") when a project ships only empty `startapp` stub `tests.py` files — that turns CI (`references/ci.md`) red on the first push. Ship at least one real test per app you touched:

```python
# users/tests.py
import pytest


@pytest.mark.django_db
def test_smoke(client):
    assert client.get("/health/").status_code in (200, 302, 404)
```

## Run

```sh
uv run pytest
uv run pytest -k user        # only tests with "user" in the name
uv run pytest path/to/tests.py::test_signup
```

`pytest-django` builds a fresh `test_<dbname>` from migrations on first run, then reuses it. Add `--create-db` to force a rebuild after a schema change.

## Coverage

`pytest-cov` plugs `coverage.py` into the pytest run.

```sh
uv add --dev pytest-cov
```

`pyproject.toml`:

```toml
[tool.coverage.run]
source = ["."]
omit = [
    ".venv/**",
    "**/migrations/**",
    "**/tests/**",
    "**/test_*.py",
    "config/wsgi.py",
    "config/asgi.py",
    "manage.py",
]

[tool.coverage.report]
show_missing = true
skip_covered = true
```

Add `fail_under = <threshold>` to `[tool.coverage.report]` once the app has real code — on a fresh scaffold, the seeded smoke tests land at an arbitrary percentage and any gate just turns first-push CI red.

Run:

```sh
uv run pytest --cov                # terminal report
uv run pytest --cov --cov-report=html   # writes htmlcov/
```

In CI, emit Cobertura XML for upload to a coverage service (Codecov / Coveralls):

```yaml
      - run: uv run pytest --cov --cov-report=xml
      - uses: codecov/codecov-action@v7    # optional
```

Add `htmlcov/` and `.coverage` to `.gitignore`.

## CI

`references/ci.md`'s GitHub Actions workflow runs `uv run pytest` after `uv sync --frozen`. The dev deps installed above are what makes that step actually succeed.
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