Skill UI

Implements an Apollo.io observability stack that collects metrics, structured logs, distributed traces, and alerts, enabling teams to monitor Apollo integrations via Grafana dashboards and health checks.

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.

Guides developers through reproducing issues, isolating failure cases, testing hypotheses, and verifying fixes with regression safeguards, while referencing tools, logs, stack traces, and git bisect workflows to expose stubborn root causes.

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.

Capture and submit your first error event to Sentry, then confirm it appears in the dashboard with stack trace, metadata, user context, and tags for verifying integrations.

Guides teams on integrating Sentry with existing logging, metrics, and APM stacks, correlating traces and dashboards, and wiring alerts for unified observability workflows.

Windsurf Debugging AI uses Cascade to analyze stack traces, error logs, and context so developers can identify root causes, apply fixes, and document prevention steps during troubleshooting.

Adds samber/oops structured error builders to Go services, giving stack traces, codes, user-friendly messages, panic recovery, and exporter-friendly attributes for observability and diagnostics.

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.

Ensures every framework-specific decision is traced to authoritative docs: detect stack versions, fetch relevant pages, implement documented patterns, cite sources, and flag conflicts before committing code.

Inspects live or staging websites to spot layout, responsive, and accessibility issues, then traces those problems to source files for targeted fixes, making it ideal for developers and designers reviewing static sites, SPAs, or full-stack apps.