메뉴
Types Express route handlers in this project using generated contract namespaces (e.g. Drivers, Vehicles). Use when the user asks to type an Express endpoint, add TypeScript types to a route handler, or type request/response params in a *.routes.ts file.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Classifies and refactors error handling in this TMS codebase: decides when errors should be plain value objects (domain/application layer) vs instances of Error (infrastructure, unexpected, or input-validation guards). Generates the correct before/after transformation for domain errors, application service errors, and infrastructure errors. Use when the user asks to refactor errors, add a new error class, review error handling patterns, or when reviewing any *.errors.ts, *-service.ts, or *.routes.ts files.
Adds or updates endpoints in the OpenAPI contract based on the running API. Analyzes route files, DTO schemas, and real HTTP responses for each endpoint variant. Use when the user asks to add endpoints to the OpenAPI spec, update the contract, document a new route, or generate OpenAPI definitions from a running Express/Node API.
Creates a DTO type file for an Express endpoint by running the HTTP request, inspecting the real response, and generating TypeScript types. Then types the Express route handler with the new DTO. Use when the user asks to type an Express endpoint, create a DTO for an endpoint, add TypeScript types to a route handler, or type a response from a REST API endpoint.
Creates a new REST endpoint or updates an existing one in the TMS API. Covers the full workflow: OpenAPI contract (YAML), entry.yaml registration, contract bundling, TypeScript type generation, and typed Express route handler. Use when the user asks to add an endpoint, create a route, update the API contract, document a new route, or implement a REST handler in tms-api.
| name | type-express-endpoints |
| description | Types Express route handlers in this project using generated contract namespaces (e.g. Drivers, Vehicles). Use when the user asks to type an Express endpoint, add TypeScript types to a route handler, or type request/response params in a *.routes.ts file. |
| File | What's in it |
|---|---|
src/types/data-contracts.ts | Shared models: ErrorResponse, entity interfaces (DriverListItem, etc.) — symlink to contract/types/data-contracts.ts |
src/types/<Domain>Route.ts | Per-domain namespaces with RequestParams, ResponseBody, RequestBody, RequestQuery — symlink to contract/types/<Domain>Route.ts |
Always provide all four generic parameters to Request. Never use {} or omit parameters.
import { ErrorResponse } from '../types/data-contracts';
import { Drivers } from '../types/DriversRoute';
router.get('/', async (
req: Request<
Drivers.GetDrivers.RequestParams,
Drivers.GetDrivers.ResponseBody | ErrorResponse,
Drivers.GetDrivers.RequestBody,
Drivers.GetDrivers.RequestQuery
>,
res: Response<Drivers.GetDrivers.ResponseBody | ErrorResponse>,
) => { ... });
Request<Params, ResBody, ReqBody, Query> — all four, always.res: Response<SuccessBody | ErrorResponse> — always union with ErrorResponse.src/types/<Domain>Route.ts, e.g. Drivers, Vehicles, Customers.GetDrivers, CreateDriver, GetDriverById.ErrorResponse always from ../types/data-contracts.RequestBody is never (GET), it still appears in Request<> explicitly.RequestQuery, RequestBody, ResponseBody — use contract types. Local duplicates (e.g. GetCustomersHttpQuery, CustomerListItemResponse, PatchCustomerHttpBody) are redundant. Use Customers.GetCustomers.RequestQuery, Customers.GetCustomers.ResponseBody, Customers.PatchCustomer.RequestBody, etc. req.body is already typed via Request<> generics — no cast needed.