AGENTS.md

This file gives AI coding agents project-specific guidance for the Dailog backend.

Project Overview

Note: npm run lint currently runs ESLint with --fix, so it may modify existing files.

File names use kebab-case plus a role suffix.
Examples:
- schedule.controller.ts
- schedule.service.ts
- schedule.module.ts
- schedule.dto.ts
- schedule.entity.ts
- schedule.interface.ts
Domain folders use plural kebab-case, such as schedules, diaries, categories.
DTOs for the same domain should be grouped in one *.dto.ts file when practical.

Keep domain logic in domain modules.
Controllers should handle routing and delegate business logic to services.
Services should own business logic, validation beyond DTO checks, database access, and external API calls.
Do not access repositories or the database directly from controllers.
Register controllers and providers in the matching module.
When another module's service is needed, use imports and exports explicitly.
Put only truly shared filters, interceptors, decorators, and helpers under src/global or shared/common folders.

Global exception handling lives under src/global/error.
Success response wrapping lives under src/global/common.
Controllers should not manually wrap successful responses as { resultType: "SUCCESS", ... }; the response interceptor handles that.
Throw custom exceptions instead of using local try/catch for ordinary API errors.
Failure responses should follow:

{
  "resultType": "FAIL",
  "code": 500,
  "errorCode": "INTERNAL_SERVER_ERROR",
  "reason": "서버 내부 오류가 발생했습니다",
  "data": null
}