Saleor Django Schema Migration
saleor/saleor
Generates and splits Django schema migrations for Saleor with manage.py makemigrations, enforcing one new model or one field change per migration file.
Set up a Django project into the op-django layout so the architecture, signals, and settings skills have a foundation to build on.
$ npx skills add dvf/opinionated-django --skill dj-scaffold -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dvf/opinionated-django dj-scaffold --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dvf/opinionated-django.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dj-scaffold .claude/skills/dj-scaffold && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dj-scaffold" agent skill from https://github.com/dvf/opinionated-django/tree/master/skills/dj-scaffold into .claude/skills/dj-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dj-scaffold", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dvf/opinionated-django/tree/master/skills/dj-scaffoldType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dvf/opinionated-django --skill dj-scaffold -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dvf/opinionated-django dj-scaffold --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dvf/opinionated-django.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/dj-scaffold .agents/skills/dj-scaffold && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dj-scaffold" agent skill from https://github.com/dvf/opinionated-django/tree/master/skills/dj-scaffold into .agents/skills/dj-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dj-scaffold", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dvf/opinionated-django --skill dj-scaffold -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dvf/opinionated-django dj-scaffold --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dvf/opinionated-django.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/dj-scaffold .cursor/skills/dj-scaffold && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dj-scaffold" agent skill from https://github.com/dvf/opinionated-django/tree/master/skills/dj-scaffold into .cursor/skills/dj-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dj-scaffold", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dvf/opinionated-django.git --path skills/dj-scaffold--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dvf/opinionated-django --skill dj-scaffold -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dvf/opinionated-django dj-scaffold --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dvf/opinionated-django.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/dj-scaffold .gemini/skills/dj-scaffold && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dj-scaffold" agent skill from https://github.com/dvf/opinionated-django/tree/master/skills/dj-scaffold into .gemini/skills/dj-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dj-scaffold", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dvf/opinionated-django dj-scaffoldInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dvf/opinionated-django --skill dj-scaffold -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dvf/opinionated-django.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/dj-scaffold .github/skills/dj-scaffold && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dj-scaffold" agent skill from https://github.com/dvf/opinionated-django/tree/master/skills/dj-scaffold into .github/skills/dj-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dj-scaffold", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dvf/opinionated-django --skill dj-scaffold -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dvf/opinionated-django dj-scaffold --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dvf/opinionated-django.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/dj-scaffold .opencode/skills/dj-scaffold && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dj-scaffold" agent skill from https://github.com/dvf/opinionated-django/tree/master/skills/dj-scaffold into .opencode/skills/dj-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dj-scaffold", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
dj-scaffoldSet up a Django project into the op-django layout so the architecture, signals, and settings skills have a foundation to build on.
Dj Scaffold is an agent skill from dvf/opinionated-django. Set up a Django project into the op-django layout so the architecture, signals, and settings skills have a foundation to build on. Use when starting a new project from scratch, or when converting an existing Django project to follow this opinionated structure. Creates the src/project/ shell (ids, services registry, api, reliable signals), installs dependencies with uv, and establishes the per-app directory conventions.
Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Backend development. It works with Django. The repository describes itself as: An opinionated Django project with Repository pattern, Pydantic DTOs, svcs DI, and Stripe-style ULID IDs. The licence is MIT.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit f17fc2d. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashGrepGlobFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
uvdjango-adminFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
pyrefly.orgFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Dj Scaffold loads about 3.3k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 664 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Write, Edit, Bash, Grep, GlobAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from dvf/opinionated-django at commit f17fc2d, republished under its MIT licence (© dvf). 664 words, ~3,339 tokens.
.claude/skills/dj-scaffold/SKILL.md (or your agent's skills folder).You are preparing a Django project to use the op-django patterns. After this skill runs, the dj-architecture and dj-signals skills can add features on top without any further setup.
Figure out which situation you're in:
uv init and django-admin startproject, then transform the result.manage.py, settings.py, and at least one app already exist. You will add the src/project/ shell alongside what's there and relocate files only if asked.Read pyproject.toml (if present) and locate manage.py and settings.py so you know the project's current layout. Confirm with the user before moving any existing files.
src/
manage.py
project/
__init__.py
settings.py
urls.py
wsgi.py
asgi.py
api/
__init__.py # NinjaAPI() instance, exception handlers, mounts all resource routers
<resource>/
__init__.py # re-exports router
routes.py # handler functions
schemas.py # ninja.Schema input types
types.py # AuthedRequest and other shared typing aliases
ids.py # prefixed ULID generators
services.py # svcs registry + get() helper
signals.py # ReliableSignal base + send_reliable machinery
<app>/
__init__.py
apps.py
admin.py
models/
__init__.py
<entity>.py
dtos/
__init__.py
<entity>.py
repositories/
__init__.py
<entity>.py
services/
__init__.py
<entity>.py
signals.py # optional, defines ReliableSignal instances
receivers.py # optional, @receiver handlers — must be idempotent
tests/
<app>/
test_repo.py
test_service.py
test_api.py
pyproject.tomlPer-app models/, dtos/, repositories/, services/ are packages, not single files — one module per entity.
Use uv for everything. Never pip or poetry.
uv add 'django>=6.0' 'django-ninja>=1.6' 'pydantic>=2.0' 'svcs>=25.1' \
'python-ulid>=3.0' 'celery>=5.4' python-decouple
uv add --dev ruff 'pyrefly>=0.42' django-stubs pytest pytest-djangoPyrefly auto-recognizes Django constructs as long as django-stubs is installed — no plugin, no mypy_django_plugin-style config. See pyrefly.org/en/docs/django for the current support matrix.
src/project/ids.pyfrom ulid import ULID
def prefixed_ulid(prefix: str) -> str:
return f"{prefix}_{str(ULID()).lower()}"
def _make_generator(prefix: str):
def generate() -> str:
return prefixed_ulid(prefix)
generate.__name__ = f"generate_{prefix}_id"
generate.__qualname__ = f"generate_{prefix}_id"
return generate
# Add one generator per aggregate root, with a unique 3-4 char prefix.
# Example:
# generate_prd_id = _make_generator("prd")src/project/services.pyimport svcs
registry = svcs.Registry()
def register_services(registry: svcs.Registry) -> None:
"""Register every real factory. Tests re-run this to restore overrides."""
# Register repositories and services here as the project grows.
# Example:
# from products.repositories.product import ProductRepository
# from products.services.product import ProductService
#
# registry.register_factory(ProductRepository, ProductRepository)
#
# def _product_service_factory(container: svcs.Container) -> ProductService:
# return ProductService(container.get(ProductRepository))
#
# registry.register_factory(ProductService, _product_service_factory)
register_services(registry)
def get[T](service_type: type[T]) -> T:
"""Get a service from the registry. Works anywhere — views, tasks, commands."""
return svcs.Container(registry).get(service_type)src/project/types.pyNarrows request.user to a guaranteed-authenticated Django User so handlers don't have to deal with AnonymousUser unions.
# If the project swaps AUTH_USER_MODEL for a custom user (see dj-models),
# import that model here instead — a stale stock-User import makes this
# type silently wrong everywhere it's used.
from django.contrib.auth.models import User
from django.http import HttpRequest
class AuthedRequest(HttpRequest):
"""
An HttpRequest whose `user` attribute is guaranteed to be an authenticated User.
Use as the first-argument annotation on any django-ninja handler that requires
auth. The narrowing is a contract, not runtime enforcement — pair this with
ninja's `auth=` on the router or a middleware that rejects anonymous requests.
"""
user: User # type: ignore[assignment]src/project/api/ packageThe API lives in a package, not a single file. src/project/api/__init__.py owns the NinjaAPI() instance and central exception handlers, and mounts one router per resource subpackage. Each resource subpackage (src/project/api/<resource>/) contains routes.py (handler functions), schemas.py (ninja Schema input types), and an __init__.py that re-exports the router.
src/project/api/__init__.py:
from ninja import NinjaAPI
# Import resource routers and mount them below.
# from project.api.products import router as products_router
# TODO: no auth wired — every route is public at this mount point.
# `AuthedRequest` is a typing contract only; it enforces nothing at runtime.
# Wire real auth before shipping, e.g. NinjaAPI(auth=django_auth) or a
# per-router `auth=` argument.
api = NinjaAPI()
# api.add_router("/products", products_router)
@api.exception_handler(ValueError)
def on_value_error(request, exc: ValueError):
return api.create_response(request, {"detail": str(exc)}, status=400)
@api.exception_handler(LookupError)
def on_lookup_error(request, exc: LookupError):
return api.create_response(request, {"detail": str(exc)}, status=404)
@api.exception_handler(PermissionError)
def on_permission_error(request, exc: PermissionError):
return api.create_response(request, {"detail": str(exc)}, status=403)Example resource subpackage — src/project/api/products/routes.py:
from typing import List
from ninja import Router
from products.dtos.product import ProductDTO
from products.services.product import ProductService
from project.services import get
from project.types import AuthedRequest
from .schemas import CreateProductIn
router = Router()
@router.get("/", response=List[ProductDTO])
def list_products(request: AuthedRequest):
return get(ProductService).list_products()src/project/api/products/schemas.py:
from decimal import Decimal
from ninja import Schema
class CreateProductIn(Schema):
name: str
price: Decimal
stock: intsrc/project/api/products/__init__.py:
from .routes import router
__all__ = ["router"]To add a new resource router: (a) create src/project/api/<resource>/ with routes.py, schemas.py, and __init__.py, then (b) import and mount the router in src/project/api/__init__.py via api.add_router("/<resource>", <resource>_router).
Wire api.urls into src/project/urls.py:
from django.contrib import admin
from django.urls import path
from project.api import api
urlpatterns = [
path("admin/", admin.site.urls),
path("api/", api.urls),
]src/project/signals.py — Reliable SignalsThis module provides the ReliableSignal base that apps import. Receivers run asynchronously via Celery, and send_reliable() enqueues them inside the current DB transaction so rollbacks are respected.
import json
from celery import shared_task
from django.db import transaction
from django.dispatch import Signal
from django.utils.module_loading import import_string
@shared_task
def _dispatch_reliable_receiver(receiver_path: str, kwargs_json: str) -> None:
receiver = import_string(receiver_path)
receiver(**json.loads(kwargs_json))
class ReliableSignal(Signal):
"""A Django Signal whose receivers run asynchronously via Celery.
- `send_reliable()` must be called inside a `transaction.atomic()` block.
- Receiver tasks are enqueued on transaction commit, so rollbacks are respected.
- Delivery is at-least-once. Every receiver MUST be idempotent.
- Arguments MUST be JSON-serializable (pass IDs, never model instances).
"""
def send_reliable(self, sender, **kwargs) -> None:
payload = json.dumps(kwargs)
# _live_receivers() is a private Django API; since Django 5.0 it returns
# a (sync_receivers, async_receivers) tuple. Re-check on Django upgrades.
sync_receivers, async_receivers = self._live_receivers(sender)
for receiver in (*sync_receivers, *async_receivers):
path = f"{receiver.__module__}.{receiver.__qualname__}"
transaction.on_commit(
lambda p=path: _dispatch_reliable_receiver.delay(p, payload)
)This is a minimal implementation — feel free to harden it (dead-letter queue, replay tooling, explicit retry policy) as the project matures.
Create src/project/celery.py:
import os
from celery import Celery
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "project.settings")
app = Celery("project")
app.config_from_object("django.conf:settings", namespace="CELERY")
app.autodiscover_tasks()In src/project/__init__.py:
from .celery import app as celery_app
__all__ = ("celery_app",)Hand off to the dj-settings skill to lay out settings.py with banner sections. At minimum it must include:
INSTALLED_APPS with each project app as "<app>.apps.<App>Config"CELERY_BROKER_URL and CELERY_RESULT_BACKEND (read via python-decouple)DEFAULT_AUTO_FIELD is irrelevant — all PKs are ULID CharFieldspyproject.toml[tool.ruff]
line-length = 100
target-version = "py312"
[tool.pyrefly]
project-includes = ["src"]
python-version = "3.12"
[tool.pytest.ini_options]
DJANGO_SETTINGS_MODULE = "project.settings"
python_files = ["test_*.py"]
pythonpath = ["src"]Pyrefly + Django caveats (from pyrefly.org/en/docs/django):
django-stubs and it just works — no plugin to enable, no extra [tool.pyrefly] keys required.user.order_set (the implicit reverse manager Django generates from a ForeignKey) will flag as an attribute error. Work around it in the repository layer by either (a) querying the child model directly — OrderRepository().list_for_user(user_id) — or (b) using an explicit related_name and a narrow cast / # type: ignore[attr-defined] at the call site. Do not paper over this in services or DTOs; push it down to the repo.ManyRelatedManager is generic over [Parent, Model] rather than the concrete child type (unlike mypy's django-plugin). For DTO coercion this doesn't matter — the coerce_related_manager validator handles it — but don't rely on pyrefly to catch mistyped M2M targets.QuerySet typing beyond .all() is still thin. Keep chained queryset expressions inside the repository where you can annotate the return type as list[SomeDTO] and let the caller rely on that.uv run python src/manage.py check
uv run ruff check src
uv run ruff format --check src
uv run pyrefly check src
uv run pytestAll five must pass. Fix any issue rather than silencing it.
uv addsrc/project/ids.py with _make_generator helpersrc/project/services.py with registry and get()src/project/types.py with AuthedRequestsrc/project/api/__init__.py with NinjaAPI instance (per-resource routers live in src/project/api/<resource>/ subpackages)ValueError → 400, LookupError → 404, PermissionError → 403)src/project/signals.py with ReliableSignal basesrc/project/celery.py + __init__.py exporturls.py mounts api.urlsdj-settings skillpyproject.toml has ruff / pyrefly / pytest configdjango check, ruff, pyrefly, pytest all passOnce this checklist is complete, the dj-architecture and dj-signals skills can build features on top without any extra setup.
© dvf, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/dj-scaffold of dvf/opinionated-django.
Open the folder on GitHubat commit f17fc2d
Dj Scaffold next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dj Scaffold this skilldvf/opinionated-django | 109 | — | ~3.3k | Automated safety check: Notes | MIT | |
| Saleor Django Schema Migrationsaleor/saleor | 23k | — | ~1k | Automated safety check: Pass | BSD-3-Clause | |
| Django Access Reviewgetsentry/skills | 1k | 3 repos | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| Silk Profilerbaserow/baserow | 6.1k | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| Arch Wikiahmedemad3/arch-wiki | 250 | — | ~5.1k | Automated safety check: Pass | None | |
| Run Testsnetboxlabs/netbox-branching | 155 | — | ~1.2k | Automated safety check: Pass | Custom licence |
saleor/saleor
Generates and splits Django schema migrations for Saleor with manage.py makemigrations, enforcing one new model or one field change per migration file.
getsentry/skills
Django access control and IDOR security review. An agent skill from getsentry/skills.
baserow/baserow
Investigate backend performance using Django Silk profiling data.
ahmedemad3/arch-wiki
Scans any project codebase for new/changed modules, endpoints, middleware, infrastructure, Docker topologies, SQL queries, or permissions and updates docs/architecture/architecture.json.
netboxlabs/netbox-branching
Run the netboxbranching plugin's Django test suite against a local NetBox checkout.
aropan/clist
Add or change a CLIST Django management command, including arguments, resource selection, EventLog monitoring, or cron and Healthchecks wiring.
dvf/opinionated-django
Implement a Django feature following the opinionated architecture — prefixed ULID IDs, repository pattern, Pydantic DTOs, svcs service locator, project-scoped django-ninja API, Celery reliable…
dvf/opinionated-django
Structure Django models with proper Meta classes, verbose names, and optimized indexes.
dvf/opinionated-django
Use Stripe-style prefixed ULID primary keys (e.g. An agent skill from dvf/opinionated-django.
dvf/opinionated-django
Set up and write pytest tests for an op-django project — pytest-django configuration, two-sided Celery testing (patched dispatch sites + plain-function task bodies, never eager mode), freezegun for…
dvf/opinionated-django
Structure Django business logic as plain services that receive their dependencies via constructor injection, and wire them through an svcs registry so they can be resolved anywhere — views, Celery…
dvf/opinionated-django
Add reliable signals (async side-effects via Celery) to a Django feature.
Works with
Categories
Set up a Django project into the op-django layout so the architecture, signals, and settings skills have a foundation to build on. Dj Scaffold is an agent skill from dvf/opinionated-django. Set up a Django project into the op-django layout so the architecture, signals, and settings skills have a foundation to build on.
Dj Scaffold fits situations like: starting a new project from scratch; converting an existing Django project to follow this opinionated structure.
Run `npx skills add dvf/opinionated-django --skill dj-scaffold -a claude-code`. Or copy the skill folder (skills/dj-scaffold in dvf/opinionated-django) into .claude/skills/dj-scaffold in your project. Claude Code loads it when a task matches its description.
Run `npx skills add dvf/opinionated-django --skill dj-scaffold -a codex`. Or copy the skill folder (skills/dj-scaffold in dvf/opinionated-django) into .agents/skills/dj-scaffold in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dvf/opinionated-django --skill dj-scaffold -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dj-scaffold, .gemini/skills/dj-scaffold, .github/skills/dj-scaffold and .opencode/skills/dj-scaffold in your project.
Going by SKILL.md and its folder, Dj Scaffold needs the command-line tools its instructions call (uv and django-admin). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Grep, Glob.
SKILL.md names 1 domain. As links in the text: pyrefly.org. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Dj Scaffold is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Dj Scaffold: Saleor Django Schema Migration (saleor/saleor, 23k stars), Django Access Review (getsentry/skills, 1k stars), Silk Profiler (baserow/baserow, 6.1k stars) and Arch Wiki (ahmedemad3/arch-wiki, 250 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
dvf (a GitHub user) maintains it in dvf/opinionated-django, which has 109 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on August 14, 2026.
Source: dvf/opinionated-django on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.