4-phase root cause debugging: understand bugs before fixing.
The English summary is being prepared. Showing the original description.
1.9K skills · sorted by relevance
4-phase root cause debugging: understand bugs before fixing.
The English summary is being prepared. Showing the original description.
系统的 6 阶段 Core Debugging 协议。结构化 Bug 处理流程,包含快速检查、隔离测试、20分钟规则和 Bug 报告模板。
The English summary is being prepared. Showing the original description.
Systematic 6-phase debugging protocol. Structured approach to bugs with quick checks, isolated testing, 20-minute rule, and bug report template.
The English summary is being prepared. Showing the original description.
Operational guide for the ArtCraft MCP integration — the community Python rebuild (C:\Users\rasta\artcraft-mcp-py\artcraft_mcp_server.py) that replaces the broken upstream artcraft-mcp.exe, the live api.storyteller.ai/v1 API map (required headers, cookie auth, endpoint schemas), the upstream bug/PR trail (issues #1/#3, PR #2), the reverse-engineering playbook (browser capture, cookie injection, schema fishing via validation errors, handshake replay, Windows MITM kit), and the generic MCP-protocol debugging playbook (snake_case servers, the shim pattern, 'missing field protocolVersion' diagnosis). Use when working on ArtCraft MCP tools, debugging an artcraft server connection, extending the Python rebuild, or diagnosing any third-party MCP handshake failure.
The English summary is being prepared. Showing the original description.
Use when working with error debugging multi agent review
The English summary is being prepared. Showing the original description.
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.
The English summary is being prepared. Showing the original description.
Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.
The English summary is being prepared. Showing the original description.
Use when working with debugging toolkit smart debug
The English summary is being prepared. Showing the original description.
[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res
The English summary is being prepared. Showing the original description.
Provider (v6.x) state management for Flutter using ChangeNotifier and InheritedWidget with MVVM architecture pattern. Use this skill when implementing Provider-based state management, using Consumer/Consumer2 widgets for targeted rebuilds, accessing state with context.read/context.watch/context.select, setting up ChangeNotifierProvider or StateNotifierProvider, configuring MultiProvider for multiple providers, implementing ProxyProvider for dependent state, using Selector for optimized rebuilds, migrating from StatefulWidget to reactive state, maintaining legacy Provider codebases, debugging provider not found errors, preventing memory leaks with proper ChangeNotifier disposal, fixing context access issues in initState, or resolving .value constructor anti-patterns. Essential for apps with shared state across widgets (shopping carts, authentication, global settings, form state, theme management), when teaching state management fundamentals, or when debugging memory leaks and resource cleanup in Provider-based applications.
The English summary is being prepared. Showing the original description.
UI review and browser-driven debugging workflow for Chrome DevTools MCP, Playwright MCP/CLI, browser ownership, evidence capture, minimal fixes, and durable UI regression tests.
The English summary is being prepared. Showing the original description.
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
The English summary is being prepared. Showing the original description.
Use when working with Dagger — dagger CI/CD pipeline management. Covers pipeline-as-code configuration, module management, function execution, caching layers, container builds, and pipeline debugging. Use when managing Dagger pipelines, debugging function execution, inspecting modules, or optimizing container-based CI workflows.
The English summary is being prepared. Showing the original description.
Use when working with Ansible — ansible automation and configuration management. Covers playbook execution, inventory management, role management, vault secrets, ad-hoc commands, fact gathering, and task debugging. Use when running playbooks, managing inventories, debugging task failures, or auditing Ansible configurations.
The English summary is being prepared. Showing the original description.
When isolating and fixing unpredictable or complex software bugs.
The English summary is being prepared. Showing the original description.
Expert Convex Auth setup, production, OAuth, security, and debugging guidance. Use when adding or auditing Convex Auth, configuring GitHub/Google/Apple OAuth, setting auth env vars, protecting Convex functions with getAuthUserId, debugging callback URLs, preparing production auth, rotating keys, or reviewing auth security.
The English summary is being prepared. Showing the original description.
Use when designing, running, or judging an experiment on a Syntropic137 workflow - comparing prompt variants, fan-out vs single agent, adversarial cross-model review, model selection (can Haiku do this job), phase splits, or tool grants. Trigger phrases include "run a workflow experiment", "A/B the workflow", "does fan-out help", "which model for this phase", "is this prompt better", "measure review quality", "why did the workflow do that". Do NOT use for a one-off workflow run that is just doing work, for authoring a workflow that is not being compared against anything, or for debugging a single failed execution (that is ordinary debugging).
The English summary is being prepared. Showing the original description.
Guide for training outputs, metrics logging, logtree reports, tracing/profiling, and debugging training runs. Use when the user asks about training logs, metrics, debugging, tracing, profiling, timing, Gantt charts, or understanding training output files.
The English summary is being prepared. Showing the original description.
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
The English summary is being prepared. Showing the original description.
4-phase root cause debugging: understand bugs before fixing.
The English summary is being prepared. Showing the original description.
Structured debugging methodology — reproduce, isolate, hypothesize, verify. Covers git bisect, binary search, logging, and minimal reproduction.
The English summary is being prepared. Showing the original description.
コードを書く時の実装原則(既存パターンの踏襲・deep module 設計・seam・テスタビリティ・シーム限定 TDD・コメント規約・リーダブルコード)。プロダクションコードの差分を作る時に、規模を問わず使用(数行の修正も含む)。新しい module・関数・エンドポイント・画面の追加、DB への書き込み、認可・入力検証の追加、既存構造を変えるリファクタでは特に。CSS・HTML・テンプレート等のフロントエンド資産も対象。lint・CI 等の設定ファイルだけの変更では使わない。TypeScript/Python/Go の言語別ガイドを同梱。境界: バグ・エラーの原因調査は systematic-debugging が先、提出前の diff 確認は self-review。
The English summary is being prepared. Showing the original description.
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
The English summary is being prepared. Showing the original description.
DEBUGGING SKILL — Read and analyze Cocos Creator project.log for runtime errors, warnings, and stack traces. USE FOR: any bug report, crash, UI glitch, TypeError, null reference, missing asset, CompositePanel mount fail, ChildPanel route fail, or screen spec wiring error. Load this skill FIRST before any runtime debugging session. DO NOT USE FOR: compile errors (use get_errors tool instead).
The English summary is being prepared. Showing the original description.