eco-knock-be-central

Maintain eco-knock-be-central code in the repository's established style. Use when modifying, reviewing, refactoring, testing, or organizing project code, especially Spring Boot Kotlin/Java services, controllers, repositories, entities, DTOs, gRPC clients, Flyway migrations, and E2E tests.

Independently review and gate Eco Knock production-code diffs for package structure, Java/Kotlin boundaries, class placement, constructor injection, and consistency with nearby code. Use after any change under src/main and before completion; act as the read-only verifier in the developer → verifier → refactor → verifier workflow.

Update this repository's README so it matches the current implemented scope. Use when the user asks to create, rewrite, or refresh README content, document new features, update setup or deployment instructions, or keep the README in sync with current code, configuration, Docker deployment, Raspberry Pi behavior, or project limitations.

Keep this Spring Boot project's Scalar/OpenAPI documentation accurate when REST or SSE endpoints, controller annotations, request/response DTOs, status codes, ErrorCode entries, auth/security exposure, or API examples are added or changed. Use when adding a new endpoint, changing an existing endpoint contract, reviewing API docs, fixing Scalar or /v3/api-docs output, or updating OpenAPI annotations.

Inspect the repository state, recent git history, and both staged and unstaged diffs, then draft or create small Korean commits that match the local convention. Use when the user asks to write a commit message, make a git commit, summarize changes into commits, redo a mistaken commit, keep commit messages in Korean, or split a mixed diff into very small logical commits aligned with recent repository history.