backend-microservice-development
It enforces architectural patterns for microservices by organizing logic into API, Service, and DAO layers for system stability.
Install
mkdir -p .claude/skills/backend-microservice-development && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2078" && unzip -o skill.zip -d .claude/skills/backend-microservice-development && rm skill.zipInstalls to .claude/skills/backend-microservice-development
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
编写 BK-CI 后端微服务代码时使用，例如新增 Resource、组织 API/Service/DAO 分层、依赖注入、服务归属判断和 Spring Boot 开发约定。当用户要做 Kotlin/Java 后端开发时优先使用。Key capabilities
- →Add or modify Kotlin/Java backend functions
- →Add Resource, Service, DAO, or microservice modules
- →Determine service ownership for new features
- →Organize code according to project layering conventions
- →Ensure clear boundaries between Resource, Service, and DAO
How it works
This skill guides the organization of backend microservice code by defining strict layering for API, business logic, and data access, ensuring proper service ownership and interaction through API contracts.
Inputs & outputs
When to use backend-microservice-development
- →Creating a new microservice module
- →Organizing business logic in Spring Boot
- →Implementing new API endpoints
- →Defining service and data access layers
About this skill
后端微服务开发
适用场景
- 新增或修改 Kotlin / Java 后端功能
- 新增 Resource、Service、DAO 或微服务模块
- 判断功能应该落到哪个服务
- 按项目分层约定组织代码
不适用场景
- 前端 Vue 页面开发
- Go Agent 开发
- 单纯设计 API 契约或数据库模型
快速指导
- 这个 skill 关注的是“BK-CI 后端功能如何组织和落位”，不是单纯 Spring Boot 入门。
- 开发前先做服务归属判断，再决定接口、服务和数据层放哪。
- 核心分层仍然是 API、业务实现、启动模块和数据模型，不要跨层乱放逻辑。
- 服务间交互走 API 契约，不直接碰别的服务数据库。
- 如果问题是接口设计细节，联动看
api-interface-design；如果是测试，联动看unit-testing。
高信号规则
- 功能落位比代码实现本身更容易决定后续维护成本
- Resource、Service、DAO 的边界清楚，后续扩展才稳定
- 微服务之间只共享契约，不共享存储实现
关键陷阱
- 为了快，直接把逻辑塞进 Resource
- 服务归属判断错误，导致后续跨服务耦合
- 因为调用方便而直接访问其他服务数据
延伸阅读
- 如果你在设计接口：再看
api-interface-design - 如果你在写测试：再看
unit-testing - 如果你在看基础设施：再看
microservice-infrastructure - 如果你在看 Spring Boot 框架实践：再看
springboot-backend-conventions
When not to use it
- →Frontend Vue page development
- →Go Agent development
- →Solely designing API contracts or database models
Limitations
- →Does not cover frontend Vue page development
- →Does not cover Go Agent development
- →Does not cover only API contract or database model design
How it compares
This skill provides specific guidelines for structuring BK-CI backend microservices, unlike general Spring Boot development, by focusing on service ownership and clear layer boundaries.
Compared to similar skills
backend-microservice-development side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| backend-microservice-development (this skill) | 2 | 3mo | No flags | Intermediate |
| java-pro | 34 | 4mo | No flags | Advanced |
| microservice-infrastructure | 4 | 3mo | No flags | Intermediate |
| common-technical-practices | 2 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by TencentBlueKing
View all by TencentBlueKing →You might also like
java-pro
sickn33
Master Java 21+ with modern features like virtual threads, pattern matching, and Spring Boot 3.x. Expert in the latest Java ecosystem including GraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java development, microservices architecture, or performance optimization.
microservice-infrastructure
TencentBlueKing
微服务基础设施指南，涵盖条件配置、事件驱动架构、服务间通信、国际化与日志等微服务架构的核心基础设施。当用户实现服务间调用、配置多环境、实现异步通信、处理国际化或规范日志输出时使用。
common-technical-practices
TencentBlueKing
通用技术实践指南，涵盖 AOP 切面、分布式锁、重试机制、参数校验、性能监控、定时任务、审计日志等后端开发中的常见技术实践。当用户需要实现横切关注点、处理并发控制、配置重试策略、添加性能监控或实现审计功能时使用。
spring-boot-4-conventions
loiane
Spring Framework 7 / Spring Boot 4 idioms and defaults. Use when writing or reviewing controllers, services, configuration, HTTP clients, async/virtual-thread code, or anything touching Spring's programming model.
clean-architecture
darshanchaudharii
Provides implementation patterns for Clean Architecture, Hexagonal Architecture (Ports & Adapters), and Domain-Driven Design in Java 21+ Spring Boot 3.5+ applications. Use when structuring layered architectures, separating domain logic from frameworks, implementing ports and adapters, creating entit
Context7 MCP Rule
dlwlrmjlo
Always use the Context7 MCP server when foundational planning or architecture decisions are being made.