Miaohong Java Backend Guide

Problem it solves

In a multi-module miaohong-cloud-base codebase built with Java 17 and Maven, the hard part is often not writing endpoints, but knowing where changes belong: which service module, which shared API module, which Mapper.xml files, and which Nacos config set takes effect. Re-discovering the layout every time can lead to edits in target/, misplaced Feign contracts, or circular service dependencies.

How the skill works

The skill packages repository knowledge into task-specific references. It starts from the root CLAUDE.md as the primary coding standard, then loads only the needed files such as references/module-map.md, references/commands.md, and references/conventions.md. For controller endpoints, Feign providers, mapper XML, exception propagation, and troubleshooting, it points to separate style guides. It also favors narrow builds with -pl and -am, keeps source changes under src/main and src/test, and enforces repo request rules such as POST with @RequestBody DTOs, GET limited to single-parameter queries, and no @PutMapping, @DeleteMapping, @PathVariable, or Map request/response payloads.

Boundaries

This skill is scoped to backend work in miaohong-cloud-base and expects CLAUDE.md to override older habits. If module boundaries, Nacos namespaces, or mapper XML locations change, follow the current repository and CLAUDE.md. It does not replace human review of cross-service contract changes, and it is not intended as a generic Java backend guide.