django-conventions

Enforces Django 4.x/5.x project conventions for structure, settings, URL routing, and serializers.

9|1|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/AratKruglik/antigravity-sdlc --skill django-conventions-aratkruglik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: django-conventions
Source: https://github.com/AratKruglik/antigravity-sdlc/tree/main/plugins/django-plugin/skills/django-conventions
Command: npx skills add https://github.com/AratKruglik/antigravity-sdlc --skill django-conventions-aratkruglik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Django project conventions are inconsistently applied across teams, leading to tangled apps, brittle settings, and confusing URL routing. This skill standardizes app layout, settings split (base/local/production), URLconf with namespacing, DRF ViewSets/serializers and permissions, signals, and Django admin registration to reduce onboarding time and errors.

Core Features & Use Cases

  • Standard project layout with apps and a central config
  • Clear settings separation for base/local/production environments
  • Consistent URLconf structure with app namespaces
  • DRF ViewSets and serializers with proper permissions
  • Signals and admin registrations to enable decoupled workflows

Quick Start

Configure a Django project to follow these conventions by creating apps, a settings split, and DRF components.

Frequently Asked Questions about django-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Django project structure across multiple apps?

Standardizing Django project structure requires enforcing conventions for app layout, settings splits, and URLconf namespacing to ensure consistent app configs and central routing across teams.

What is the best way to split Django settings for base, local, and production environments?

Splitting Django settings involves separating configurations into base, local, and production modules. This prevents brittle environment setups and reduces deployment errors by isolating environment-specific variables.

How do I organize URLconf with app namespaces in a scalable Django project?

Organizing URLconf with namespaces requires defining app_name in each app's urls module and including them centrally. This prevents routing conflicts and clarifies reverse URL lookups in large projects.

Does this convention guide work with Django REST Framework ViewSets and serializers?

The conventions fully support Django REST Framework by standardizing ViewSets, serializers, and permissions. This ensures consistent API endpoint definitions and access control across all project apps.

Can I use Django signals and admin customization within these app conventions?

These conventions explicitly integrate Django signals and admin registrations. This enables decoupled workflows where apps react to model changes without direct modifications, keeping admin interfaces consistent.

What Django versions are supported for scalable app conventions?

The conventions apply to Django 4.x and 5.x projects. This ensures compatibility with modern framework features while standardizing settings, URL routing, and DRF component layouts.