- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
environment-config
by dadbodgeoff
Centralized environment variable management with validation. Fail fast at startup if config is invalid. Supports multi-environment setups (dev/staging/prod) with type-safe access.
ai-generation-client
by dadbodgeoff
External AI API integration with retry logic, rate limiting, content safety detection, and multi-turn conversation support for image generation.
zod-4
by Gentleman-Programming
Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.
ai-sdk-5
by Gentleman-Programming
Vercel AI SDK 5 patterns. Trigger: When building AI chat features - breaking changes from v4.
exception-taxonomy
by dadbodgeoff
Hierarchical exception system with HTTP status codes, machine-readable error codes, and structured responses for consistent API error handling across all endpoints.
batch-processing
by dadbodgeoff
Collect-then-batch pattern for database operations achieving 30-40% throughput improvement. Includes graceful fallback to sequential processing when batch operations fail.
anomaly-detection
by dadbodgeoff
Rule-based anomaly detection for production systems with configurable thresholds, cooldown periods to prevent alert storms, and error pattern tracking for repeated failures.
logging-observability
by dadbodgeoff
Structured JSON logging with correlation IDs, request context propagation across async boundaries, performance timing decorators, and worker metrics collection.
leader-election
by dadbodgeoff
Elect a single leader among multiple instances. Only one instance runs cron jobs or processes queues. Automatic failover when leader dies.
job-state-machine
by dadbodgeoff
Async job processing with validated state transitions, progress tracking, and asset linking. Ensure jobs always reach terminal states with proper error handling.
graceful-degradation
by dadbodgeoff
Build resilient systems that degrade gracefully under failure. Implement fallbacks, feature flags, and partial responses when dependencies fail.
dead-letter-queue
by dadbodgeoff
Store failed jobs for replay or manual inspection. Track failure patterns, enable manual intervention, and prevent data loss from processing errors.
apollo-client
by apollographql
Guide for building React applications with Apollo Client 4.x. Use this skill when: (1) setting up Apollo Client in a React project, (2) writing GraphQL queries or mutations with hooks, (3) configuring caching or cache policies, (4) managing local state with reactive variables, (5) troubleshooting Apollo Client errors or performance issues.
electron
by Gentleman-Programming
Electron patterns for building cross-platform desktop applications. Trigger: When building desktop apps, working with Electron main/renderer processes, IPC communication, or native integrations.
sapui5-linter
by secondsky
Use this skill when working with the UI5 Linter (@ui5/linter) for static code analysis of SAPUI5/OpenUI5 applications and libraries. This skill should be used when: (1) Setting up UI5 Linter in a project for the first time, (2) Configuring linting rules and ignore patterns for UI5 codebases, (3) Running the linter to detect deprecated APIs, global variable usage, CSP violations, or manifest issues, (4) Using autofix to automatically correct deprecated API usage, global references, event handlers, and manifest properties, (5) Troubleshooting linting errors or warnings in UI5 code, (6) Integrating UI5 Linter into CI/CD pipelines or pre-commit hooks, (7) Preparing UI5 projects for migration to UI5 2.x by identifying compatibility issues, (8) Understanding and resolving specific linting rules like no-deprecated-api, no-globals, async-component-flags, or manifest validation rules. The skill covers all 19 linting rules, comprehensive autofix capabilities and limitations, CLI options, configuration patterns, performance optimization, and integration with development workflows. Keywords: SAPUI5, OpenUI5, UI5 Linter, @ui5/linter, static analysis, deprecated APIs, global variables, CSP, manifest.json, ui5.yaml, ESLint, pre-commit hooks, GitHub Actions, CI/CD, Node.js, TypeScript, XML, JSON, HTML, YAML, OData v2/v4, async, event handlers, jQuery, autofix, performance optimization, 19 linting rules, no-deprecated-api, no-globals, no-async-component-flags, manifest-v2, UI5 2.x migration
ship-safe
by asamassekou10
Run a full security audit on this project — 12 agents scan for secrets, injections, auth bypass, SSRF, supply chain attacks, misconfigs, and more. Use when the user wants a security audit, vulnerability scan, or asks if their code is safe to ship.
templ-http
by Xe
Integrate templ components with Go HTTP server using net/http. Use when connecting templ to web server, creating HTTP handlers, mentions 'templ server', 'HTTP routes', or 'serve templ components'.
templ-syntax
by Xe
Learn and write templ component syntax including expressions, conditionals, loops, and Go integration. Use when writing .templ files, learning templ syntax, or mentions 'templ component', 'templ expressions', or '.templ file syntax'.
code-pattern-checker
by camoa
Use before committing code - validates Drupal coding standards, SOLID/DRY principles, security practices, and CSS standards
paper-test
by camoa
Use when testing code through mental execution - trace code line-by-line with concrete input values to find bugs, logic errors, missing code, edge cases, and contract violations before deployment
fix
by tkersey
Review+fix protocol with safety guardrails (unsoundness, invariants, footguns, incidental complexity). Use when prompts say "$fix this PR", "fix current branch", "fix this diff", "repair CI red", or "apply a minimal patch", and when crash/corruption/invariant-break issues need correction with a validation signal.
invariant-ace
by tkersey
"Turn 'should never happen' into 'cannot happen' by defining owned inductive invariants and enforcing them at parse/construct/API/DB/lock/txn boundaries with a verification signal. Use when prompts mention invariants, impossible states, validation sprawl, cache/index drift, idempotency/versioning, retries/duplicates/out-of-order events, race/linearization bugs, loop correctness, or hardening another workflow (for example $fix) with invariant checks first."
Set up an investigation
by talmolab
A deep learning framework for multi-animal pose tracking.
HTTP Client
by HoangNguyen0403
Best practices for HttpClient, Interceptors, and API interactions.