Analyze ERP system integration for construction data flows. Map and optimize data flows between ERP modules
Crea scripts de migració per a mòduls OpenERP quan es modifiquen models o fitxers XML. Automatitza: generar estructura, plantilla, executar migració.
AI-native ERP system. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial…
ERPNext integration. Manage Companies. Use when the user wants to interact with ERPNext data.
Complete guide for ERPNext/Frappe API integrations (v14/v15/v16) including REST API, RPC API, authentication, webhooks, and rate limiting.
Intelligent agent for interpreting vague ERPNext development requests and producing concrete technical specifications.
Error handling patterns for ERPNext/Frappe API development (v14/v15/v16). Covers whitelisted method errors, REST API errors, client-side handling, external integrations, and…
Error handling patterns for ERPNext Document Controllers. Use when implementing try/except, validation errors, permission errors, and transaction management.
Error handling patterns for ERPNext/Frappe database operations. Use when handling DoesNotExistError, DuplicateEntryError, transaction failures, and query errors.
Error handling patterns for ERPNext/Frappe permissions and access control. Use when handling PermissionError, has_permission failures, role issues, and document access problems.
Implementation workflows and decision trees for ERPNext Client Scripts. Use when determining HOW to implement client-side features: form validations, dynamic UI, server…
Implementation workflows and decision trees for Frappe Document Controllers. Use when determining HOW to implement server-side DocType logic: lifecycle hooks, validation patterns,…
Implementation workflows and decision trees for Frappe hooks.py configuration. Use when determining HOW to implement doc_events, scheduler_events, override hooks, permission…
Implementation workflows and decision trees for Jinja templates in ERPNext/Frappe. Use when determining HOW to implement Print Formats, Email Templates, Portal Pages, or custom…
Implementation workflows for Frappe scheduled tasks and background jobs (v14/v15/v16). Covers hooks.py scheduler_events, frappe.enqueue, queue selection, job deduplication, and…
Implementation workflows and decision trees for ERPNext Server Scripts. Use when determining HOW to implement server-side features: document validation, automated calculations,…
Implementation workflows and decision trees for Frappe Whitelisted Methods (REST APIs). Use when determining HOW to implement API endpoints: public vs authenticated, permission…
Complete guide for Frappe/ERPNext permission system - roles, user permissions, perm levels, data masking, and permission hooks
Deterministic syntax for building Frappe custom apps including app structure, pyproject.toml, modules, patches and fixtures
Deterministic syntax for Frappe hooks.py configuration. Use when Claude needs to configure app events, scheduler tasks, document events, fixtures, boot session, jenv…
Deterministic Jinja template syntax for ERPNext/Frappe Print Formats, Email Templates, and Portal Pages
Scheduler and background jobs syntax for Frappe/ERPNext v14/v15/v16. Use for scheduler_events in hooks.py, frappe.enqueue() for async jobs, queue configuration, job deduplication,…
Help the user systematically identify and categorize failure modes in an LLM pipeline by reading traces.
Use when designing or reviewing React error boundaries: what an error boundary catches (rendering errors, lifecycle errors, constructor errors) and what it does not (event handler…
Create error boundaries, error handling, and fallback UIs for React applications. Use when implementing error handling, creating fallback components, or setting up error reporting.
Design resilient React error handling with Error Boundaries, Sentry integration, recovery UI, retry patterns, and graceful degradation.
ソフトウェアにおける非正常状態（Error, Defect, Fault, Failure）の分類と定義を提供する。 JIS規格・JSTQB・Bertrand Meyer等の複数の標準に基づき、各概念の違いを明確化し、 適切なエラー設計・障害対策の判断を支援する。エラー設計、障害分析、コードレビュー、…
Classify errors as FATAL, TRANSIENT, or UNKNOWN and transform raw stack traces into actionable agent instructions.
設計一致的錯誤碼，遵循 PREFIX_CATEGORY_NUMBER 格式。 使用時機：定義錯誤碼、建立錯誤處理、設計 API。 關鍵字：error code, error handling, error format, API errors, 錯誤碼, 錯誤處理。 — from AsiaOstrich/universal-dev-standards
Expert error coordinator specializing in distributed error handling, failure recovery, and system resilience.
Expert in making multi-agent systems resilient. Specializes in detecting loops, hallucinations, and failures, and implementing self-healing workflows.
Analyzes errors, searches past solutions in memory, provides immediate fixes with code examples, and saves solutions for future reference.
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes.
Advanced error analysis and pattern detection specialist for identifying, analyzing, and preventing software errors
You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions.
Proactively reviews error handling patterns and suggests improvements using Result types, proper error propagation, and idiomatic patterns.
Generate error handling middleware for any framework. Use when setting up API error handling.
Error Handler Middleware - Auto-activating skill for Backend Development. Triggers on: error handler middleware, error handler middleware Part of the Backend Development skill…
Use when implementing structured error handling in backend or frontend code. Triggers for: try-catch patterns, custom exception classes, global error handlers, error logging,…
Enforce proper error handling patterns. Use when writing async code, API calls, or user-facing features.
Production-ready API error handling for Next.js with standardized error codes, request tracking, user-friendly messages, and automatic error wrapping.
Audits Go code for error handling best practices - proper wrapping with %w, preserved context, meaningful messages, no error swallowing.
Find and fix unsafe error handling in Leavn - try! force unwraps, empty catch blocks, silent try? failures
Evaluates if error handling is sufficient for new code - checks try-catch coverage, logging, user messages, retry logic. Focuses on external calls and user-facing code.
Use when designing or implementing a cross-cutting Apex error handling framework: custom exception hierarchies, rollback-safe logging via Platform Events, BatchApexErrorEvent…
Auto-invoke when reviewing try/catch blocks, API error responses, async operations, or user feedback patterns. Enforces graceful degradation and meaningful error messages.
Verify errors are handled gracefully with meaningful user feedback. Issues result in WARNINGS.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications.
Design error states and recovery workflows that guide users to resolution. Learn context-aware error messages, graceful degradation, and recovery patterns.
Review test cases for OAuth/OIDC error handling. Covers authorization endpoint errors, token endpoint errors, error response formats, HTTP status codes, and all error codes per…
**AUTO-TRIGGER:** Invoked by yolo1 skill after every commit to analyze session errors.
Error Mapping Helper - Auto-activating skill for API Integration. Triggers on: error mapping helper, error mapping helper Part of the API Integration skill category.
Use when: making a mistake, breaking build/tests, realizing wrong approach, misunderstanding requirements, using wrong patterns, forgetting conventions, receiving correction from…
Explain compiler/runtime errors in plain language. Use when a junior developer needs help understanding an error message.
Cross-proxy/process error check with aggregation, dedup, periodic monitoring — not bash grep -r error / tail -f / journalctl -f / curl probes.
Create custom 404 and 500 error pages with brand styling. Use at project end before release. Triggers on "404", "error pages", "not found", "500 error".
Error handling patterns: classification, recovery, logging, graceful degradation, resilience.
Use when an operation fails, an error occurs, or a warning needs to be communicated to the user