Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when implementing hooks that BLOCK invalid actions, creating quality gates for state transitions, or enforcing tested:true verification. Load when designing enforcement mechanisms. Uses exit code 2 to block, JSON permissionDecision:deny, or updatedInput modification. Rules are instructions; hooks are enforcement.
Recall past work from Claude Code history before starting new tasks. Use when: (1) starting work on a codebase, (2) asked about previous decisions, (3) need context about why code exists.
Database operations and ORM patterns for ERPNext/Frappe v14-v16
ReactのError Boundary実装とエラーハンドリング戦略を専門とするスキル。 堅牢なエラー処理とユーザーフレンドリーなフォールバックUIを実現する。 Anchors: • The Pragmatic Programmer / 適用: エラー処理の実践原則 / 目的: 品質維持と堅牢性向上 • React Error Boundary / 適用: クラッシュ回復UI実装 / 目的: 予期しない障害対応 Trigger: Use when implementing error boundaries, creating crash recovery UI, designing async error handling, or setting up error monitoring. error boundary, componentDidCatch, getDerivedStateFromError, fallback UI, error reporting
Express middleware and async error handling for video rendering operations. Use this when implementing try-catch blocks in server routes, defining custom error classes, handling S3 upload failures, or managing Remotion rendering errors. Emphasizes cleanup and structured error responses.
This skill should be used when the user asks about "Effect errors", "typed errors", "error handling", "Effect.catchAll", "Effect.catchTag", "Effect.mapError", "Effect.orElse", "error accumulation", "defects vs errors", "expected errors", "unexpected errors", "sandboxing", "retrying", "timeout", "Effect.cause", "TaggedError", "Schema.TaggedError", or needs to understand how Effect handles failures in the error channel.
Modern ESM import/export patterns. Use when writing or reviewing module structure.
Update spec files to match shipped implementation. Records sync notes in the increment and finishes it when complete.