feat: update prompt to specify SQLite preference for database-backed services

- Add requirement to use SQLite for every service that will support it
- Avoid heavier databases like PostgreSQL, MySQL when SQLite is adequate
- Only use heavier databases when SQLite is not supported or inadequate
- Implement proper SQLite volume management and security practices
- Configure SQLite as default database engine in environment variables
- Ensure data integrity and performance when migrating to SQLite
- Implement proper backup strategies for SQLite databases

collab/SupportStack/BuildTheStack

@@ -103,6 +103,15 @@ Create a proof of concept with docker-socket-proxy, homepage, and wakaapi compon
 - Implement security scanning during build process (for demo, secrets via environment variables are acceptable)
 - Define network policies for internal communication only
 - Use depends_on with health checks to ensure proper startup ordering of services
+- Use SQLite for every service that will support it to avoid heavier databases where possible
+- For services requiring databases, prefer lightweight SQLite over PostgreSQL, MySQL, or other heavy database systems
+- Only use heavier databases when SQLite is not supported or inadequate for the service requirements
+- When using SQLite, implement proper volume management for database files using Docker volumes
+- Ensure SQLite databases are properly secured with appropriate file permissions and encryption where needed
+- Avoid external database dependencies when SQLite can meet the service requirements
+- For database-backed services, configure SQLite as the default database engine in environment variables
+- When migrating from heavier databases to SQLite, ensure data integrity and performance are maintained
+- Implement proper backup strategies for SQLite databases using Docker volume snapshots
 - Homepage container requires direct Docker socket access (not through proxy) for automatic label discovery
 - Docker socket proxy provides controlled access for other containers that need Docker access
 - Portainer can use docker-socket-proxy for read-only access