django-components
Installation
SKILL.md
Django components
Django is stable and well documented, so this skill does not copy its API reference. It holds what the docs do not tell you: which versions to target, where to fetch exact signatures, and the opinions that keep a Django codebase healthy. Look up the API in the versioned docs, then apply the pitfalls below.
Core principles
| Principle | Meaning |
|---|---|
| Read the installed version first | Django changes names and defaults between releases. Answer for the version the project runs, not the latest one. |
| Fetch, do not recall | Field options, setting names, and method signatures come from the versioned docs. Memory goes stale quickly. |
| Let the database do the work | Filter, aggregate, and update in SQL (F, Q, annotate, update), not in Python loops. |
| Prefer explicit over signals | A direct function call is easier to trace, test, and order than a receiver in another app. |
| Keep transactions short and visible | Wrap the unit of work in atomic, and push side effects behind on_commit. |
Version matrix
Verified 2026-10-21 against https://docs.djangoproject.com/en/6.1/releases/6.1 and https://www.djangoproject.com/download/. Re-check before quoting dates, they move.