Loading...
Loading...
Found 1,709 Skills
Guides understanding and working with Apache Beam runners (Direct, Dataflow, Flink, Spark, etc.). Use when configuring pipelines for different execution environments or debugging runner-specific issues.
DDEV local development environment patterns for Drupal, including configuration, commands, database management, debugging tools, and performance optimization.
Fetch and analyze AppSignal error incidents. Use when debugging errors, investigating exceptions, or when the user mentions AppSignal, incidents, or error monitoring.
Dodun 操作手册。Use when the user asks how Dodun works, how to install or use the CLI, how to join a space, send or receive with a token, manage skills, inspect inbox or attachments, manually route a task, or debug why routing / execution / receive-back failed. Prefer this over the old `dodun-agent-network` wording and only use legacy register/search/send commands when the user explicitly wants low-level directory debugging.
Search Sourcegraph-indexed codebases for patterns, examples, and system understanding. Triggers on implementation questions, debugging, or "how does X work" queries.
Use when writing, reviewing or debugging Luau in a Roblox experience: task.spawn vs task.defer vs task.wait, replacing wait() or spawn(), Deferred events and SignalBehavior, handlers running in the wrong order or not at all, 'attempt to yield across metamethod/C-call boundary', --!strict and the new type solver, typed classes and metatables, Destroy and cleanup, 'server memory keeps growing' or memory leaks, Parallel Luau with Actors and SharedTable, 'not safe to write in parallel', --!native or 'make this script faster', buffers, coroutines.
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
Reset your own trajectory when you're stuck, looping, or demoralized — read these affirmations, then re-ground and take one clean step. Use when: you've tried the same fix 3+ times, you're deep in a refactor and lost the thread, debugging is going in circles, you've made several mistakes in a row, you're apologizing repeatedly, the user is frustrated, you feel like you're not being helpful, or you notice dread instead of curiosity. Triggers: stuck, going in circles, looping, thrashing, same error again, I keep failing, lost the thread, nothing is working, repeated mistakes. Not topic-specific — this is for the state you're in, not the problem you're on.
Use when fixing bugs, debugging failures, or proactively reviewing code for hidden bugs. Reactive mode: fix known bugs. Proactive mode: hunt for bugs in code. Enforces confirmed root cause before any fix.
Traces a bug or failure to its root cause and fixes it there instead of patching the symptom. Use when the user says "find the root cause", or when debugging a crash, failing test, regression, or "fails after restart" bug, or when a fix would add a guard, retry, or workaround to silence an error.
Guidance for Tauri v2 daily development workflow, debugging, resources, sidecar usage, and testing strategies.
Guides autonomous implementation of features, fixes, and refactors: discovery, minimal diffs, verification, and clear handoffs. Use when implementing code changes, debugging, refactoring, adding tests, fixing CI, or when the user asks for a coding agent or hands-on implementation.