viewflow/seedkit / skills/django-seedkit
django-seedkit
FlaggedBootstrap a new Django project, or add components — auth (allauth, magic-link, axes, 2FA), payments (Stripe, dj-stripe), REST (django-modern-rest, django-bolt), Celery / Django Tasks, async views & WebSockets (ASGI, uvicorn worker, django-channels, channels-redis), Tailwind+DaisyUI, favicon, SEO meta tags + sitemap, HTML email templates, S3 storage, structlog, healthchecks, Docker, CI, deploy (VPS / Fly / GitHub-SSH), dbbackup, Sentry/Bugsink — to an existing Django codebase. Use whenever the user wants to scaffold Django, integrate a Django package, set up async / WebSockets, set up production deploys, wire CI/CD, or extend an existing Django project.
references/rest-modern-rest.md
View on GitHub# django-modern-rest
Docs: <https://django-modern-rest.readthedocs.io/>
Typed REST framework for Django. Sits inside the normal request/response cycle — no new runtime. Sync or async handlers; pluggable schema libs (pydantic, msgspec, attrs, dataclasses, TypedDict).
Requires `django>=5.0`, Python 3.11+.
## Install
`msgspec` is the recommended schema engine (fastest JSON path). Add it as the default:
```sh
uv add 'django-modern-rest[msgspec,openapi]>=0.11,<1.0' 'pyjwt[crypto]'
```
Pre-1.0 release — constrain it below 1.0. `pyjwt` comes along even without dmr's JWT auth: its throttling module imports `jwt` unconditionally. For DMR JWT auth itself, add the `jwt` extra (`'django-modern-rest[msgspec,openapi,jwt]>=0.11,<1.0'`).
If the user wants pydantic schemas instead, swap `msgspec` → `pydantic`. Both extras can co-exist.
Add `'dmr'` to `INSTALLED_APPS` only to serve the OpenAPI UI's static files (needs `django.contrib.staticfiles` with `AppDirectoriesFinder`). Plain endpoints and a YAML/JSON schema view need no app entry.
## Layout
REST endpoints live inside a registered Django app, not at project root. If the user has no app yet, create one: `uv run manage.py startapp api`.
```
api/
__init__.py
apps.py
controllers.py # Controller classes
schemas.py # request / response models
urls.py # router wiring
```
## Minimal endpoint
Use msgspec by default. The user can substitute pydantic by importing `dmr.plugins.pydantic.PydanticFastSerializer` and `pydantic.BaseModel`.
```python
# api/schemas.py
import uuid
import msgspec
class UserCreate(msgspec.Struct):
email: str
class User(msgspec.Struct):
uid: uuid.UUID
email: str
```
```python
# api/controllers.py
import uuid
from dmr import Body, Controller
from dmr.plugins.msgspec import MsgspecSerializer
from .schemas import User, UserCreate
class UserController(Controller[MsgspecSerializer]):
async def post(self, parsed_body: Body[UserCreate]) -> User:
return User(uid=uuid.uuid4(), email=parsed_body.email)
```
`Controller.post` / `.get` / `.patch` / `.delete` map to HTTP verbs. Both sync and async are supported — pick whichever matches the surrounding code.
## URL wiring — `api/urls.py`
```python
from dmr.routing import Router
from django.urls import path
from .controllers import UserController
router = Router(
'api/',
[
path('users/', UserController.as_view(), name='users'),
],
)
```
## `config/urls.py`
```python
from django.urls import include, path
from api.urls import router
urlpatterns = [
# ... existing routes
path(router.prefix, include((router.urls, 'api'), namespace='api')),
]
```
## OpenAPI
The `[openapi]` extra adds schema validation, a YAML view, and richer examples via polyfactory. Wire the schema view per the upstream docs (https://django-modern-rest.readthedocs.io/) — keep the URL behind `if settings.DEBUG` unless the user wants a public schema.
## Boot check
Adds nothing to the standard boot check. After `migrate` + `createsuperuser`:
```sh
curl -sf -X POST http://127.0.0.1:8000/api/users/ \
-H 'content-type: application/json' \
-d '{"email":"a@b.com"}'
```
## Pitfalls
- Don't put controllers in `config/` — Django app discovery only scans `INSTALLED_APPS`.
- `dmr` belongs in `INSTALLED_APPS` only for the OpenAPI UI's static files — see Install. Adding it for plain endpoints buys nothing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |