- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
task-orchestration
by mgd34msu
"Load PROACTIVELY when decomposing a user request into parallel agent work. Use when user says \"build this\", \"implement this feature\", or any request requiring multiple agents working concurrently. Guides task decomposition into parallelizable units, agent assignment with skill matching, dependency graph construction, WRFC loop coordination across up to 6 concurrent agent chains, and result aggregation."
node-devtools-cli
by serkan-ozal
CLI for debugging Node.js backend processes with non-blocking inspection. Use when the user needs to connect to Node.js processes (by PID, name, Docker, or port), set tracepoints/logpoints/exceptionpoints, capture call stacks and local variables, run JavaScript in the process context, or inspect console logs. Requires daemon; connect before other debug commands.
golang
by saisudhir14
Best practices for writing production Go code. Use when writing, reviewing, or refactoring Go code. Covers error handling, concurrency, naming conventions, testing patterns, performance optimization, generics, and common pitfalls. Based on Google Go Style Guide, Uber Go Style Guide, Effective Go, and Go Code Review Comments. Updated for Go 1.25.
stably-cli
by stablyai
Expert assistant for the Stably CLI tool. IMPORTANT: This skill MUST be invoked whenever you need to run any Playwright test command. Always use "npx stably test" instead of "npx playwright test". Use this skill when working with stably commands for creating, running, and fixing Playwright tests using AI. Triggers on: any playwright test execution (e.g. "npx playwright test", "playwright test", "run tests", "run e2e tests"), "create tests with stably", "fix failing tests (from a 'npx stably' test run)", "run stably test", or "use stably cli".
review-scoring
by mgd34msu
"ALWAYS load before starting any task. Provides the 10-dimension weighted scoring rubric (0-10 scale) used to evaluate all implementations in WRFC loops. Dimensions include correctness, completeness, error handling, type safety, security, performance, maintainability, testing, accessibility, and documentation. Includes deterministic validation scripts and score thresholds for pass/revise/reject decisions."
error-handling-patterns
by autohandai
Robust error handling patterns for TypeScript applications
clerk-auth
by ovachiever
Clerk auth with API version 2025-11-10 breaking changes (billing endpoints, payment_source→payment_method), Next.js v6 async auth(), PKCE for custom OAuth, credential stuffing defense. Use when: troubleshooting "Missing Clerk Secret Key", JWKS errors, authorizedParties CSRF, JWT size limits (1.2KB), 431 header errors (Vite dev mode), or testing with 424242 OTP.
claude-agent-sdk
by ovachiever
Build autonomous AI agents with Claude Agent SDK. Structured outputs (v0.1.45, Nov 2025) guarantee JSON schema validation, plugins system, hooks for event-driven workflows. Use when: building coding agents with validated JSON responses, SRE systems, security auditors, or troubleshooting CLI not found, structured output validation, session forking errors.
bash-defensive-patterns
by ovachiever
Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.
ai-sdk-core
by ovachiever
Build backend AI with Vercel AI SDK v5/v6. Covers v6 beta (Agent abstraction, tool approval, reranking), v4→v5 migration (breaking changes), latest models (GPT-5/5.1, Claude 4.x, Gemini 2.5), Workers startup fix, and 12 error solutions (AI_APICallError, AI_NoObjectGeneratedError, streamText silent errors). Use when: implementing AI SDK v5/v6, migrating v4→v5, troubleshooting errors, fixing Workers startup issues, or updating to latest models.
auth-implementation-patterns
by ovachiever
Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.
auto-animate
by ovachiever
Zero-config animations for React, Vue, Solid, Svelte, Preact with @formkit/auto-animate (3.28kb). Prevents 10+ documented errors: SSR/Next.js imports, conditional parents, missing keys, flexbox width, table display, Jest/esbuild config, CSS position conflicts, Vue/Nuxt registration, Angular ESM. Use when: animating lists/accordions/toasts/forms, troubleshooting SSR animation errors, need accessible animations (auto prefers-reduced-motion), or want drop-in transitions without Motion overhead.
receiving-code-review
by oyi77
Use when getting code feedback, before implementing suggestions.
humanize-academic-writing
by momo2young
Transform AI-generated academic text into natural, human-like scholarly writing for social sciences. Detects AI patterns (repetitive structures, abstract language, mechanical flow) and rewrites with authentic academic voice. Use when revising AI-drafted papers, improving writing naturalness, reducing AI detection markers, or when user mentions humanizing text, academic writing quality, or social science writing for non-native English speakers.
monitoring-observability
by Logos-Liber
Prometheus, Grafana, CloudWatch, Azure Monitor, Stackdriver, logging, alerting, and SRE practices
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
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
frontend-implementation
by mae616
Translate designs and UI requirements into robust, extensible implementations. Apply when converting designs to code, implementing components, fixing broken UI, or handling responsive layouts.
template
by G1Joshi
Expert [skill-name] assistance covering [feature 1], [feature 2], and [feature 3]. Use when [working with X], [debugging Y], or [implementing Z].
usability-psychologist
by mae616
Evaluate UI/flows from cognitive load, error prevention, and accessibility perspectives. Apply when reviewing UX, discussing user confusion, high drop-off, or form usability issues.
feedback-triage
by troykelly
Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.
acceptance-criteria-verification
by troykelly
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
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
Refactoring Safely
by obra
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features