backend-new-route

To add a new backend route, implement the service function in your services file, register the endpoint using the @bp.route decorator in routes.py, and return valid JSON. If building a distinct domain, create a new Blueprint and register it in your main app file.

Create a new Flask Blueprint when introducing a different application domain, keeping logic modular and testable. For simple demo extensions, add HTTP endpoints directly to existing routes.py and their corresponding logic to services.py.

Structure backend services and routes by separating logic into services.py and exposing them via HTTP endpoints in routes.py. Use clear parameters, adequate HTTP methods, and valid JSON returns to ensure endpoints remain consistent and testable.

Yes, you need to document API contracts and naming conventions in a reference skill after creating new HTTP endpoints. This ensures consistent reuse across teams and clarifies the expected request parameters and JSON response structures.

Register a new Flask Blueprint by defining it in the backend directory and wiring it into the app/main.py file. This connects your modular service logic to the core application architecture.

Yes, you can build demo routes by adding HTTP endpoints to backend/routes.py and placing the execution logic in backend/services.py. This ensures your API demos follow the established architectural conventions.