← ClaudeAtlas

python-django-stacklisted

Python and Django conventions for multi-tenant SaaS POS projects: views, services, naming, JSON APIs, PDFs, and cart patterns. Trigger: When writing any view, service, API endpoint, or model code in apps/.
lgzarturo/codeconductor · ★ 0 · AI & Automation · score 76
Install: claude install-skill lgzarturo/codeconductor
## When to Use - Writing any new view, service method, or API endpoint - Designing a new feature and deciding where logic lives - Adding a JSON API response - Implementing a PDF report or cart operation - Structuring the architecture of a new app ## Django Project Structure ### Recommended Apps A well-structured Django project follows modular app patterns: ``` apps/ ├── core/ # Configuration, shared models (Store) ├── users/ # User model, authentication ├── employees/ # Employees (tenant) ├── catalog/ # Products, categories (tenant) ├── cart/ # Storefront cart (tenant) ├── orders/ # Orders (tenant) ├── pos/ # Point of Sale (tenant) ├── storefront/ # Public store (tenant) └── analytics/ # Reports and metrics (tenant) ``` ### Per-App File Structure ``` apps/catalog/ ├── __init__.py ├── models.py # Models (Product, Category, ProductImage) ├── views.py # Views ├── urls.py # Routes ├── services.py # Business logic ├── serializers.py # Serialization (if using DRF) ├── reports.py # PDF reports ├── signals.py # Signals ├── admin.py # Admin config ├── tests/ │ ├── __init__.py │ └── test_{feature}.py └── migrations/ ``` ## View Patterns ### FBV vs CBV | Type | When to Use | Examples | | ------------------------ | -----------------------