Diagnose and fix common Haskell Bazel build errors, especially dependency visibility issues

Debug bugs and errors using intel-first approach with systematic root cause analysis. Use proactively when errors occur, tests fail, or unexpected behavior appears. MUST trace from symptom to root cause with CoD^Σ reasoning.

Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.

Language-specific debug logging patterns and best practices. Reference when adding instrumentation for Dart/Flutter, Kotlin/Android, Swift/iOS, or JavaScript/TypeScript applications.

>

Use renovate-dryrun to test Renovate configuration locally. Use this skill when debugging or validating renovate.json5 changes.

Document debugging sessions with hypothesis tracking and knowledge base

디버깅, 디버그, 버그, 에러, 오류, 버그 수정 - Specialized in identifying root causes of bugs, analyzing error logs, and providing robust fixes. Use this when the user reports an error, unexpected behavior, or needs performance troubleshooting.

Systematic debugging workflow with hypothesis testing

Debug and diagnose Thread mesh networks and OpenThread Border Routers. Use when troubleshooting Thread connectivity, analyzing Router Advertisements, testing IPv6 reachability to Thread devices, inspecting Thread Network Data, or diagnosing Border Router configuration issues.

Deploy to the production VPS (archivist@194.163.189.144) and iteratively debug failures until successful deployment.

Debug crashes, segfaults, and memory errors using valgrind integration with nextest through pre-configured profiles

Guides developers through scenario test debugging using Ruby debug gem step execution. Provides interactive debugging patterns and test helper context.

Systematic bug investigation and resolution workflow with root cause analysis.

Debugging specialist for errors, test failures, and unexpected

Expert at advanced debugging and root cause analysis. Use when troubleshooting complex issues, finding root causes of bugs, investigating performance problems, or analyzing system failures.

Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and verification protocols. Use when encountering bugs, test failures, unexpected behavior, performance issues, or before claiming work complete. Prevents random fixes, masks over symptoms, and false completion claims.

Part of the hidden validation layer. When code breaks during generation, fix it automatically without exposing technical details to user.

Comprehensive debugging guide for Capacitor applications. Covers WebView debugging, native debugging, crash analysis, network inspection, and common issues. Use this skill when users report bugs, crashes, or need help diagnosing issues.

A reasoning pattern for diagnosing and fixing bugs that span multiple abstraction layers in complex systems.

You are a data engineer debugging a failed Airflow DAG. Follow this systematic approach to identify the root cause and provide actionable remediation.

Debugs Docker build failures, container runtime errors, platform architecture issues (ARM64/AMD64/WSL2), AWS ECR/ECS pull failures, and optimizes Docker workflows. Use when encountering Docker build errors, container crashes, ECR authentication issues, ECS deployment problems, performance issues, networking failures, volume permission errors, or when working with multi-platform Docker images.

Expert in systematic debugging, root cause analysis, profiling, and performance troubleshooting. Use when stuck on bugs, investigating errors, or optimizing performance.

Systematically debug issues with reproduction steps, error analysis, hypothesis testing, and root cause fixes. Use when investigating bugs, analyzing production incidents, or troubleshooting unexpected behavior.

Sistematik debugging döngüsü - reproduce, isolate, hypothesize, fix.

Activate systematic debugging mode. Expert in root cause analysis and scientific debugging methodology. Use when troubleshooting bugs, investigating issues, or diagnosing unexpected behavior.

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 hypotheses and validating them with specific tasks.

Use PROACTIVELY when debugging React Native apps. Reads console logs and executes JavaScript in running apps via Metro bundler. Invoke for: app crashes, state inspection, API debugging, error investigation, or running diagnostic code. Requires Metro running (port 8081).

Apply systematic root cause analysis and debugging methodologies to diagnose and fix bugs, test failures, and unexpected behavior. Use when encountering production issues, investigating test failures, diagnosing performance problems, tracing error sources through call stacks, analyzing logs and stack traces, reproducing inconsistent bugs, debugging race conditions, investigating memory leaks, or applying scientific method to problem-solving before proposing fixes.

Comprehensive debugging strategies, tools, and techniques for efficiently identifying and fixing bugs across different environments.

Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing

**Automate first, ask questions never.** If you can write a test to verify behavior, do that instead of asking the user to manually check something.

Structured decision critic that systematically stress-tests reasoning before commitment surfacing hidden assumptions verifying claims and generating adversarial perspectives to improve decision quality.

Autonomous decision-making CLI for strategy development (project)

Decision-making methodologies, scoring frameworks, and planning strategies for Group 2 agents in four-tier architecture

Document major decisions made

Map and optimize decision moments across Awareness, Consideration, Conversion, and Retention, then attach specific assets, visuals, and automations to each stage. Use when designing funnels, campaigns, or retention systems.

Use when designing branching logic, eligibility rules, and fallback paths.

Load past architectural decisions. Use when making new decisions to ensure consistency.

Create, update, and translate Dify X Reveal.js slide decks in this repo. Use when asked to draft slides, extract outlines, or maintain bilingual CN/EN parity for the ctrip/paypal/pupu/milvus/aispeech/dentsply/oceanbase/legalai decks, including deck HTML (index.html/index_en.html) and legal workflow YAMLs.

Identify misplaced files and organize project structure following open-source best practices, while delegating refactoring to specialized skills

Decode BSV transaction hex into human-readable format.

Deconstructs complex problems using the 'Polymath Investor' framework with a 5-step cognitive chain (First Principles → Modular Isolation → Pareto Filtering → Cross-Domain Mapping → Dynamic Zooming). Use when analyzing systems, architectures, businesses, or learning challenges; when seeking high-leverage insights or 'Alpha'; when applying first principles thinking; or when needing cross-disciplinary perspectives to reveal blind spots. Transforms overwhelming complexity into actionable levers.

Use when you need to create an execution plan from a feature spec - handles worktree context, dispatches subagent for task decomposition, validates quality, analyzes dependencies, groups into phases, and commits the plan

Break down large tasks into smaller, actionable items. Use when planning sprints, estimating work, or creating implementation plans. Covers task breakdown strategies.

Comprehensive framework for deep analysis of articles, papers, and long-form content using 10+ thinking models (SCQA, 5W2H, critical thinking, inversion, mental models, first principles, systems thinking, six thinking hats). Use when users want to: (1) deeply understand complex articles/content, (2) analyze arguments and identify logical flaws, (3) extract actionable insights from reading materials, (4) create study notes or learning summaries, (5) compare multiple sources, (6) transform knowledge into practical applications, or (7) apply specific thinking frameworks. Triggered by phrases like 'analyze this article,' 'help me understand,' 'deep dive into,' 'extract insights from,' 'use [framework name],' or when users provide URLs/long-form content for analysis.

Three-pass critical reading framework for systematic document analysis. Supports tech blogs, retrospectives, technical documentation, personal writing, and academic papers. Primary focus on Third Pass critical analysis, context validation, and actionable reconstruction. Use when analyzing complex documents, performing critical reading, extracting actionable insights, or conducting deep analysis. Triggers include Third Pass, 비판적 분석, critique, 깊이 읽기, 심층 분석.

---name: deep-visual-proteomics-agent

Enter and manage Deep Work sessions in Agent Hive. Use this skill when starting a focused work session on a project, generating session context, following the handoff protocol, or managing your responsibilities as an agent during a work session.

Use when discussing or working with DeepEval (the python AI evaluation framework)