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/seo.md
View on GitHub# SEO — meta tags + sitemap
Docs: <https://docs.djangoproject.com/en/6.1/ref/contrib/sitemaps/> · <https://ogp.me/>
Stock Django pages ship no `<meta name="description">`, no Open Graph tags, and no sitemap. Search results fall back to guessed snippets, and links pasted into chat apps or social feeds show a bare URL instead of a preview card. One template block plus `django.contrib.sitemaps` covers both.
## Meta tags
Add inside the `<head>` of `templates/base.html` (scaffolded in `references/tailwind.md`), after `<title>`:
```django
{% block meta %}
<meta name="description" content="{{ meta_description|default:'<one-line project purpose>' }}">
<link rel="canonical" href="{{ request.scheme }}://{{ request.get_host }}{{ request.path }}">
<meta property="og:type" content="website">
<meta property="og:site_name" content="<project name>">
<meta property="og:title" content="{{ meta_title|default:'<project name>' }}">
<meta property="og:description" content="{{ meta_description|default:'<one-line project purpose>' }}">
<meta property="og:url" content="{{ request.scheme }}://{{ request.get_host }}{{ request.path }}">
<meta name="twitter:card" content="summary">
{% endblock %}
```
Replace `<project name>` / `<one-line project purpose>` at scaffold time with the answers from the Foundation questionnaire. Views pass `meta_title` / `meta_description` in context to customize per page; a page with special needs (an `og:image`, an `article` type) overrides `{% block meta %}` wholesale.
The canonical/`og:url` value is rebuilt from `scheme`/`host`/`path` rather than `request.build_absolute_uri` — the latter includes the query string, and `?page=2` variants would each declare themselves canonical.
## Sitemap
`django.contrib.sitemaps` generates `sitemap.xml` from querysets and named URLs. No `django.contrib.sites` needed — the view falls back to the request's host.
### Settings
```python
INSTALLED_APPS += ["django.contrib.sitemaps"]
# Absolute URL advertised to crawlers; robots.md's view appends a
# `Sitemap:` line when this is set.
SITEMAP_URL = env("SITEMAP_URL", default=None)
```
`.env.prod`:
```sh
SITEMAP_URL=https://example.com/sitemap.xml
```
### `config/sitemaps.py`
Same placement rule as `references/robots.md`: `config/` by default, or an existing `core`/landing app.
```python
from django.contrib.sitemaps import Sitemap
from django.urls import reverse
class StaticViewSitemap(Sitemap):
changefreq = "weekly"
priority = 0.5
def items(self):
return ["<url-name>"] # named URLs of the public pages
def location(self, item):
return reverse(item)
sitemaps = {"static": StaticViewSitemap}
```
For public model pages, add a `Sitemap` subclass whose `items()` returns the queryset — `location` defaults to each object's `get_absolute_url()`.
### `config/urls.py`
```python
from django.contrib.sitemaps.views import sitemap
from config.sitemaps import sitemaps
urlpatterns += [
path("sitemap.xml", sitemap, {"sitemaps": sitemaps}, name="sitemap"),
]
```
## Verifying
```sh
curl -sf http://127.0.0.1:8000/sitemap.xml | grep -q '<urlset'
curl -sf http://127.0.0.1:8000/ | grep -q 'property="og:title"'
```
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 |