ContiNew Admin Frontend and Backend Development

Problem

In ContiNew Admin projects, backend conventions are spread across architecture, permission configuration, response formatting, and dependency choices, while frontend code can drift away from the existing Vue 3 + TypeScript + Arco Design patterns. For new contributors, the blocker is often not how to write one endpoint, but where a new module should sit, how permission codes should be configured, how DTOs should be split, what pagination responses should look like, and which utility libraries should be preferred.

How It Works

The skill packages ContiNew Admin constraints into a set of reference documents:

• Development guide: explains layering, module responsibilities, and annotation-driven CRUD under Spring Boot 3.x, MyBatis-Plus, and Sa-Token.
• Code templates: provide starting points for new modules, migration scripts, and common utilities, reducing the cost of assembling code from scratch.
• Frontend standards: constrain components, API calls, state, hooks, routing, and permission handling for admin pages built with Arco Design.
• Dependencies and response format: define when to prefer continew-starter and Hutool, and document structures such as R and PageResp for cleaner frontend-backend integration.

Boundaries

It fits teams that already use or plan to adopt the ContiNew Admin stack, especially when unifying code review, module generation, and API conventions. If the project uses a different stack or does not follow continew-starter module conventions, the templates and standards should be treated as references rather than drop-in rules for the existing architecture.