Interface IAutoBeRpcListener

Mandatory handler for requirements analysis completion events.

Called when the analysis phase completes successfully, providing the finalized requirements documentation that serves as the foundation for all subsequent development phases. Client applications must handle this event to receive the completed analysis artifacts.

Optional handler for requirements analysis review events.

Called during the review and amendment phase, enabling client applications to show that requirements are being refined and improved based on feedback and additional analysis.

Optional handler for requirements analysis compose events.

Occurs when an agent is called that generates metadata for the analysis, such as the table of contents, role, number of pages, and so on.

Optional handler for requirements analysis start events.

Called when the Analyze agent begins drafting the requirements analysis, enabling client applications to show analysis phase initiation and prepare progress indicators for the requirements documentation process.

Optional handler for requirements analysis writing progress events.

Called during the writing phase as analysis documents are being created, allowing client applications to display real-time progress and provide visibility into the document generation process.

Mandatory handler for assistant message events during conversation flow.

Called when the AI assistant sends messages to the user, providing responses, explanations, progress updates, and guidance throughout the vibe coding workflow. This is a core communication channel that keeps users informed about ongoing activities and system responses.

Optional handler for API authorization operation definition progress events.

Called as detailed authorization operation specifications are created for each endpoint, enabling client applications to track progress and show how API authorization is being systematically developed.

Optional handler for API schema complement events.

Called when missing schemas are identified and added to complete the specification, enabling client applications to show that gaps are being filled to ensure comprehensive API coverage.

Mandatory handler for API design completion events.

Called when the Interface phase completes successfully, providing the complete OpenAPI specification and generated NestJS application files. Client applications must handle this event to receive the completed API artifacts.

Optional handler for API endpoint creation events.

Called when the complete list of API endpoints is established, allowing client applications to show the API surface area scope and architectural foundation being built.

Optional handler for API endpoint review events.

Called when the Interface agent reviews API endpoints, enabling client applications to show the review process and any identified issues.

Optional handler for API interface group creation events.

Called when the Interface agent generates groups of API endpoints based on the organized database schemas, enabling client applications to show the initial scope of API surface area being designed and track progress in the interface design phase.

Optional handler for API operation definition progress events.

Called as detailed operation specifications are created for each endpoint, enabling client applications to track progress and show how API functionality is being systematically developed.

Optional handler for API operation review events.

Called when the Interface agent reviews API operations, enabling client applications to show the review process and any identified issues.

Optional handler for API component schema creation events.

Called when reusable schema components are being defined, allowing client applications to show progress in type definition and data structure development for the API specification.

Optional handler for API schema review and enhancement events.

Called when the Interface agent reviews and improves the generated OpenAPI schemas, enabling client applications to show the quality assurance process where schemas are validated for completeness, security compliance, and type safety before being integrated into the final API specification.

Optional handler for API design start events.

Called when the Interface agent begins RESTful API specification design, enabling client applications to indicate the start of API development and prepare progress tracking for the interface design phase.

Mandatory handler for database design completion events.

Called when the Prisma phase completes successfully, providing the validated database schemas and compilation results. Client applications must handle this event to receive the completed database artifacts.

Optional handler for database component organization events.

Called when tables are organized into categorized groups by business domain, allowing client applications to display the structural planning of the database architecture and show progress scope.

Optional handler for database schema correction events.

Called when the AI self-correction process addresses validation failures, enabling client applications to show that issues are being resolved automatically through the feedback loop mechanism.

Optional handler for database schema insufficient model creation events.

Called when the AI function calling process creates fewer models than expected for a specific business domain during database schema generation. This event indicates that the schema creation was incomplete and may require additional iterations or corrective actions to generate the missing models.

Client applications can use this event to inform users about partial schema completion, display which models were successfully created versus which are still missing, and potentially trigger retry mechanisms or manual intervention workflows to complete the database design.

The event provides detailed information about completed models and missing model names, enabling targeted recovery strategies to address the insufficient generation and ensure comprehensive database schema coverage.

Optional handler for database schema review events.

Called when the Prisma agent reviews and validates schema modifications, enabling client applications to show that the database design is being thoroughly evaluated against best practices and business requirements.

Client applications can use this event to display the review findings, highlight any necessary modifications, and confirm that the schema adheres to normalization principles, relationship integrity, and performance optimization.

The review process ensures that the database design is robust, maintains data integrity, and aligns with the overall project goals and requirements.

Optional handler for database schema creation progress events.

Called each time a domain-specific schema file is completed, enabling client applications to track incremental progress and show which business areas have been fully designed.

Optional handler for database design start events.

Called when the Prisma agent begins database schema design, enabling client applications to indicate the start of data architecture development and prepare progress tracking for the database design phase.

Optional handler for database schema validation events.

Called when validation failures occur during schema compilation, allowing client applications to inform users about quality assurance processes and potential correction activities.

Optional handler for authorization implementation completion events.

Called when the Realize agent completes the implementation of all authorization components, signaling that the authentication and authorization system is fully implemented and ready for use.

Optional handler for authorization correction events.

Called when the Realize agent corrects compilation failures in the generated authorization implementation code (providers, payloads, decorators), enabling client applications to show that issues are being resolved automatically through iterative improvement.

Optional handler for authorization implementation start events.

Called when the Realize agent begins implementing authentication and authorization components, including providers, payloads, and decorators for role-based access control.

Optional handler for authorization validation events.

Called when the Realize agent validates the generated authorization components (providers, payloads, decorators), enabling client applications to show quality assurance processes and potential correction activities for the authentication and authorization system.

Optional handler for authorization implementation progress events.

Called when the Realize agent generates authorization components (providers, payloads, decorators) for each user role, enabling client applications to track the progress of authorization system implementation.

Optional handler for implementation completion events.

Called when the Realize phase completes successfully, providing the complete working application implementation. Client applications must handle this event to receive the final implementation artifacts that represent the culmination of the entire vibe coding pipeline.

Optional handler for implementation correction events.

Called when the AI self-correction process addresses compilation or logic errors in implementation code, allowing client applications to reflect that backend logic is being automatically improved through iterative fixes.

This enables real-time visibility into how faulty implementation files are revised and finalized by the Realize agent to meet project standards.

Optional handler for implementation start events.

Called when the Realize agent begins implementing business logic and service layer code, enabling client applications to indicate the start of the final implementation phase.

Optional handler for implementation test completion events.

Called when the complete test suite execution finishes, providing test results and validation outcomes. Client applications can use this event to show final quality assurance results and confirm that the generated application meets all specified requirements and passes comprehensive validation.

Optional handler for implementation test operation events.

Called during individual test operation execution, enabling client applications to provide detailed progress tracking and show which specific API endpoints and business logic components are being validated through the comprehensive test suite.

Optional handler for implementation test reset events.

Called when the test environment is reset between test runs, allowing client applications to show that clean testing conditions are being established to ensure reliable and isolated test execution.

Optional handler for implementation test start events.

Called when the Realize agent begins running the test suite to validate the generated implementation, enabling client applications to show that comprehensive testing is beginning to ensure application quality and functionality.

Optional handler for implementation validation events.

Called when implementation code undergoes compilation validation, allowing client applications to show quality assurance processes and potential correction activities for the final implementation.

Optional handler for implementation progress events.

Called as individual implementation files are created, enabling client applications to track incremental progress and show how the complete application functionality is being assembled.

Mandatory handler for test suite completion events.

Called when the Test phase completes successfully, providing the complete test suite with comprehensive validation coverage. Client applications must handle this event to receive the completed test artifacts.

Optional handler for test code correction events.

Called when the AI self-correction process addresses compilation failures in test code, enabling client applications to show that issues are being resolved automatically through iterative improvement.

Optional handler for test scenario planning events.

Called when test scenarios are being planned and organized, allowing client applications to show the scope of validation coverage being designed for the application.

Optional handler for test suite generation start events.

Called when the Test agent begins creating e2e test scenarios, enabling client applications to indicate the start of test development and prepare progress tracking for comprehensive validation coverage.

Optional handler for test code validation events.

Called when test code undergoes TypeScript compilation validation, allowing client applications to show quality assurance processes and potential correction activities for test code.

Optional handler for test code generation progress events.

Called as individual test files are created, enabling client applications to track incremental progress and show which API endpoints are being validated through comprehensive test scenarios.

Optional handler for user message events during conversation flow.

Called when user messages are processed, allowing client applications to track conversation history and provide enhanced user interface features such as message confirmation or conversation replay capabilities.