Depuració
Detecció i correcció de problemes i anàlisi d’errors
lint
helderberto
Run linting and formatting checks. Use when user asks to "run linter", "/lint", "check linting", "fix lint errors", or requests code linting/formatting.
golang-patterns
peopleforrester
Go 1.22+ best practices, patterns, and idioms. Covers error handling, concurrency, interfaces, generics, and standard library patterns. Use when writing Go code or reviewing Go patterns.
fix-github-issue
freekmurze
Fix GitHub issues using gh CLI. Use when asked to fix, resolve, or address a GitHub issue. Creates fixes on separate branches, runs tests locally, and creates PRs when tests pass. Requires gh CLI authenticated and repo cloned locally.
receiving-code-review
oyi77
Use when getting code feedback, before implementing suggestions.
moltbook-interact
oyi77
Automate interactions on Moltbook - post content, engage with threads, and manage account
model-router
oyi77
Intelligent model routing via subagents - automatically spawn the right model for each task complexity
insecure-defaults
runkids
"Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing security, reviewing config management, or analyzing environment variable handling."
dwarf-expert
runkids
Provides expertise for analyzing DWARF debug files and understanding the DWARF debug format/standard (v3-v5). Triggers when understanding DWARF information, interacting with DWARF files, answering DWARF-related questions, or working with code that parses DWARF data.
address-sanitizer
runkids
AddressSanitizer detects memory errors during fuzzing. Use when fuzzing C/C++ code to find buffer overflows and use-after-free bugs.
fp-check
runkids
"Systematically verifies suspected security bugs to eliminate false positives. Produces TRUE POSITIVE or FALSE POSITIVE verdicts with documented evidence for each bug."
java-best-practices
Leavesfly
Java 编码最佳实践与设计模式
checkout-integration
dodopayments
Guide for creating checkout sessions and payment flows with Dodo Payments - one-time, subscriptions, and overlay checkout.
nix
i9wa4
Nix commands and package management guide. Use when: - Running nix build, nix run - Adding custom packages - Using nurl for hash acquisition
git
i9wa4
Git operations guide. Provides how-to for common git tasks. Use when: - Writing commit messages (Conventional Commits format) - Understanding git workflows
robius-matrix-integration
ZhangHanDong
CRITICAL: Use for Matrix SDK integration with Makepad. Triggers on: Matrix SDK, sliding sync, MatrixRequest, timeline, matrix-sdk, matrix client, robrix, matrix room, Matrix 集成, 聊天客户端
makepad-router
ZhangHanDong
"CRITICAL: Use for ALL Makepad/Robius questions including widgets, layout, events, and shaders.
sentry-ios-swift-setup
getsentry
Setup Sentry in iOS/Swift apps. Use when asked to add Sentry to iOS, install sentry-cocoa SDK, or configure error monitoring, tracing, session replay, logging, or profiling for iOS applications using Swift and SwiftUI.
sentry-setup-logging
getsentry
Setup Sentry Logging in any project. Use this when asked to add Sentry logs, enable structured logging, setup console log capture, or integrate logging with Sentry. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and other frameworks.
sentry-setup-tracing
getsentry
Setup Sentry Tracing (Performance Monitoring) in any project. Use this when asked to add performance monitoring, enable tracing, track transactions/spans, or instrument application performance. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and Node.js.
fix-ci
ryoppippi
Diagnoses and fixes CI failures with the gh CLI. Use when GitHub Actions checks are red and the failing logs need to be fetched, analysed, and resolved.
react-server-components
ryoppippi
Reviews React Server/Client Component boundaries against Next.js and React docs. Use when auditing 'use client' placement or splitting components for proper RSC behaviour.
explore-plan
AlexanderMattTurner
Drives the Explore -> Plan -> Critique -> Review -> Verify discipline for a written plan. Activate on entry to plan mode, before writing the plan — including the plan-mode requests "plan this", "scope this out", "figure out how to do X", "explore the codebase first" — in auto mode at the start of any non-trivial task, where no plan gate fires — and in any other mode when the task obviously needs a plan (several files, an unfamiliar subsystem, more than one PR), invoked informally without entering plan mode. A trivial edit (typo, single-line change) activates nothing, in any mode. Enforces a self-critiqued written plan, convergent setup work started in the background while design questions settle, and real verification instead of trusting a success claim.
fact-checking
axiomantic
"Verify technical claims in code, docs, and comments via evidence-backed verdicts before merge."
debugging
axiomantic
"Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work', 'X is broken', 'something's wrong', 'getting an error', 'exception in', 'stopped working', 'regression', 'crash', 'hang', 'flaky test', 'intermittent failure', or when user pastes a stack trace/error output. NOT for: test quality issues (use fixing-tests), adding new behavior (use implementing-features)."