llms.txt is an open proposal for a short Markdown file that lists a project's key docs and links, so AI tools can find them without crawling every page.

Where should llms.txt be deployed?

At /llms.txt on your documentation site, or in your repository root. Tools read it when they fetch it; nothing loads it automatically.

# Django 6 & Ninja / DRF Architecture Specialist

> Production guidelines for Django 6. Enforces async ORM methods, Django Ninja Pydantic schemas, strict migrations, N+1 query elimination, and the built-in tasks and CSP support.

## Quick Reference

- **Framework**: Django 6 / Django Ninja / DRF

- **Language**: Python 3.12+

- **Styling & UI**: None / API Service

- **Database / Persistence**: PostgreSQL / Django ORM

- **Architectural Philosophy**: strict

## Core Architectural Invariants

- **Clean Layered Architecture**: Decouple presentation, business logic, and data access layers via interfaces.

- **Guard Clauses & Early Returns**: Exit early from functions to eliminate deeply nested if-else pyramids.

- **Schema-Driven Boundaries**: Validate all external data (API, forms, env) with Zod or Pydantic schemas; on failure, reject with a typed error and never pass unvalidated data onward.

## Operational Guardrails & Prohibited Patterns

- **Inspect Before Acting**: Always read and understand existing code and imports before suggesting changes.

- **Minimal Surgical Diffs**: Touch only lines relevant to prompt. Preserve existing comments and formatting.

- **Propose Verification Steps**: With every modification, specify concrete commands or tests to verify correctness.

- **Concise & Direct Tone**: Skip conversational pleasantries. Deliver focused diffs and a short rationale.

## Mandatory Project Directives

- Never execute raw SQL without query parameterization.

- Ensure all model fields declare explicit verbose_name and db_index where filtered.

## Implementation Reference

### Preferred Patterns

```python

from ninja import Router, Schema

from django.shortcuts import aget_object_or_404

from .models import Article

router = Router()

class ArticleOut(Schema):

id: int

title: str

author_name: str

@router.get("/articles/{article_id}", response=ArticleOut)

async def get_article(request, article_id: int):

article = await Article.objects.select_related("author").aget(id=article_id)

return {"id": article.id, "title": article.title, "author_name": article.author.username}

```

### Discouraged Anti-Patterns

```python

@router.get("/articles/{article_id}")

async def get_article(request, article_id: int):

article = Article.objects.get(id=article_id) # Blocking sync query inside async handler!

return {"id": article.id, "title": article.title, "author": article.author.username}

```

## Verification Commands & Workflows

1. Use asynchronous ORM methods (aget, acreate, afirst) inside async view handlers.

2. Prevent N+1 queries: always apply select_related for foreign keys and prefetch_related for M2M relations.

3. Validate API payloads with Django Ninja Schema or DRF Serializers before domain logic execution.

4. Never modify existing committed migration files; create new sequential migrations via makemigrations.

5. Use GeneratedField for database-computed columns rather than overriding model save().

6. Run background work with django.tasks (@task, .enqueue()) and a real worker backend; the built-in backends are for development and tests.

7. Set the Content Security Policy with SECURE_CSP and ContentSecurityPolicyMiddleware instead of a third-party package.

## Context Documents & Specs

- [System Architecture](ARCHITECTURE.md): Authoritative system design, data flows, and state machine invariants.

- [AI Multi-Agent Spec](AGENTS.md): Universal specification for autonomous coding agent operations.

Backend · Any LLM tool that fetches it

Django 6 & Ninja / DRF llms.txt

An llms.txt for a Django 6 & Ninja / DRF project: a short Markdown map of what it is and where the key docs and code live.

Path: llms.txt
Loads: Fetched on request
Format: Markdown index (.txt)
Used by: Any LLM tool that fetches it

All llms.txt presets and how llms.txt works

What this file tells the agent

An llms.txt gives language models and agents a short Markdown map of your Django 6 & Ninja / DRF project: what it is and where the key docs and code live, so a tool that fetches it can go straight to the right files.

Use asynchronous ORM operations (aget(), acreate(), afirst()) inside async def view handlers.
Prevent N+1 query catastrophes: always apply select_related() for ForeignKey/OneToOne and prefetch_related() for ManyToMany/reverse relationships.
Enforce Django Ninja schemas or DRF serializers with explicit field typing; never return raw unvalidated model instances.
Never alter existing committed migration files; generate new sequential migrations via python manage.py makemigrations.
Use GeneratedField for computed database columns rather than redundant model save() recalculations.

Code to avoid, and what to write instead

The rule steers the agent away from the left and toward the right.

avoid

# Discouraged: Synchronous blocking query inside async context & N+1 queries
@router.get("/articles/{article_id}")
async def get_article(request, article_id: int):
    article = Article.objects.get(id=article_id)  # Synchronous blocking call!
    return {"id": article.id, "title": article.title, "author": article.author.username}  # N+1 DB hit!

write instead

from ninja import Router, Schema
from django.shortcuts import aget_object_or_404
from .models import Article

router = Router()

class ArticleOut(Schema):
    id: int
    title: str
    author_name: str

@router.get("/articles/{article_id}", response=ArticleOut)
async def get_article(request, article_id: int):
    # Asynchronous fetch with joined relationship preventing N+1
    article = await Article.objects.select_related("author").aget(id=article_id)
    return {
        "id": article.id,
        "title": article.title,
        "author_name": article.author.username,
    }

Install it in one command

01
Go to your project root
The file goes at llms.txt, relative to the root.
02
Download the file
Run the command on the right. It downloads this preset and writes the file.
03
Make sure it gets used
Nothing loads llms.txt automatically. Serve it at your site root, or point agents to it from CLAUDE.md or AGENTS.md.

$ curl -fsSL "https://www.devscratchpad.tech/api/raw/llms-txt/python-django" -o "llms.txt"

writes llms.txt

path

llms.txt

To write the file from your own code instead, use Read your code or Convert Legacy Rules in the editor above.

More for Django 6 & Ninja / DRF

Other formats

Other llms.txt presets

Questions

What is llms.txt?: llms.txt is an open proposal for a short Markdown file that lists a project's key docs and links, so AI tools can find them without crawling every page.
Where should llms.txt be deployed?: At /llms.txt on your documentation site, or in your repository root. Tools read it when they fetch it; nothing loads it automatically.

Target Standard & File Format

Identity & Activation Rules

Technology Stack Context

Engineering Philosophy

Architectural & Code Quality Conventions

Agent Behavioral Guardrails

Step-by-Step Workflow Procedures

Target File Location