Debugging
Find and fix bugs, error analysis
content-reflection
by drshailesh88
Pre-publication quality assurance for cardiology thought leadership content. Use AFTER any content is drafted to evaluate scientific rigor, voice authenticity, positioning alignment, audience calibration, and credibility risk. Provides structured critique with specific revision suggestions. Works on any content type—tweets, threads, newsletters, editorials, video scripts.
changelog-writer
by peopleforrester
Generate and maintain changelogs following Keep a Changelog and Conventional Commits standards. Use when releasing versions, documenting changes, or updating project history.
typescript-patterns
by peopleforrester
TypeScript 5.x best practices, patterns, and idioms. Covers strict mode, branded types, discriminated unions, utility types, and Zod validation. Use when writing TypeScript or reviewing TS patterns.
rust-patterns
by peopleforrester
Rust best practices, patterns, and idioms. Covers ownership, error handling with Result/Option, traits, lifetimes, and async Rust. Use when writing Rust code or reviewing Rust patterns.
error-patterns
by DoubleslashSE
Error recognition and diagnosis patterns for infrastructure troubleshooting. Use when identifying, categorizing, or resolving errors across platforms.
debugging-assistant
by peopleforrester
Systematic debugging approach for identifying and fixing bugs. Use when the user reports a bug, error, or unexpected behavior. Guides through methodical investigation rather than guessing at solutions.
clean-code
by fellipeutaka
Write clean, readable, and maintainable code following principles from Robert C. Martin's "Clean Code" and Object Calisthenics. Use when writing, reviewing, or refactoring code to improve naming, function design, formatting, error handling, and class structure. Includes code smell detection and refactoring guidance.
Functional Patterns for Node.js/TypeScript
by DoubleslashSE
```
dotnet-build
by DoubleslashSE
.NET build configuration and error handling. Use when building projects, diagnosing build errors, or configuring build options.
commit-helper
by peopleforrester
Write clear, conventional commit messages. Use when the user asks to commit changes, needs help with commit messages, or when following Conventional Commits specification is required.
playwright
by fellipeutaka
Write, debug, and maintain Playwright end-to-end tests for web applications. Use when working with Playwright test files, configuring playwright.config.ts, writing browser automation, debugging flaky E2E tests, setting up authentication for tests, API mocking/interception, visual regression testing, accessibility testing, or CI/CD integration for browser tests. Triggers: Playwright, E2E test, end-to-end, browser test, @playwright/test, playwright.config, page object model, test fixture, visual snapshot, trace viewer.
golang-patterns
by 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.
code-reviewer
by peopleforrester
Systematic code review for pull requests and code changes. Use when the user asks for a code review, PR review, or wants feedback on code quality. Provides structured feedback on correctness, security, performance, and maintainability.
instrument-existing-agent-with-prefactor-sdk
by prefactordev
Use when an existing agent already works without Prefactor and you need to add tracing for runs, llm calls, tool calls, and failures with minimal behavior changes.
error-detective
by AutumnsGrove
Systematic debugging and error resolution using the TRACE framework (Trace, Read, Analyze, Check, Execute). Use when debugging errors, analyzing stack traces, investigating failures, root cause analysis, or troubleshooting production issues.
apply-all-findings
by troykelly
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
debug
by thechandanbhagat
Debug code, analyze errors, interpret stack traces, find root causes, and suggest fixes. Use when troubleshooting bugs, analyzing crashes, or investigating unexpected behavior.
proof-architect
by Data-Wise
Structured methodology for constructing and verifying mathematical proofs in statistical research
autonomous-operation
by troykelly
Use when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achieved
silent-failure-hunter
by troykelly
Use when asked to detect silent failures/weak error handling or explicitly asked to run the silent-failure-hunter subagent.
research-after-failure
by troykelly
Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming
no-deferred-work
by troykelly
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
test-driven-development
by aiaiohhh
Use when implementing any feature or bugfix, before writing implementation code
deep-learning-core
by levy-n
Explains neural network fundamentals: the Three Pillars (Model, Loss, Optimizer), backpropagation, gradient descent variants (SGD, Adam), regularization (Dropout, BatchNorm), and MLP architecture design. Use when learning how neural networks work, debugging training issues, or when user asks about 'backpropagation', 'vanishing gradients', 'learning rate', 'loss function', 'overfitting', 'underfitting', 'activation functions', 'why isn\'t my model learning', 'gradient descent', 'Adam', 'Dropout', 'BatchNorm', 'autoencoder', 'denoising autoencoder', or 'latent space'.