菜单
Apply Book Corners Django/PostGIS domain knowledge. Use when changing models, migrations, queries, admin behavior, seed data, fixtures, geospatial behavior, slug generation, dependencies, or core library/user app architecture.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run Book Corners local development commands. Use when starting services, running tests, applying migrations, building CSS, running the dev server, seeding demo data, or building local docs.
Handle Book Corners website UI work and validation. Use when changing Django templates, views, forms, JavaScript, HTMX interactions, static assets, CSS/Tailwind, browser behavior, or user-facing website text.
Create a GitHub issue/ticket for the Book Corners backend/web repo. Use whenever the user wants to file a bug, create a ticket, open an issue, report a problem, or request a feature/enhancement/documentation change for andreagrandi/book-corners.
Update Book Corners API behavior and documentation. Use when changing API endpoints, API schemas, API URL routing, search behavior used by the API, OpenAPI output, or API-facing request/response shapes.
Create Book Corners GitHub issues and add them to the Book Corners GitHub Project. Use when the user asks to add a ticket, create an issue, file a bug, or record an enhancement/documentation work item for this repository.
Handle Book Corners deployment, hosting, production logs, infrastructure, and environment configuration. Use for Dokku, VPS, DNS, SSL, Grafana Loki, production debugging, deploys, rollbacks, backups, or operational commands.
| name | book-corners-domain |
| description | Apply Book Corners Django/PostGIS domain knowledge. Use when changing models, migrations, queries, admin behavior, seed data, fixtures, geospatial behavior, slug generation, dependencies, or core library/user app architecture. |
Use this reference for core application architecture and domain patterns.
Book Corners is a Django 6 project with PostGIS geospatial data.
Apps:
users: custom AbstractUser model configured as AUTH_USER_MODEL = "users.User".libraries: core little free library domain.The Library model stores little free library locations with a PostGIS PointField using SRID 4326. The Report model tracks user-submitted issues about libraries.
Library and report moderation use status workflows managed through Django admin actions, including approving or rejecting libraries and resolving or dismissing reports.
Admin uses GISModelAdmin for Library so map-based editing is available.
Current URL routing includes web pages such as /, /login/, /register/, and /latest-entries/, Django admin at /admin/, and API routes scaffolded under /api/v1/.
When adding a model field or modifying queries, ensure fields used in filter(), order_by(), list_filter, or values_list() have a database index.
Add indexes in the model Meta.indexes list and generate a migration. Skip indexes for low-cardinality boolean fields or fields that are rarely queried.
Slug generation:
Library.save() auto-generates unique slugs from city + address + name.max_length.Database configuration:
dj-database-url parses DATABASE_URL.GDAL_LIBRARY_PATH and GEOS_LIBRARY_PATH are read from the environment in config/settings.py.Test fixtures:
user, admin_user, and admin_client in root conftest.py.library, admin_library, and admin_report in libraries/tests.py.e2e_user, approved_libraries, single_library, mock_external_apis, and authenticated_page in tests/e2e/conftest.py.Environment:
.envrc configures local macOS DATABASE_URL (discovered dynamically via scripts/local_env.py), GDAL_LIBRARY_PATH, and GEOS_LIBRARY_PATH..env.example contains Docker equivalents.Seed data:
seed_libraries can reset and generate realistic Library rows with geospatial points and mixed statuses.--reset, --count, --seed, and --images-dir.libraries_examples/ is intentionally gitignored so each developer can use local photo sets.Dependencies:
django, psycopg2-binary, Pillow, dj-database-url, pytest, pytest-django, gunicorn, and structlog.uv to install Python packages.uv lock file; use simple requirements files.