OpenParable
Skip to content
← Back to skills

Error Code Catalog

Documents
error-code-catalog

Error Code Catalog is an Agent Skill for documents published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Manage and document SDK error codes and messages

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/sdk-platform-development/skills/error-code-catalog/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/error-code-catalog, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Error Code Catalog Skill

Overview

This skill manages a comprehensive catalog of SDK error codes, messages, and documentation, ensuring consistent, helpful error handling across all SDK operations.

Capabilities

  • Define error code taxonomy with categories
  • Generate error documentation automatically
  • Validate error message quality and actionability
  • Support error localization (i18n)
  • Map HTTP status codes to SDK errors
  • Generate error handling code from catalog
  • Track error frequency and patterns
  • Create troubleshooting guides per error

Target Processes

  • Error Handling and Debugging Support
  • API Design Specification
  • API Documentation System

Integration Points

  • Error tracking systems (Sentry, Bugsnag)
  • i18n frameworks for localization
  • Documentation generators
  • SDK code generation
  • Analytics platforms

Input Requirements

  • Error categorization requirements
  • Message style guidelines
  • Localization requirements
  • HTTP mapping rules
  • Troubleshooting depth

Output Artifacts

  • Error code catalog (JSON/YAML)
  • Error documentation pages
  • SDK error classes/types
  • Localization resource files
  • Troubleshooting guides
  • Error mapping tables

Usage Example

skill:
  name: error-code-catalog
  context:
    catalogFile: ./errors/catalog.yaml
    errorFormat:
      codePrefix: "SDK"
      codeLength: 4
      pattern: "SDK-{category}-{number}"
    categories:
      - auth
      - validation
      - network
      - rate-limit
      - server
    localization:
      enabled: true
      locales: ["en", "es", "ja", "de"]
    includeRemediation: true

Best Practices

  1. Use meaningful error code prefixes
  2. Include remediation steps in all errors
  3. Categorize errors logically
  4. Keep error messages actionable
  5. Support localization from the start
  6. Link errors to documentation