onflou-spring-conv-code

You can enforce Spring backend code conventions by loading dedicated MCP resources that define layer boundaries, package structure, and role-specific rules for Controller, Service, and Mapper components to ensure consistent implementation.

The recommended package structure and DTO naming conventions are provided through loaded MCP resources that specify exact model naming patterns and package organization to maintain clear architectural boundaries in your Spring backend.

MyBatis database rules and exception handling in a Spring project are configured using predefined backend quality standards that guide DB interactions, response formatting, and logging to maintain consistent error management.

Yes, MCP resources can be used to guide Spring backend security and logging standards by loading convention resources that provide specific rules for secure coding practices and standardized log management.

The best way to review Spring backend code against Onflou project conventions is by loading dedicated Skill resources that provide comprehensive guidance on code conventions, refactoring, and layer boundaries for quality assurance.