← 返回
未分类

ceshi

Use when working in the miaohong-cloud-base Java backend repository for multi-module Spring Boot development, gateway/auth/service debugging, Nacos-backed configuration work, MyBatis-Plus mapper changes, shared API contract updates, or backend troubleshooting in this codebase.
user_0f11e42a
未分类 community v1.0.0 1 版本 99056.6 Key: 无需
★ 0
Stars
📥 105
下载
💾 0
安装
1
版本
#latest

概述

Miaohong Java Backend

Overview

Use this skill to work inside miaohong-cloud-base without rediscovering the repository layout every time. Load only the references needed for the current task so the context stays focused.

The repository root file CLAUDE.md is the primary coding standard for this project. When any older repository habit or this skill conflicts with CLAUDE.md, follow CLAUDE.md.

Workflow

  1. Confirm the scope before editing.
  2. Work from source, not generated output.
    • Prefer files under src/main and src/test.
    • Ignore target/ unless you are checking built artifacts on purpose.
  3. Keep changes as narrow as possible.
    • Prefer targeted Maven builds with -pl -am.
    • Fall back to full-repo builds only when module boundaries are unclear.
  4. Treat configuration as split across local files and Nacos.
    • bootstrap.yml usually defines the application name, active profile placeholder, and Nacos imports.
    • application.yml usually carries local overrides such as logging, static resources, or module-specific behavior.
  5. Verify the right layer when behavior changes cross services.
    • Shared infrastructure belongs in miaohong-common.
    • Shared API contracts and Feign-facing DTOs belong in miaohong-modules-api.
    • Runtime business behavior belongs in the concrete service module under miaohong-modules, miaohong-auth, or miaohong-gateway.

Repo-Specific Guardrails

  • Assume Java 17 and Maven are required.
  • Assume runtime configuration depends on reachable Nacos namespaces and imported config sets.
  • Expect business modules to be package-first, for example com.miaohong.ai.user, not feature folders under a single controller tree.
  • Check for mapper XML beside Java packages because this repository stores many *Mapper.xml files under src/main/java/.../mapper/xml, not under src/main/resources.
  • When a request changes an external or shared contract, inspect both the provider module and the relevant API module before editing.
  • For controller interface documentation, prefer Javadoc comments above the method and do not add Swagger annotations.
  • For request and response shape, treat CLAUDE.md as the source of truth:
  • no @PutMapping
  • no @DeleteMapping
  • no @PathVariable
  • POST uses @RequestBody DTO
  • GET is limited to single-parameter queries
  • no Map request bodies or response payloads
  • For Java classes generated in this repo, use @author bianruhao.
  • For service implementations, avoid introducing circular dependencies across services. Prefer extracting shared logic, using mappers/providers, or moving cross-cutting behavior to a shared module instead of having services inject each other in a loop.

Reference Map

版本历史

共 1 个版本

  • v1.0.0 Initial release 当前
    2026-04-10 13:46 安全 安全

安全检测

腾讯云安全 (Keen)

安全,无风险
查看报告

腾讯云安全 (Sanbu)

安全,无风险
查看报告

🔗 相关推荐

security-compliance

Skill Vetter

spclaudehome
AI智能体技能安全预审工具。安装ClawdHub、GitHub等来源技能前,检查风险信号、权限范围及可疑模式。
★ 1,216 📥 266,608
ai-intelligence

Self-Improving + Proactive Agent

ivangdavila
自我反思+自我批评+自我学习+自组织记忆。智能体评估自身工作、发现错误并持续改进。
★ 1,359 📥 318,562
developer-tools

Github

steipete
使用 `gh` CLI 与 GitHub 交互,通过 `gh issue`、`gh pr`、`gh run` 和 `gh api` 管理议题、PR、CI 运行及高级查询。
★ 669 📥 324,253