[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D3HRNF4KB9FD6B8K24BBJF":3,"skill-same:01M7D3HRNF4KB9FD6B8K24BBJF":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7D3HRNF4KB9FD6B8K24BBJF","error-handling",null,"Error taxonomy, recoverable\u002Ffatal, retries, contextual errors, user-facing vs internal, logging, propagation, panic\u002Fexception boundaries","poppyTM\u002Faipo-lang","poppyTM","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F339400917?v=4","01M78F6YNKFR5S5JQR27X9F09Z","Poppy Team","01M7D3H3PCFF0AZSRPP5GTS76P",0,"MIT","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ferror-handling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: error-handling\ndescription: Error taxonomy, recoverable\u002Ffatal, retries, contextual errors, user-facing vs internal, logging, propagation, panic\u002Fexception boundaries\n---\n# Error Handling Strategy\n\n## 1. Error Taxonomy\nEstablish a clear taxonomy of errors within the domain. Distinguish between expected domain errors (e.g., 'Insufficient Funds') and unexpected technical faults (e.g., 'Database Connection Lost'). Use strong types for domain errors to enable programmatic handling.\n\n## 2. Recoverable vs. Fatal Errors\nDefine strict boundaries between recoverable and fatal errors. Recoverable errors should be handled gracefully, often returning an error result to the caller. Fatal errors (e.g., out of memory, corrupted internal state) should trigger an immediate fail-fast mechanism (panic\u002Fcrash) to prevent cascading failures.\n\n## 3. Retry Strategies\nImplement intelligent retry mechanisms for transient technical faults (e.g., network timeouts). Use exponential backoff with jitter to avoid thundering herd problems. Ensure operations are idempotent before retrying. Define a maximum retry limit to prevent infinite loops.\n\n## 4. Contextual Errors\nErrors must carry sufficient context for debugging. Wrap low-level errors with high-level context as they propagate up the stack. Include relevant IDs, state information, and the attempted operation. Never return a bare 'Not Found' without specifying *what* was not found.\n\n## 5. User-Facing vs. Internal Errors\nStrictly separate internal error representations from user-facing error messages. Internal errors contain technical details, stack traces, and sensitive data. User-facing errors must be safe, sanitized, localized, and actionable, never leaking system internals.\n\n## 6. Structured Error Logging\nLog errors systematically using structured formats (e.g., JSON). Include error severity, context fields, correlation IDs, and stack traces. Ensure error logs are easily searchable and aggregate-able in observability platforms. Alert on unexpected spikes in error rates.\n\n## 7. Error Propagation\nEstablish consistent rules for error propagation. Choose either explicit error returns (e.g., Go, Rust) or structured exception handling (e.g., Java, Python). Avoid mixing paradigms. Ensure errors are propagated to a layer capable of making a meaningful decision about them.\n\n## 8. Panic and Exception Boundaries\nDefine clear boundaries where exceptions must be caught and converted to standard responses (e.g., HTTP middleware catching panics to return 500s). Prevent internal exceptions from leaking across process boundaries or API endpoints.\n\n## 9. Circuit Breakers\nImplement circuit breaker patterns to prevent repeated failures from overwhelming downstream services. When a service fails repeatedly, open the circuit to fail fast locally. Periodically probe the service and close the circuit only when health is restored.\n\n## 10. Error Rate Monitoring\nContinuously monitor error rates as a key service level indicator (SLI). Define acceptable error budgets. Automatically trigger alerts or rollbacks if error budgets are exhausted. Differentiate between baseline background noise and anomalous error spikes.\n\n","# Error Handling Strategy\n\n## 1. Error Taxonomy\nEstablish a clear taxonomy of errors within the domain. Distinguish between expected domain errors (e.g., 'Insufficient Funds') and unexpected technical faults (e.g., 'Database Connection Lost'). Use strong types for domain errors to enable programmatic handling.\n\n## 2. Recoverable vs. Fatal Errors\nDefine strict boundaries between recoverable and fatal errors. Recoverable errors should be handled gracefully, often returning an error result to the caller. Fatal errors (e.g., out of memory, corrupted internal state) should trigger an immediate fail-fast mechanism (panic\u002Fcrash) to prevent cascading failures.\n\n## 3. Retry Strategies\nImplement intelligent retry mechanisms for transient technical faults (e.g., network timeouts). Use exponential backoff with jitter to avoid thundering herd problems. Ensure operations are idempotent before retrying. Define a maximum retry limit to prevent infinite loops.\n\n## 4. Contextual Errors\nErrors must carry sufficient context for debugging. Wrap low-level errors with high-level context as they propagate up the stack. Include relevant IDs, state information, and the attempted operation. Never return a bare 'Not Found' without specifying *what* was not found.\n\n## 5. User-Facing vs. Internal Errors\nStrictly separate internal error representations from user-facing error messages. Internal errors contain technical details, stack traces, and sensitive data. User-facing errors must be safe, sanitized, localized, and actionable, never leaking system internals.\n\n## 6. Structured Error Logging\nLog errors systematically using structured formats (e.g., JSON). Include error severity, context fields, correlation IDs, and stack traces. Ensure error logs are easily searchable and aggregate-able in observability platforms. Alert on unexpected spikes in error rates.\n\n## 7. Error Propagation\nEstablish consistent rules for error propagation. Choose either explicit error returns (e.g., Go, Rust) or structured exception handling (e.g., Java, Python). Avoid mixing paradigms. Ensure errors are propagated to a layer capable of making a meaningful decision about them.\n\n## 8. Panic and Exception Boundaries\nDefine clear boundaries where exceptions must be caught and converted to standard responses (e.g., HTTP middleware catching panics to return 500s). Prevent internal exceptions from leaking across process boundaries or API endpoints.\n\n## 9. Circuit Breakers\nImplement circuit breaker patterns to prevent repeated failures from overwhelming downstream services. When a service fails repeatedly, open the circuit to fail fast locally. Periodically probe the service and close the circuit only when health is restored.\n\n## 10. Error Rate Monitoring\nContinuously monitor error rates as a key service level indicator (SLI). Define acceptable error budgets. Automatically trigger alerts or rollbacks if error budgets are exhausted. Differentiate between baseline background noise and anomalous error spikes.\n\n",{"name":5,"description":7},"main","b2b8635798b0fab7a7c037608a616985cc1da742",".agents\u002Fskills\u002Ferror-handling","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang","https:\u002F\u002Fwww.poppy.lat\u002Faipo\u002Fdocs\u002F","https:\u002F\u002Fgithub.com\u002FpoppyTM","https:\u002F\u002Fpoppy.lat","Construímos linguagens de programação e ferramentas para quem lê código com o mesmo cuidado com que escreve.","2026-11-02 17:30:11",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add poppyTM\u002Faipo-lang --skill error-handling",{"tool":39,"command":40},"bunx","bunx skills add poppyTM\u002Faipo-lang --skill error-handling",{"tool":42,"command":43},"pnpm","pnpm dlx skills add poppyTM\u002Faipo-lang --skill error-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ferror-handling\u002FSKILL.md",true,[47,53,57,61,65,71],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"checks\u002Ferror-taxonomy-checklist.md","REFERENCE","参考文档",310,"https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ferror-handling\u002Fchecks\u002Ferror-taxonomy-checklist.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"examples\u002Fresult_pattern_example.md",1405,"https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ferror-handling\u002Fexamples\u002Fresult_pattern_example.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"manifest.json",1190,"https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ferror-handling\u002Fmanifest.json",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Ferror-handling-guidelines.md",1335,"https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ferror-handling\u002Freferences\u002Ferror-handling-guidelines.md",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fcheck_bare_excepts.sh","SCRIPT","脚本",62,"https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ferror-handling\u002Fscripts\u002Fcheck_bare_excepts.sh",{"path":72,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":73,"sourceHtmlUrl":74},"templates\u002Ferror-handling-template.md",805,"https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ferror-handling\u002Ftemplates\u002Ferror-handling-template.md",[76,83,89,95,101,108],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D3JYBW82B2Q8XH75TKWBT7","lang-aipo","Aipo V1 canonical engineering, ADR-001 syntax conformance, braces blocks, Tipo:nome method bindings, structural interfaces, transactional failure handling, and anti-hallucination guardrails for LLMs.","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002Fskills\u002Flang-aipo\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7D3JWY6HS47F1TRVX14SZ5F","goal-management","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fgoal-management\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7D3JV6D1SPD1WNS14634CGV","evidence-collection","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fevidence-collection\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7D3JSSDVRNC7W42KAFA65MH","code-review","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fcode-review\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7D3JPEZSE144W9T31QKB9XP","testing-quality","Testing pyramid, deterministic tests, regression tests, behavior assertions, test isolation, flaky detection, representative fixtures","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Ftesting-quality\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7D3JJES8J9K0HXG45H27BRF","cognitive-clarity","Unambiguous communication, single-decision focus, visual structuring, and rationale-first explanation tailored for neurodivergent collaboration","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Fcognitive-clarity\u002FSKILL.md",[],[]]