Enhance static files management guidelines: clarify directory structure, file management rules, and benefits of separation for better adherence to Django best practices

.clinerules

@@ -28,3 +28,16 @@ This applies to all management commands including but not limited to:
 - Starting shell: `uv run manage.py shell`
 
 NEVER use `python manage.py` or `uv run python manage.py`. Always use `uv run manage.py` directly.
+
+## Static Files Management
+IMPORTANT: All static files must be placed in the `static/` directory, not `staticfiles/`. The `staticfiles/` directory is reserved for Django's collectstatic command output and should not be used directly.
+
+This consolidation:
+1. Follows Django best practices of separating source static files from collected files
+2. Prevents confusion between development and production static file locations
+3. Makes it clear which static files are part of the source code (static/) versus compiled/collected (staticfiles/)
+
+When adding new static files:
+- Add them to `static/` directory
+- Use Django's `static` template tag to reference them
+- Run `uv run manage.py collectstatic` when deploying

memory-bank/systemPatterns.md

@@ -21,6 +21,23 @@
    - Implement component-based structure
    - Follow progressive enhancement
 
+### Static Files Organization
+1. Directory Structure
+   - `static/` - Source static files (CSS, JS, images, etc.)
+   - `staticfiles/` - Collected files (generated by collectstatic)
+
+2. File Management Rules
+   - Place all source static files in `static/` directory
+   - Never directly modify `staticfiles/` directory
+   - Use Django's `static` template tag for references
+   - Run collectstatic before deployment
+
+3. Benefits of Separation
+   - Clear distinction between source and compiled files
+   - Prevents confusion in development vs production
+   - Follows Django best practices
+   - Simplifies deployment process
+
 ## Design Patterns
 
 ### Data Access