Loading...
Loading...
Found 1,164 Skills
ALWAYS use when writing code importing "@tresjs/core". Consult for debugging, best practices, or modifying @tresjs/core, tresjs/core, tresjs core, tres.
Build, integrate, and troubleshoot SharePlay GroupActivities features, including GroupActivity definitions, activation flows, GroupSession lifecycle, messaging and journals, ShareLink and SharePlay UI surfaces, and visionOS spatial coordination. Use when implementing or debugging SharePlay experiences across Apple platforms, especially visionOS.
Handle production incidents with urgency. Use when production issues occur for debugging, fixes, and post-mortems.
Docker container debugging and management. Use when investigating container issues, checking logs, resource usage, or Docker Compose services.
Kubernetes debugging patterns. Use for pod crashes, CrashLoopBackOff, OOMKilled, ImagePullBackOff, scheduling failures, deployment issues.
Query Windows 11 version 24H2 cumulative update file information. Search for DLLs, drivers, and system files across all patch levels. Compare file versions between builds, track version history, and identify what changed in each update. Use when: (1) investigating which Windows build introduced a file version, (2) comparing file changes between patches, (3) finding DLL/driver versions for specific builds, (4) debugging Windows update regressions, (5) user asks about Windows 11 24H2 files, KB updates, or build versions.
Kubernetes debugging methodology and scripts. Use for pod crashes, CrashLoopBackOff, OOMKilled, deployment issues, resource problems, or container failures.
Structured multi-step reasoning via Sequential Thinking MCP. Use for complex debugging, architectural trade-offs, or root cause analysis.
Analyzes logs efficiently through targeted search and iterative refinement. Use when investigating errors, debugging incidents, or analyzing patterns in application logs.
Guide for debugging issue on a specific code sections, pattern, or files. Used this skill when user asking for assistant when debugging an issues or explaining a code.
Query Langfuse traces for debugging LLM calls, analyzing token usage, and investigating workflow executions. Use when debugging AI/LLM behavior, checking trace data, or analyzing observability metrics.
Use when ANY runtime debugging is needed — setting breakpoints, inspecting variables, evaluating expressions, analyzing threads, or reproducing crashes interactively with LLDB