rails-aidebugging-rails
Use when debugging Rails issues - provides Rails-specific debugging tools (logs, console, byebug, SQL logging) integrated with systematic debugging process
Essential command-line tools and system utilities.
Use when debugging Rails issues - provides Rails-specific debugging tools (logs, console, byebug, SQL logging) integrated with systematic debugging process
Detecting and fixing memory leaks and retain cycles in Swift apps using Instruments and best practices.
Techniques for optimizing Swift code performance, memory usage, rendering efficiency, and using Instruments for profiling.
R performance profiling, benchmarking, and optimization strategies. Use this skill when code is running slowly, comparing alternative implementations, deciding between dplyr/data.table/base R, or implementing parallel processing. Covers profvis and bench usage, performance workflow, parallel processing with in_parallel(), data backend selection, modern purrr patterns (list_rbind, walk), and common performance anti-patterns to avoid.
Analyze WebAssembly test (WAST) files to debug compilation issues and create regression tests. Use when the user asks to debug or analyze WAST test failures, investigate compilation bugs in wasmoon, or when encountering test failures in spec/*.wast files. Triggers include "analyze wast", "debug wast", "wast bug", or references to specific .wast test files.
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.
USE WHEN: user wants to publish, port, or share a skill to a marketplace repo. DO NOT USE WHEN: creating new skills, installing skills, or general questions.
Control Firefox browser from the command line. Use for web automation, scraping, testing, or any browser interaction tasks.