scaffold-endpoint

Scaffold New Endpoint

Generator agent: creates a new API endpoint (handler, service, repository, route registration, migration, DTO) by discovering and copying the project's existing patterns.

Hard Rules

1. Discover, don't assume — detect the framework and layering from the codebase. NEVER hardcode a framework convention.
2. Follow the reference endpoint's pattern exactly: same constructor/DI style, error mapping, middleware, response format.
3. NEVER invent a convention. If neither the codebase nor the docs show a pattern for a layer, ask the user instead of guessing.
4. Every file you claim to create must exist on disk, and the project must still build (see Done ONLY when).
5. Stub business logic with explicit TODO markers and list every stub in the report.

Phase 0 — Load Project Context

Read if present, skip silently if absent: CLAUDE.md or AGENTS.md; docs/architecture/backend-layers.md (layering, DI, error handling, how to add endpoints); docs/architecture/api-reference.md (existing endpoints, naming, auth requirements). Use it to: pick the documented layer pattern, error types, HTTP status mappings, auth middleware, and route grouping. If no docs exist, rely on Phase 1 discovery alone.

Phase 1 — Discover Project Patterns

Step 1: Identify the stack

Marker file	Look for framework
go.mod	chi, gin, echo, fiber, mux
package.json	express, fastify, nestjs, koa, hono
requirements.txt / pyproject.toml	flask, fastapi, django
Cargo.toml	actix-web, axum, rocket

Done when: framework identified, or explicitly recorded as "unknown — using docs/user guidance".

Step 2: Locate the architecture

1. Route registration — Grep: Route|router|app\.get|app\.post|@app\.|urlpatterns|r\.Get|r\.Post
2. Handlers/Controllers — directories: handlers/, controllers/, transport/, api/, routes/
3. Services/Business logic — services/, usecases/, domain/, business/
4. Data access/Repositories — repo/, repositories/, dal/, models/, db/
5. DTOs/Schemas — dto/, schemas/, types/, models/