spring-rest

Spring REST

Instructions

Build the API layer of the use case $ARGUMENTS: a @RestController that maps requests to the service methods of the service Handover, request and response records, and RFC 9457 Problem Details for every domain exception.

Scope

• Consumes the Handover of the service layer.
• Produces endpoints with their JSON and statuses for the UI layer and other clients.
• Never touches services, repositories, migrations, views, tests, or anything under docs/ other than the Markers table of docs/architecture/stack.md. Holds no business rule the service does not enforce.

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

Name the use case in the Javadoc of each handler method. A request DTO constraint that repeats a rule the service enforces gets // UC-XXX BR-YYY: <rule> above it.

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.

Handover

Handover from spring-rest (UC-XXX)
- POST /api/<resources> → 201 <Entity>Response; 409 Problem Details for <Reason>Exception (A<n>)
- record <Entity>Request(<fields>), record <Entity>Response(<fields>)
Nothing to do: <reason>