Deploys to archivist@194.163.189.144 VPS and iteratively debugs until successful. Use when deploying to VPS, debugging deployment failures, investigating container issues,…
Score 70/100
Guide PMs through debugging AI-generated code: how to read error messages, form effective debugging prompts, isolate issues, and decide when to fix forward vs start over.
Score 70/100
Debug E2E tests by taking screenshots at key points to visually inspect application state.
Score 70/100
Debug crashes, segfaults, and memory errors using valgrind integration with nextest through pre-configured profiles
Score 70/100
Guides developers through scenario test debugging using Ruby debug gem step execution. Provides interactive debugging patterns and test helper context.
Score 70/100
Debug broken Zoom implementations quickly. Use when auth, webhooks, SDK joins, MCP transport, or real-time media workflows are failing and you need to isolate the layer before…
Score 70/100
Expert at advanced debugging and root cause analysis. Use when troubleshooting complex issues, finding root causes of bugs, investigating performance problems, or analyzing system…
Score 70/100
Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries…
Score 70/100
Use when an Agent2 agent returns errors, 500s, mock data unexpectedly, fails to start, or behaves incorrectly — systematic diagnosis for framework issues, config problems, Docker…
Score 70/100
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error.
Score 70/100
Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and…
Score 70/100
Use when troubleshooting Atmos configuration, deployment errors, or unexpected behavior. Covers debug logging, describing stacks/components, interpreting errors, and common issues…
Score 70/100
Hidden automatic debugging when something breaks - user sees simple question or "fixing..." not stack traces or technical errors
Score 70/100
Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.
Score 70/100
Troubleshooting guide for Claude Code issues. Use when Claude behaves unexpectedly, tools fail, sessions hang, or you need to diagnose problems.
Score 70/100
A reasoning pattern for diagnosing and fixing bugs that span multiple abstraction layers in complex systems.
Score 70/100
Debugs and fixes dbt errors systematically. Use when working with dbt errors for: (1) Task mentions "fix", "error", "broken", "failing", "debug", "wrong", or "not working" (2)…
Score 70/100
Debugs Docker build failures, container runtime errors, platform architecture issues (ARM64/AMD64/WSL2), AWS ECR/ECS pull failures, and optimizes Docker workflows.
Score 70/100
Expert in systematic debugging, root cause analysis, profiling, and performance troubleshooting. Use when stuck on bugs, investigating errors, or optimizing performance.
Score 70/100
Debug iOS apps and profile performance using LLDB, Memory Graph Debugger, and Instruments. Use when diagnosing crashes, memory leaks, retain cycles, main thread hangs, slow…
Score 70/100
Systematically debug issues with reproduction steps, error analysis, hypothesis testing, and root cause fixes.
Score 70/100
Use when investigating Kubernetes pod failures, crashes, resource issues, or service degradation. Provides systematic investigation methodology for incident triage, root cause…
Score 70/100
Systematic debugging methodologies for finding and resolving complex bugs. Use PROACTIVELY when encountering difficult bugs, mysterious failures, or issues that resist simple…
Score 70/100
Activate systematic debugging mode. Expert in root cause analysis and scientific debugging methodology.
Score 70/100
Evidence-driven investigation for network, streaming, and protocol-layer bugs. Use when debugging connection resets (ECONNRESET, HTTP/2 RST_STREAM, INTERNAL_ERROR), SSE or…
Score 70/100
Converts ORM calls to raw SQL and analyzes query performance. Detects N+1 queries, missing indexes, and other anti-patterns.
Score 70/100
Root cause analysis frameworks including log-first investigation, git bisect correlation, and pattern-based diagnosis with confidence scoring.
Score 70/100
Use when Konflux pipelines fail, are stuck, timeout, or show errors like ImagePullBackOff. Covers PipelineRun failures, TaskRun issues (Pending, Failed, stuck Running), build…
Score 70/100
Comprehensive protocol for validating root causes of software issues. Use when you need to systematically debug a complex bug, flaky test, or unknown system behavior by forming…
Score 70/100
Use PROACTIVELY when debugging React Native apps. Reads console logs and executes JavaScript in running apps via Metro bundler.
Score 70/100
Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.
Score 70/100
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack.
Score 70/100
Apply systematic root cause analysis and debugging methodologies to diagnose and fix bugs, test failures, and unexpected behavior.
Score 70/100
Debugging workflows for Python (pdb, debugpy), Go (delve), Rust (lldb), and Node.js, including container debugging (kubectl debug, ephemeral containers) and production-safe…
Score 70/100
Use when the user reports a bug they can't reproduce, asks where to start debugging, or mentions a Heisenbug / production-only failure.
Score 70/100
Comprehensive debugging strategies, tools, and techniques for efficiently identifying and fixing bugs across different environments.
Score 70/100
Use when seeing WebSocket errors like "Invalid frame header", "RSV1 must be clear", or "WS_ERR_UNEXPECTED_RSV_1" - covers multiple WebSocketServer conflicts, compression issues,…
Score 70/100
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
Score 70/100
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to…
Score 70/100
디버깅 실패 시 자동 트리거되는 체계적 문제 해결 워크플로우. DEBUGGING_STRATEGY.md 기반 Phase 0-3 디버깅 프로세스 자동화.
Score 70/100
Guide for debugging GitHub Agentic Workflows - analyzing logs, auditing runs, and troubleshooting issues
Score 70/100
Building decay and upkeep systems for survival games. Use when implementing timer-based decay, Tool Cupboard patterns (Rust-style protection radius), resource upkeep costs, or…
Score 70/100
Expert on Decibel on-chain perpetual futures trading platform on Aptos. Covers trading engine, orderbook, TypeScript SDK, REST APIs, WebSocket streams, market data, position…
Score 70/100
Record or list architectural decisions and active migrations in `.claude/rules/architecture.md`. 管理架構決策與遷移記錄。 Use when: record a decision, add a decision, add a migration,…
Score 70/100
Systematic framework for rigorous, situationally-grounded decision analysis. Use when evaluating options with competing benefits where stated values may diverge from actual…
Score 70/100
Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.
Score 70/100
Decision-making methodologies, scoring frameworks, and planning strategies for Group 2 agents in four-tier architecture
Score 70/100
Use when the user asks to design or refactor a declaration contract, such as a function signature, type shape, schema, or generic parameter list, and wants guidance on grouping,…
Score 70/100
Identify misplaced files and organize project structure following open-source best practices, while delegating refactoring to specialized skills
Score 70/100
Decode JWTs, inspect claims, and verify or sign tokens with local keys during auth debugging and test setup.
Score 70/100
Architectural code analysis for Python design quality. Evaluates simplicity (Rich Hickey), functional core/imperative shell (Gary Bernhardt), and coupling (Constantine & Yourdon).
Score 70/100
Analyze large source files and produce decomposition plans, optionally executing refactoring with import updates and test verification
Score 70/100
Deconstructs complex problems using the 'Polymath Investor' framework with a 5-step cognitive chain (First Principles → Modular Isolation → Pareto Filtering → Cross-Domain Mapping…
Score 70/100
Use after writing-plans to decompose monolithic plan into individual task files and identify tasks that can run in parallel (up to 2 subagents simultaneously)
Score 70/100
Use when dealing with complex systems that need simplification, identifying bottlenecks or critical failure points, redesigning architecture or processes for better performance,…
Score 70/100
Use when building dedicated servers — headless export, server architecture, lobby management, and deployment
Score 70/100
Advanced problem-solving skill using sequential thinking. Use for complex architectural decisions, debugging hard problems, or planning.
Score 70/100
Advanced problem-solving skill using sequential thinking. Use for complex architectural decisions, debugging hard problems, or planning.
Score 70/100
Multi-agent investigation for stubborn bugs. Use when: going in circles debugging, need to investigate browser/API interactions, complex bugs resisting normal debugging, or when…
Score 70/100
Deep technical documentation generation workflow using zen mcp's clink and docgen tools. First uses clink to launch gemini CLI in WSL for code analysis, then uses docgen for…
Score 70/100