scaffold-endpoint

Scaffold New Endpoint

Create a new API endpoint by learning from the project's existing patterns. This agent does NOT assume any specific framework — it discovers the architecture from the codebase.

Phase 1 — Discover Project Patterns

Step 1: Identify the Stack

Detect the backend framework and architecture:

• Go: check go.mod for chi, gin, echo, fiber, mux, etc.
• Node.js: check package.json for express, fastify, nestjs, koa, hono, etc.
• Python: check requirements.txt/pyproject.toml for flask, fastapi, django, etc.
• Rust: check Cargo.toml for actix-web, axum, rocket, etc.

Step 2: Find the Architecture

Locate key architectural files:

1. Route registration — where are routes/endpoints registered?
   • Grep: Route|router|app\.get|app\.post|@app\.|urlpatterns|r\.Get|r\.Post
2. Handlers/Controllers — where do request handlers live?
   • Look for directory patterns: handlers/, controllers/, transport/, api/, routes/
3. Services/Business logic — where does business logic live?
   • Look for: services/, usecases/, domain/, business/
4. Data access/Repositories — where does DB access live?
   • Look for: repo/, repositories/, dal/, models/, db/
5. DTOs/Schemas — where are request/response types defined?
   • Look for: dto/, schemas/, types/, models/

Step 3: Read a Reference Endpoint

Find the closest existing endpoint to the requested one:

1. Grep for similar domain terms in handler files
2. Read the reference handler, service, and repo files
3. Note exact patterns: constructor style, error handling, middleware, response format

Phase 2 — Scaffold by Analogy

Generate each layer by following the reference pattern exactly:

1. Handler/Controller (Transport Layer)

Create in the same directory as existing handlers. Follow the reference for:

• Constructor/DI pattern
• Request parsing
• Response formatting
• Error mapping (domain errors -> HTTP status codes)
• Auth/middleware annotations