メニュー
Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.
Improve and rewrite user prompts to reduce ambiguity and improve LLM output quality. Use when a user asks to optimize, refine, clarify, or rewrite a prompt for better results, or when the request is about prompt optimization or prompt rewriting.
Edits, rewrites, or improves text for clarity, tone, grammar, or style.
Validate API changes against an expected contract. Use when a mid-level developer needs to detect breaking changes.
Build a basic HTTP request (curl or fetch) for an API. Use when a junior developer needs a quick request example.
Optimize GraphQL queries and resolvers for performance. Use when a mid-level developer needs to reduce N+1 or payload size.
Review a system architecture for scalability, reliability, and maintainability. Use when a senior developer needs to critique a design.
| name | api-error-taxonomy |
| description | Define consistent API error codes and responses. Use when a mid-level developer needs error standardization. |
Define consistent API error codes and responses.
