Api Implementation

Edge Cases

Refactoring Logic

flowchart TD
    A([Start: api_spec + tech_stack + context]) --> B{API type?}
    B -- REST --> C[Parse method + path + body schema]
    B -- GraphQL --> D[Parse resolver + input type + return type]
    C --> E[Implement request validation]
    D --> E
    E --> F{Validation passes?}
    F -- No --> G[Return 400 with field-level errors]
    F -- Yes --> H{Auth required?}
    H -- Not specified --> I[⚠️ Flag as security gap\nadd auth middleware comment]
    H -- Yes --> J{Auth valid?}
    J -- No --> K[Return 401 / 403]
    J -- Yes --> L[Delegate to service layer]
    I --> L
    L --> M{Business rule check}
    M -- Conflict/duplicate --> N[Return 409]
    M -- Rule violation --> O[Return 422]
    M -- Not found --> P[Return 404]
    M -- Pass --> Q{DB/external call}
    Q -- Error --> R[Log internally\nReturn 500 generic]
    Q -- Success --> S[Return 200/201 response]
    S --> T[Write tests:\nhappy path + 400 + 4xx]
    T --> U[List assumptions\n+ follow-up items]
    U --> V([Output: Handler + Tests\n+ Implementation Notes])

Examples

• Input Example
• Output Example

Quality Gate

1. Is the solution the simplest possible?
2. Are failure modes handled (4xx/5xx)?
3. Does it scale 10x in load/size?
4. Are security implications addressed?
5. is it testable and observable?

MCP Dependencies

• @upstash/context7-mcp: Library documentation and examples.

Changelog