java-service-layer

A guide for writing the Service layer in a Java Spring Boot application, where business rules are kept between web requests and data access. It covers service interfaces, implementations, transactions, errors, logging, and dependency injection.

In plain words
What is it for?
It helps create or improve service interfaces and implementations, manage database transactions, handle exceptions, record logs, inject dependencies, and structure business logic.
Why use it?
It provides a consistent place for business logic and reduces common design mistakes in service code.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/lambert0529/skills/java-service-layer
Any agent
npx skills add lambert0529/skills --skill java-service-layer
Clone the repo
git clone --depth 1 https://github.com/lambert0529/skills

Made for: Claude Code, Codex.

Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,460 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00091 $0.01460
Opus 5 $0.00046 $0.00730
Sonnet 5 $0.00018 $0.00292
Haiku 4.5 $0.00009 $0.00146

Measured 2d ago against content hash 2bb6808388f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

java-service-layer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

java/java-service-layer/SKILL.md · 188 lines

How it starts

The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Java Service 层开发规范

快速开始

生成 Service 层代码的基本步骤:

  1. 定义 Service 接口(使用 assets/ServiceInterfaceTemplate.java
  2. 实现 Service 接口(使用 assets/ServiceImplTemplate.java
  3. 配置事务管理(见 references/transaction-management.md
  4. 封装业务逻辑(见 references/business-logic-patterns.md

接口与实现分离

规范要求

  • 定义 Service 接口(Interface)
  • 实现类使用 @Service 注解
  • 接口命名:XxxService
  • 实现类命名:XxxServiceImpl

代码模板

参考 assets/ServiceInterfaceTemplate.javaassets/ServiceImplTemplate.java 模板文件。

依赖注入最佳实践

1. 优先使用构造函数注入

@Service
@RequiredArgsConstructor  // Lombok 自动生成构造函数
public class UserServiceImpl implements UserService {
    private final UserRepository userRepository;  // final 字段,不可变
    private final EmailService emailService;
    
    // 依赖明确且可测试,无需 Spring 上下文即可实例化
}

优势

  • ✅ 依赖明确且不可变(final 字段)
  • ✅ 可测试性强,无需 Spring 上下文即可实例化
  • ✅ IDE 友好,依赖关系清晰
  • ✅ 线程安全

2. 处理可选依赖

@Service
@RequiredArgsConstructor
public class NotificationService {
    private final EmailProvider emailProvider;
    private SmsProvider smsProvider;  // 可选依赖
    
    public NotificationService(EmailProvider emailProvider) {
        this.emailProvider = Objects.requireNonNull(emailProvider);
    }
    
    @Autowired(required = false)
    public void setSmsProvider(SmsProvider smsProvider) {
        this.smsProvider = smsProvider;
    }
    
    public void notify(User user, String message) {
        emailProvider.send(user.getEmail(), message);
        if (smsProvider != null) {
            smsProvider.send(user.getPhone(), message);
        }
    }
}

3. 使用 @Qualifier 解决 Bean 歧义

@Service
@RequiredArgsConstructor
public class PaymentService {
    @Qualifier("stripePaymentGateway")
    private final PaymentGateway paymentGateway;
    
    public PaymentResult processPayment(PaymentRequest request) {
        return paymentGateway.charge(request);
    }
}

4. 避免字段注入

// ❌ 不推荐:字段注入
@Service
public class UserService {
    @Autowired
    private UserRepository userRepository;  // 难以测试,依赖不明确
}

// ✅ 推荐:构造函数注入
@Service
@RequiredArgsConstructor
public class UserService {
    private final UserRepository userRepository;  // 明确且可测试
}

Read the full file on GitHub · 188 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 188 lines · 91 tokens per session scan A 2bb6808388f1

Subscribe to this mod's changes

java-service-layer is a skill published in the GitHub repository lambert0529/skills (11 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 91 tokens to every session and 1,460 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens