dmr-openapi-skeleton

Generate Django-modern-rest skeletons from OpenAPI 3.1+ specifications.

1.3k|150|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/wemake-services/django-modern-rest --skill dmr-openapi-skeleton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dmr-openapi-skeleton
Source: https://github.com/wemake-services/django-modern-rest/tree/main/.agents/skills/dmr-openapi-skeleton
Command: npx skills add https://github.com/wemake-services/django-modern-rest --skill dmr-openapi-skeleton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenAPI 3.1+ specifications can be converted into ready-to-run Django-modern-rest skeletons, significantly reducing boilerplate for DTOs, controllers, routers, and docs wiring.

Core Features & Use Cases

  • Generates DTOs, controllers, routers, and docs wiring from OpenAPI 3.1+ specs.
  • Bootstraps new Django projects or apps with a runnable skeleton, ready for smoke tests.
  • Use Case: quickly scaffold a project from an OpenAPI contract to validate API surface and integration points.

Quick Start

Provide an OpenAPI 3.1+ specification to generate a Django-modern-rest skeleton.

Frequently Asked Questions about dmr-openapi-skeleton

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

FAQPage Schema
How do I generate a Django skeleton from an OpenAPI 3.1 spec?

To generate a Django skeleton from an OpenAPI 3.1 spec, provide the specification to the Skill. It outputs a runnable Django-modern-rest project structure with DTOs, controllers, routers, and OpenAPI docs wiring.

Can I bootstrap a Django project from an OpenAPI contract with minimal business logic?

Yes, bootstrapping a Django project from an OpenAPI contract generates a runnable skeleton with minimal business logic. It scaffolds views, urls, serializers, and routers ready for smoke tests to validate API integration points.

Does OpenAPI 3.1 scaffolding include serializers and DTOs for Django?

OpenAPI 3.1 scaffolding includes serializers and DTOs for Django. The generated skeleton preserves the public contract while wiring views, urls, controllers, routers, and OpenAPI docs into a runnable project structure.

What is the best way to scaffold Django views and urls from OpenAPI 3.1+?

Scaffolding Django views and urls from OpenAPI 3.1+ is best handled by generating a Django-modern-rest skeleton. This preserves the public API contract and produces a runnable structure with minimal tests for immediate validation.

Are there limitations when generating Django-modern-rest skeletons from OpenAPI 3.1+?

Generating Django-modern-rest skeletons from OpenAPI 3.1+ provides minimal business logic and minimal tests. It is designed for scaffolding DTOs, controllers, and routers to validate API surface, not for generating production-ready application features.

Why do I need to bootstrap DTOs and routers from an OpenAPI specification?

Bootstrapping DTOs and routers from an OpenAPI specification significantly reduces boilerplate for docs wiring. It allows you to quickly scaffold a Django project from an API contract to validate integration points before implementing business logic.