When building a public API where inconsistent errors confuse developers and slow integrations.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: API Development & Integrations - Use case: API Error Design System - Source task: - Design a consistent error handling and response system for {{describe_the_api}}. Include: - 1. error response schema (error code, message, details, request ID, documentation link) - 2. HTTP status code mapping to error categories - 3. machine-readable error codes taxonomy (AUTH_001, VALIDATION_002, etc.) - 4. human-readable messages that are helpful without exposing internals - 5. validation error format (field-level errors for form submissions) - 6. error documentation template # Goal Error response schema, status code mapping, machine-readable code taxonomy, human-readable message guidelines, validation error format, and documentation template. # Constraints - Produce a complete, usable first draft in one response. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Error response schema, status code mapping, machine-readable code taxonomy, human-readable message guidelines, validation error format, and documentation template.
{{double-curly}} with your real context.When building a public API where inconsistent errors confuse developers and slow integrations.
Include a documentation URL in every error response — developers should be one click away from understanding why the request failed.
Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal
Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.
Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.
Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.