playbooks

home / skills / leavesfly / jimi / backend-dev-suite

backend-dev-suite skill

/src/main/resources/skills/backend-dev-suite

This skill helps you accelerate backend development by enforcing Java best practices, designing robust databases, and applying OWASP-aligned security checks.

npx playbooks add skill leavesfly/jimi --skill backend-dev-suite

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.3 KB
---
name: backend-dev-suite
description: 后端开发综合技能包（Java 编码 + 数据库设计 + 安全加固）
version: 1.0.0
category: development
triggers:
  - backend dev suite
  - 后端开发整套
  - 后端最佳实践
  - Java 后端综合
  - 后端代码与数据库
dependencies:
  - java-best-practices
  - database-design
  - security-checklist
---

# 后端开发综合技能包

当你在进行后端功能开发或重构时，需要同时关注 **Java 编码规范**、**数据库设计** 与 **安全加固**，请启用本技能包。

本技能包会自动组合以下已有技能：

1. `java-best-practices`：Java 编码规范、设计模式与异常/并发最佳实践；
2. `database-design`：表结构设计、索引策略与 SQL 优化指南；
3. `security-checklist`：基于 OWASP 的安全检查清单与防护示例。

## 使用建议

- 在设计或修改后端接口/服务时：
  1. 先根据 `java-best-practices` 规划代码结构与异常处理；
  2. 再根据 `database-design` 设计数据模型和索引策略，避免 N+1、字段类型不当等问题；
  3. 最后按 `security-checklist` 检查认证授权、输入校验、敏感信息保护等安全要点。
- 回答时建议分三块输出：编码层面、数据层面、安全层面，方便你逐项检查和落地。

Overview

This skill packages a focused backend development toolkit that combines Java coding best practices, database design guidance, and security hardening. It helps developers design, refactor, and validate backend services by delivering concrete, actionable recommendations across code, data, and security layers.

How this skill works

The skill inspects intended design or existing code and returns three targeted sections: coding recommendations for Java, data model and SQL/index guidance, and security checks based on OWASP principles. It synthesizes patterns from Java best practices, database design heuristics, and a security checklist to produce prioritized, implementable actions.

When to use it

  • Designing or refactoring backend services and APIs
  • Preparing database schemas, indexes, and query plans
  • Performing security reviews or preparing for audits
  • Integrating new features that touch persistence or auth
  • Improving performance and reducing common bugs in Java code

Best practices

  • Provide inputs describing API responsibilities, expected load, and data access patterns before requesting advice
  • Request separate outputs for code, data, and security to make a clear implementation plan
  • Include sample code snippets and representative SQL when available for precise recommendations
  • Prioritize fixes by impact: security > data integrity > performance > style
  • Use suggested unit/integration tests and threat test cases to validate changes

Example use cases

  • Refactoring a monolithic service into cleaner Java modules with explicit exception handling
  • Designing a normalized schema and index plan to prevent N+1 queries for a new feature
  • Hardening authentication and session handling to meet OWASP Top 10 controls
  • Optimizing slow reports by reviewing SQL, adding appropriate indexes, or changing fetch strategies
  • Reviewing concurrency and thread-safety in a service that processes high write volume

FAQ

Will it modify my code or database automatically?

No. It provides recommendations and concrete change suggestions; you must apply and test them in your environment.

Can it generate migration scripts and unit tests?

It can produce example migration SQL and test templates, but generated artifacts should be reviewed and adapted to your conventions.