Skill UI

This specialized skill acts as an expert debugger, designed for deep root cause analysis of software errors, test failures, and unexpected behavior. It guides the user through systematic debugging processes, including capturing stack traces, isolating failure points, implementing minimal fixes, and providing comprehensive reports detailing the root cause, evidence, specific code patches, and prevention recommendations. Ideal for complex bug resolution and quality assurance.

This skill provides a structured methodology for tackling complex bugs, performance bottlenecks, and production incidents. It guides users through reproducing issues, forming hypotheses, performing controlled experiments, and narrowing down the scope using proven strategies and tools. Ideal for deep dive troubleshooting and root cause analysis in complex software systems.

A comprehensive, expert-level workflow for debugging complex software issues in production environments. This skill guides users through initial triage, advanced observability data collection (APM, distributed traces, logs), intelligent hypothesis generation, and full root cause analysis. Use it when dealing with intermittent failures, performance bottlenecks, or needing a complete fix and prevention plan.

Provides systematic error investigation for distributed systems, combining production incident review, observability tooling, and targeted debugging to find root causes and prevent future failures.

This skill is designed for advanced error detective work. It analyzes complex log streams, correlates stack traces across distributed systems, and detects anomalous error patterns. It helps identify root causes by correlating errors with system deployments and changes, providing actionable findings for immediate fixes and long-term prevention strategies.

This expert specializes in guiding systematic bug investigation, feature implementation, and collaborative development workflows using GitHub. It covers the entire lifecycle, from initial issue triage and root cause analysis to professional Pull Request creation. Use it to ensure fixes are thoroughly tested, proper branching is maintained, and modern CI/CD best practices are followed, transforming vague reports into production-ready code.

This skill teaches users to apply the scientific method to software debugging. Instead of random changes, it guides the process through five steps: Observation, Hypothesizing, Prediction, Testing, and Analysis. By systematically forming and testing specific, measurable hypotheses, users can efficiently isolate failing components and confirm the true root cause of technical issues.

Performs a systematic and structured investigation to determine the true source of bugs, errors, and unexpected system behavior, rather than merely treating symptoms. This method utilizes techniques like the Five Whys, hypothesis-driven testing, stack trace analysis, and gathering evidence (logs, git diffs) across multiple phases. It is ideal for complex, intermittent, or deeply rooted technical issues in software development.

A structured methodology for coordinating multiple, simultaneous investigation threads to determine the root cause of complex system failures, performance regressions, or integration bugs. This skill decomposes a large problem into independent tracks (e.g., database, application code, infrastructure), assigns ownership, and manages structured sync points (Continue/Pivot/Converge) to converge on a solution faster than serial debugging. Essential for high-stakes production incident response.

A comprehensive, four-stage methodology for debugging complex software issues, ensuring that fixes target the root cause rather than merely masking symptoms. This guide mandates rigorous investigation (gathering evidence, tracing data flow), pattern analysis, controlled hypothesis testing, and disciplined implementation via test-driven development. Use this when facing production bugs, test failures, performance degradation, or unexplained system behavior, especially under time pressure.

This comprehensive guide addresses common and complex errors encountered when automating Apple Notes on macOS using JXA or osascript. It covers three major areas: TCC permission denials, AppleEvent communication failures, and iCloud synchronization issues. The document provides a detailed error reference table, root cause analysis, tested fixes, and diagnostic scripts to help developers successfully automate Notes tasks.