---

name: error-handling-patterns version: 1.0.0 type: knowledge description: Standardized error handling patterns including exception hierarchy, error message formatting, security audit logging, and graceful degradation. Use when raising exceptions, handling errors, or implementing validation. keywords: error, exception, validation, raise, try, catch, except, audit, logging, graceful degradation, error handling auto_activate: true allowed-tools: [Read]

Error Handling Patterns Skill

Standardized error handling patterns for all libraries to ensure consistent error reporting, security audit logging, and graceful degradation across the autonomous development system.

When This Skill Activates

• Raising custom exceptions
• Handling errors and validation failures
• Implementing security audit logging
• Designing graceful degradation
• Formatting error messages
• Creating exception hierarchies
• Keywords: "error", "exception", "validation", "raise", "try", "catch", "audit"

---

Core Concepts

Overview

This skill provides comprehensive guidance on error handling patterns. For detailed patterns and implementation examples, see the documentation files in docs/.

Key Topics:

• Detailed methodologies and best practices
• Implementation patterns and examples
• Common pitfalls and anti-patterns
• Cross-references to related skills

See: Documentation files in docs/ directory for complete details

---

Quick Reference

---

Progressive Disclosure

This skill uses progressive disclosure to prevent context bloat:

• Index (this file): High-level concepts and quick reference (<500 lines)
• Detailed docs: docs/*.md files with implementation details (loaded on-demand)

Available Documentation:

• docs/detailed-guide-1.md - Detailed implementation guide
• docs/detailed-guide-2.md - Detailed implementation guide
• docs/detailed-guide-3.md - Detailed implementation guide
• docs/detailed-guide-4.md - Detailed implementation guide

---

Cross-References

Related Skills:

• See PROJECT.md for complete skill dependencies

Related Tools:

• See documentation files for tool-specific guidance

---

Key Takeaways

1. Research existing patterns before implementing
2. Follow established best practices
3. Refer to detailed documentation for implementation specifics
4. Cross-reference related skills for comprehensive understanding