Depuració

observability-first-debugging

NTCoding

"Systematic debugging methodology that eliminates guessing and speculation. Add instrumentation to gather specific data that fully explains the problem. Evidence before hypothesis. Observation before solution. Triggers on: debugging, error investigation, 'why is this failing', unexpected behavior, test failures, non-zero exit codes, stack traces."

fix-it-never-work-around-it

NTCoding

"Stops execution and fixes root cause when commands, builds, scripts, or tools fail unexpectedly. Triggers on workaround language: 'directly', 'instead', 'alternatively', 'skip', 'fall back', 'work around', 'isn't working', 'broken', 'manually'. Activates on any unexpected non-zero exit code or process failure."

tdd-process

NTCoding

"Strict test-driven development state machine with red-green-refactor cycles. Enforces test-first development, meaningful failures, minimum implementations, and full verification. Activates when user requests: 'use a TDD approach', 'start TDD', 'test-drive this'."

writing-tests

NTCoding

"Principles for writing effective, maintainable tests. Covers naming conventions, assertion best practices, and comprehensive edge case checklists. Based on BugMagnet by Gojko Adzic. Triggers on: writing any test, 'add tests', test review, test naming, assertion choices, edge case coverage, 'what should I test', test structure decisions."

independent-research

NTCoding

"Use when about to ask the user a factual question, propose a solution, diagnose an error, or choose between approaches. Triggers on: 'Do you have X installed?', 'What version?', 'Is X configured?', 'We should...', 'The fix is...', 'Options: 1...', 'Based on my understanding...', 'I believe X supports...'. Before deciding anything, spin up parallel subagents to WebSearch for current docs, community solutions, framework best practices, and GitHub issues. Your memory is stale — verify everything."

bash-defensive-patterns

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.

local-review

OmniNode-ai

Local code review loop that iterates through review, fix, commit cycles without pushing

integrate-asset-delivery-with-transloadit-smartcdn-in-nextjs

transloadit

Add Transloadit Smart CDN URL signing to a Next.js App Router project (server-side signing route + optional client demo page).

conformance-debug

uze-sh

Fast, targeted debugging of the Harness Conformance Lab (conformance/) — use whenever a conformance check fails (locally or in CI), a check is recorded ADAPTED, a harness version drifted, a harness TUI check needs poking at directly, or you're about to guess at a fix instead of reproducing the real failure. Covers reading the failure's shape, checking the vendor's current docs/changelog/issues before touching code, the --sandbox and --experiment fast loops, proving the provider speaks the real wire shape with --discovery and mitmproxy, telling a vendor limitation from a Lab defect, and reading evidence/verdict.json.

langsmith-trace-analyzer

Lubu-Labs

"Fetch, organize, and analyze LangSmith traces for debugging and evaluation. Use when you need to: query traces/runs by project, metadata, status, or time window; download traces to JSON; organize outcomes into passed/failed/error buckets; analyze token/message/tool-call patterns; compare passed vs failed behavior; or investigate benchmark and production failures."

tui-chat-design

jeong-sik

"masc TUI 채팅 화면이 무엇을 어떤 기호로 그리는지 정리한 표와 규칙이다. 말한 사람 마크, 턴 레일, 왼쪽 여백의 순서, 시계 칸, Ctrl-F 밀도 단계, 밝기 위계와 끝난 일의 접힘, 줄 문구를 바꾸거나 새 기호를 넣기 전에 쓴다. 바꾼 화면을 실제로 띄워 확인하는 방법은 tui-pty-scenario 에 있다."

investigate

d-kimuson

問題の原因調査・切り分けを行うときに有効化

qodo-pr-resolver

ilchemla

Resolve Qodo PR review comments through analyze-confirm-execute workflow with severity-based prioritization. Analyzes comment validity, detects CI failures, confirms response approach with user, executes code changes, runs tests, and resolves threads. Use when responding to Qodo PR review comments, addressing Qodo feedback, resolving review issues, or managing Qodo review threads.

langgraph-error-handling

Lubu-Labs

Implement LangGraph error handling with current v1 patterns. Use when users need to classify failures, add RetryPolicy for transient issues, build LLM recovery loops with Command routing, add human-in-the-loop with interrupt()/resume, handle ToolNode errors, or choose a safe strategy between retry, recovery, and escalation.

intelligence

OmniNode-ai

Request intelligence from the OmniIntelligence service for pattern discovery, code analysis, and context enrichment

challenge-that

NTCoding

"Force critical evaluation of proposals, requirements, or decisions by analyzing from multiple adversarial perspectives. Triggers on: accepting a proposal without pushback, 'sounds good', 'let's go with', design decisions with unstated tradeoffs, unchallenged assumptions, premature consensus. Invoke with /challenge-that."

concise-output

NTCoding

"Enforces brevity and signal-over-noise in all outputs. Eliminates verbose explanations, filler phrases, and unnecessary elaboration. Triggers on: every response (governs output length and density when loaded)."

git-advanced-workflows

julianobarbosa

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

olore-neverthrow-latest

olorehq

Local neverthrow documentation reference (latest). Neverthrow documentation. Use for type-safe error handling with Result and ResultAsync, railway-oriented programming, andThen/map chaining, and error aggregation in TypeScript.

olore-zod-3

olorehq

Local Zod v3 documentation reference. Use when asked about Zod schema validation, TypeScript type inference, error handling, or migration from earlier versions.

olore-zod-latest

olorehq

Local zod documentation reference (latest). Zod schema validation documentation. Use for TypeScript type inference, parsing, error handling, and schema composition.

olore-sentry-latest

olorehq

Local Sentry documentation reference (latest). Sentry error monitoring documentation. Use for error tracking, performance monitoring, session replay, SDK setup, alerts, releases, and integrations.

Rust Expert Skill

huiali

express

blencorp

Express.js framework patterns including routing, middleware, request/response handling, and Express-specific APIs. Use when working with Express routes, middleware, or Express applications.