mcpField
D
django

django

github.com/microsoftDevelopment2.5k47 installsUpdated 2d ago
Repository

About django

A development skill for Django projects, aimed at developers working across models, views, routing, forms, administration, and tests. It offers guidance on project structure, ORM use, request handling, and testing practices.

Key features

  1. 01Django app structure guidance
  2. 02Model and ORM query practices
  3. 03View and URL handling patterns
  4. 04Authentication and query optimization
  5. 05pytest-django testing guidance

Use cases

  1. 01Organize apps around domain concepts
  2. 02Build CRUD views and route requests
  3. 03Reduce N+1 database queries
  4. 04Test database-backed views

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/microsoft/debugpy --skill django

After installing, type/djangoin Claude Code to confirm it loaded.

Details

From the project README

Skill: Django

Best practices for Django web development including models, views, templates, and testing.

When to Use

Apply this skill when working with Django projects — models, views, URL routing, templates, forms, admin, and management commands.

Project Structure

  • Follow the standard Django app layout: models.py, views.py, urls.py, admin.py, tests.py, forms.py.
  • Keep each app focused on a single domain concept; avoid "god apps" with unrelated models.
  • Use settings/base.py, settings/dev.py, settings/prod.py for environment-specific configuration.

Models

  • Always define __str__ on models for admin and debugging readability.
  • Use Meta.ordering sparingly — it adds ORDER BY to every query. Prefer explicit .order_by() on querysets.
  • Use database indexes (db_index=True, Meta.indexes) for fields that appear in filter() / order_by().
  • Prefer CharField with choices (or TextChoices / IntegerChoices) over bare strings for constrained fields.
  • Use F() expressions and Q() objects for complex queries to avoid race conditions and improve readability.

Views

  • Prefer class-based views (CBVs) for CRUD; prefer function-based views for one-off logic.
  • Always explicitly set queryset or override get_queryset() — never rely on mutable class-level state.
  • Use select_related() and prefetch_related() to avoid N+1 query problems.
  • Set LOGIN_URL and use @login_required / LoginRequiredMixin consistently.

Testing

  • Use pytest-django with @pytest.mark.django_db for database access.
  • Prefer TestCase or TransactionTestCase only when explicit transaction control is needed; otherwise use pytest fixtures.
  • Use RequestFactory or Client to test views without starting a server.
  • Use baker.make() (model-bakery) or factories instead of manual model construction in tests.

Pitfalls

  • Never do blocking I/O in async views without wrapping in sync_to_async.
  • Avoid importing models at module level in settings.py or urls.py (circular imports).
  • Never store secrets in settings.py — use environment variables.
  • Avoid raw SQL unless the ORM genuinely cannot express the query.

Comments

Markdown supported