Loading...
Loading...
Found 2,164 Skills
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.
Systematic debugging discipline based on David Agans' nine rules, understand the system, reproduce reliably, bisect the search space, change one variable at a time, keep an audit trail, and never declare a fix done until it's verified against the original failure. Use when the user reports something broken, throwing, failing, or slow, or says "diagnose" / "debug this".
This skill should be used when the user asks to "run electrobun dev", "electrobun development mode", "electrobun --watch", "hot reload electrobun", "CEF devtools", or is debugging the electrobun renderer or understanding the dev build cycle.
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.
Prove it for debugging, performance investigation, bottleneck analysis, profiling, and optimization work. When reading code does not prove the cause, run a minimal reproduction, add temporary traces, measure bottlenecks, and verify the fix or improvement.
Debugging and acceptance of MaaFramework (MaaFW) applications (in development state, with devices online) — addressing node recognition failures, missed click targets (recognition success ≠ effective clicks), ROI calibration and threshold tuning, single-node run verification, stuck flows and controller connection troubleshooting, end-to-end acceptance, and pipeline_override effect validation; triage is conducted across five layers: configuration, recognition, action, flow, and acceptance, producing root cause conclusions and evidence, with fixes handed over to maafw-pipeline / maafw-interface / maafw-custom. Use when debugging or acceptance-testing a MaaFW application with a device attached — node recognition failures, clicks that miss, ROI calibration and threshold tuning, single-node run verification, stuck flows and controller connection issues, end-to-end acceptance, or pipeline_override effect checks; triage by layer (config / recognition / action / flow / acceptance), then hand the fix back to maafw-pipeline / maafw-interface / maafw-custom.
End-to-end front→back performance debugging for the Kodus web app. Use when a screen is slow, blank, looping, or you need to trace a UI perf problem down to the API query. Drives Playwright/Chrome MCP to open + measure the screen, then reads the API use-case/repository and the DB (Postgres/Mongo indexes, explain) to find and fix the root cause, verifying live.
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.
Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
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.