71건 · 관련도순
Expert at building resilient applications through proper error handling. Covers Result types, error boundaries, try-catch patterns, typed errors, and graceful degradation. Use when "error handling, try catch, error boundary, Result type, exception, error-handling, typescript, react, resilience" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply the fail-early (fail-fast) pattern to detect and report errors at the earliest possible point. Covers input validation with guard clauses, meaningful error messages, assertion functions, and anti-patterns that silently swallow failures. Primary examples in R with general/polyglot guidance. Use when writing functions that accept external input, adding input validation before CRAN submission, refactoring code that silently produces wrong results, reviewing PRs for error-handling quality, or hardening internal APIs against invalid arguments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design Invocable Apex actions that return deterministic, agent-friendly errors instead of surfacing raw exceptions to the LLM. NOT for authoring the action itself — @InvocableMethod schema, labels, security context — use agentforce/custom-agent-actions-apex. NOT for the Apex tests that force each error branch — use agentforce/agent-action-unit-tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enforces error handling standards: silent error prohibition, custom error class hierarchy (AppError base with category never-fallback / transient / permanent, cause preservation, ValidationError / UnauthorizedError / UpstreamError etc. — canonical definitions in ERRORS.md), external-boundary normalization (normalizeExternalError), Result pattern (Result.ok/Result.fail), proper try-catch with error type checking, structured error logging with a single Logger contract, fallback prohibition categories (isNeverFallback), and HTTP status code mapping. Use when implementing error handling, reviewing catch blocks, or designing error responses.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When designing how a system recovers from and reports failures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and review error handling in TypeScript, Python, and Go applications. Use structured error types, controlled retries, API error responses, and readable failure messages to make failures visible and separate user guidance from developer diagnostics.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review JavaScript error handling in source code and browser behavior. Find unhandled asynchronous failures, improve logs with useful context, and add React Error Boundaries, components that handle rendering errors, so failures are handled explicitly and are easier to investigate.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Implement Python error handling with early input checks, appropriate exception types, and clear messages. Handle individual failures in batch jobs, preserve error context for debugging, and use Pydantic models to validate structured input.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design application and API behavior when operations fail. Choose between exceptions and Result types, which explicitly represent success or failure, and improve retries, error messages, logging, and resource cleanup so failures are easier to handle and investigate.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review DAX formulas, the expressions used for calculations in Power BI, and propose clearer, more maintainable alternatives. Identify repeated calculations, costly filtering, and error-handling issues, then explain changes and recommend ways to test them.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Add error handling to n8n workflows with connected error outputs, retries, and failure notifications. Return HTTP status codes that explain what went wrong, distinguish invalid requests from service failures, and keep internal error details out of public responses.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Diagnose iii invocation failures using error codes across Node, Python, Rust, and browser workers. Distinguish permission denials, timeouts, and handler failures, then choose appropriate exception handling and decide whether retrying is suitable.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guides developers in handling API failures consistently from backend responses to frontend messages. It covers ordinary and streaming requests, translated error codes, retry and authentication handling, request identifiers, and removing credentials from server logs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error branches/outputs, retries, retryOnFail, Respond to Webhook status codes, 4xx/5xx, Error Trigger, or "my workflow fails silently". Covers per-node error outputs and wiring, retry/self-healing, error-trigger workflows, and 4xx/5xx response shapes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Golang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from samber/cc-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (performance vs benchmark vs troubleshooting, samber/lo vs mo vs ro, DI cluster, safety vs security), and configures the project's agent-config file (CLAUDE.md, AGENTS.md, GEMINI.md, Cursor rules, or Copilot instructions) to force-trigger skills in a project (/golang-how-to configure).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Idiomatic Golang design patterns — functional options, constructor APIs, `init()` and global-state avoidance, enums, panic vs error decisions, resource management and lifecycle, graceful shutdown, timeouts and retries, streaming and iterators, and architecture styles (clean, hexagonal, DDD, flat). Apply when choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go pattern fits a specific problem. Not for wiring a DI container or comparing DI libraries (→ See `samber/cc-skills-golang@golang-dependency-injection` skill), nor for error wrapping, `errors.Is`/`As`, or logging mechanics (→ See `samber/cc-skills-golang@golang-error-handling` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See `samber/cc-skills-golang@golang-samber-oops` skill; for slog handler ecosystem → See `samber/cc-skills-golang@golang-samber-slog` skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Monadic types for Golang using samber/mo — Option, Result, Either, Future, IO, Task, and State types for type-safe nullable values, error handling, and functional composition with pipeline sub-packages. Apply when using or adopting samber/mo, when the codebase imports `github.com/samber/mo`, or when considering functional programming patterns as a safety design for Golang. Not for nil-safety and zero-value design without this library (→ See `samber/cc-skills-golang@golang-safety` skill), nor for native error wrapping with fmt.Errorf, errors.Is and errors.As (→ See `samber/cc-skills-golang@golang-error-handling` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design confirmations, status updates, and notifications that tell users an action registered. Use when the system must acknowledge success or change. For waiting states use `loading-states`; for failures use `error-handling-ux`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a form end to end — field order, grouping, validation, and completion. Use when the artifact is a form. For product-wide error strategy use `error-handling-ux`; for first-run signup use `onboarding-design`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design error prevention, detection, and recovery across a product — message content, placement, and escape routes. Use when errors span multiple flows. For validation inside a single form, use `form-design`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.