# Eric Backend

> Apply when implementing or reviewing transport handlers, service/core boundaries, backend DTO ownership, input validation boundaries, or service bootstrap.

- Skill: `akarachen/eric-backend` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add akarachen/eric-backend`
- Raw SKILL.md: https://api.skillmd.com/api/skills/akarachen/eric-backend/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: akarachen (https://skillmd.com/u/akarachen)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/akarachen/eric-backend

---


# Eric Backend

- Keep controllers as short and thin as possible. Prefer framework-native parsing, validation, binding, and response handling over handwritten controller plumbing, unless the project has an established convention. Keep business logic in service/core.
- Keep DTO/request/response types with their owning module, unless the project has a shared contract layer.
- Keep runtime setup, managed state, database initialization, migrations, logging, and shutdown wiring in the application entrypoint.