Loading...
Loading...
Found 1,737 Skills
Resolves React hook violations (rules of hooks, useEffect dependencies, hook ordering).
Guidance for implementing encoders/compressors that must produce output compatible with an existing decoder/decompressor. This skill applies when tasked with writing compression algorithms, arithmetic coders, entropy encoders, or any encoder that must be the inverse of a given decoder implementation.
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug, build error, broken, not working, why is X failing, check this code, security check, PR review, audit code, refactor. Also triggers when investigating 4xx or 5xx errors, deploy failures, environment variable issues, and CMS integration problems.
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.
Debug and fix bugs, errors, or unexpected behavior
Activate when the user clearly has a skill issue. Generates chaotic, barely-functional code with maximum confidence and sarcastic commentary. Guarantees an infinite loop of attempted fixes that never quite land.
Use when the user asks to implement agreed work, diagnose or fix a bug or performance regression, and verify the resulting outcome.
Проверить способ решения до того, как цена ошибки выросла. Использовать: перед нетривиальной фичей или дорогой развилкой; когда запрос описывает готовое решение вместо проблемы; перед редизайном, миграцией, унификацией или другой массовой правкой; перед второй правкой без новых фактов; после двух неудачных исправлений, повторного сообщения о том же симптоме или одной ложной победы. Не использовать как ритуал для мелких очевидных правок и продолжения уже согласованной работы.
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.
Diagnose, repair, and verify follow-up changes to an implementation already in progress.
Concurrent investigation of independent failures. Use when multiple unrelated issues need parallel resolution.
Use when a named runtime or compiler bug in a local repository needs independent reproduction.