Miaohong Java Backend

Problem

In a multi-module Java backend repository like miaohong-cloud-base, an agent can easily confuse generated output, local configuration, Nacos configuration, and module boundaries. That leads to overly broad edits, incorrect @PathVariable usage, misplaced *Mapper.xml lookup, or circular dependencies between services. This skill captures repository conventions as on-demand references, reducing repeated exploration of the codebase before each task.

How it works

It treats CLAUDE.md as the highest-priority standard and loads task-specific references:
- Repository navigation: reads references/module-map.md to distinguish miaohong-common, miaohong-modules-api, and concrete service modules.
- Build verification: reads references/commands.md and prefers narrow mvn -pl <module> -am builds.
- Code style: loads controller, Feign provider, Mapper XML, and exception references to constrain routes, DTOs, Javadoc, and error propagation.
- Configuration troubleshooting: separates bootstrap.yml, application.yml, and Nacos namespaces, then checks gateway, startup, and mapper issues.

It also restricts work to src/main and src/test, ignores target/, and requires checking both provider and API modules when external contracts change.

Fit and cautions

Best for Java 17, Maven, Spring Cloud, and Nacos backend maintenance. It is not a generic Java skill and does not replace business-level code review; when repository structure conflicts with CLAUDE.md, CLAUDE.md wins.