spring-service

Spring Service

Instructions

Build the service layer of the use case $ARGUMENTS: a @Service with @Transactional methods that enforce the business rules and throw a domain exception per alternative flow the service decides.

Scope

• Consumes the Handover of the persistence layer: the repository, its methods, and the records they return.
• Produces the public service methods the layer above calls — a @RestController, a Vaadin Flow view, or a Hilla @BrowserCallable endpoint — with their input records, return types, and exceptions.
• Never touches queries, migrations, controllers, views, endpoints, tests, or anything under docs/ other than the Markers table of docs/architecture/stack.md.

Run Directly or from /use-case-implement

Run from /use-case-implement, this skill inherits the inputs that skill read, the gaps the user answered, and its rules for reconciling an existing implementation; it does not repeat the status check or ask the same questions again. Run directly, read the use case, the requirements it links, docs/entity_model.md, and docs/architecture/stack.md yourself, and stop on a Draft or Reviewed use case.

Business Rule Markers

Every business rule of the use case is enforced here, whatever else enforces it too. Put // UC-XXX BR-YYY: <rule> directly above the guard clause or method that enforces it, and name the use case in the Javadoc of each public method that realizes a step or an alternative flow. Read the time from an injected Clock.

Markers

Keep this skill's rows in the Markers table of docs/architecture/stack.md exactly as references/markers.md lists them: add them when they are missing, correct them when they differ. Touch no other row.

Workflow