role-backend-developer

To implement backend API endpoints from an architectural specification, you need to provide detailed API contracts and data models. The system then acts as a backend developer to generate production-ready RESTful API code, business logic, and data access layers adhering to architectural conventions.

The repository pattern for backend data access layer implementation abstracts data persistence logic away from business logic. It allows the system to implement clean, framework-independent data persistence code based on your provided data models and specifications.

Writing framework-independent business logic for a RESTful API involves isolating core processing rules from external dependencies. By providing detailed architectural specifications, the system generates clean business logic code separate from API endpoint routing and data access layers.

Yes, you need to provide detailed API contracts and data models to generate backend code. The implementation requires comprehensive architectural specifications, including endpoint definitions and data structures, to produce production-ready API endpoints and database interaction logic.

Yes, you can use an architectural spec to generate a complete user registration API. Given the architect's specification for the registration endpoint, the system produces the necessary API endpoint, validation, business logic, and database interaction code.

The main limitation is the strict requirement for detailed specifications; without comprehensive API contracts and data models, implementation cannot proceed. The system focuses solely on API endpoints, business logic, and data access layers, requiring pre-defined architectural conventions.