systematic-debugging
[ 注目 ]Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Killer-Skillsディレクトリで数千のAI Agentスキルを探索・インストール。Claude Code、Windsurf、Cursorなどに対応。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Debugging techniques and tools for IntelliJ development. Use when debugging IDE issues or investigating failures.
Desktop app (Tauri 2 + SolidJS) to compose Claude Code workspaces with curated skill packages, MCP servers, hooks, commands & CORE-documenten — OpenAEC Foundation
Use Maestro MCP and Tauri MCP to run React Native flows and capture Inspector state for self-validation. Use when working on RN/Inspector code and you need to verify changes (run app, run Maestro flows, capture screenshots, then evaluate results).
Instructions for debugging agentstack-server during development
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
Debugs Docker build failures, container runtime errors, platform architecture issues (ARM64/AMD64/WSL2), AWS ECR/ECS pull failures, and optimizes Docker workflows. Use when encountering Docker build errors, container crashes, ECR authentication issues, ECS deployment problems, performance issues, networking failures, volume permission errors, or when working with multi-platform Docker images.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Systematic methodology for debugging pagination issues in API integrations, especially when switching between API versions or endpoints. Auto-activates when pagination stops early, returns duplicate results, or fails to iterate through complete datasets. Covers cursor-based vs page-based pagination, API response structure verification, and efficiency optimization. Trigger keywords: pagination bug, API not paginating, stuck at one page, cursor pagination, nextPageCursor, page-based pagination. (project)
Debugging, build analysis, and ecosystem tools.