Cline rules

1# Routing Pattern
2 
3## Brief overview
4 
5Routes must be thin, declarative wrappers. All business logic lives in controllers.
6 
7## Rule: Thin Routes, Fat Controllers
8 
9- `routes/*.ts` export only thin handler functions — each handler is an `async (c: Context) => Response` function that delegates immediately to the corresponding controller in `controllers/`.
10- `routes/index.ts` is 100% declarative — it imports all handlers and registers routes with `app.post('/', handler)` or `app.get('/', handler)` inside `registerRoutes(app)`. No business logic, no conditionals, no validation in the routing layer.
11- No business logic, no conditionals, no validation in routes.
12 
13## Anti-patterns to avoid
14 
15- Do NOT add logic in route handlers — if you find yourself adding logic in a route handler, extract it to the corresponding controller.
16- Do NOT put business logic in `routes/index.ts` — route registration should only import handlers and attach them to paths.
17 
18## Example
19 
20```typescript
21// routes/index.ts — 100% declarative
22import { handleChatCompletions } from '../controllers/chat'
23 
24export const registerRoutes = (app: any) => {
25  app.post('/:version/chat/completions', handleChatCompletions)
26}
27 
28// controllers/chat.ts — all business logic here
29export async function handleChatCompletions(c: Context) {
30  // ... provider resolution, streaming, error handling, metrics
31}
32```
33 
34## Pattern checks
35 
36- If `routes/index.ts` contains anything other than route registration (conditionals, validation, business logic), the routing pattern is violated.
37- If a handler in `routes/*.ts` contains more than a single call to a controller, the separation of concerns is violated.
38