PCE（Process-Context Engine）とLDE（Law-Driven Engineering）を統合した実行時Law違反監視スキル。 本番環境でのLaw違反を検知し、pce-memoryにフィードバックして継続的改善を促す。 使用タイミング: (1) 本番ログからLaw違反を分析する時、(2) 「Law違反を確認して」、 (3) 運用中のLaw健全性をチェックする時、(4) 違反パターンから新Lawを発見する時
Processus de debugging systématique une fois la cause identifiée. MANDATORY pour bug fixing. À utiliser lors de correction de bugs, debugging, ou quand l'utilisateur demande de "corriger", "debugger", "réparer un bug".
Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.
代码库功能完成度分析工具。分析项目中各功能模块的实现状态、核心文件存在性、架构采用情况，并生成结构化的JSON分析报告。适用于项目进度跟踪、功能盘点、技术债务评估等场景。
agent-browser (CLI)を使用したWebアプリケーションのデバッグ手法。ブラウザ自動化、スクリーンショット取得、DOMの検査、ログ収集などのデバッグタスクに使用します。
Expert-level Rust performance optimization guidelines for build profiles, allocation, synchronization, async/await, and I/O. This skill should be used when writing, reviewing, or optimizing Rust code for performance. Triggers on tasks involving slow Rust code, large binary size, long compile times, LTO configuration, release profile tuning, allocation reduction, clone avoidance, lock contention, BufReader/BufWriter, flamegraph analysis, async runtime issues, Tokio performance, spawn_blocking, parking_lot vs std sync, or any Rust performance investigation.
Reverse engineering binaries using radare2 (r2). Analyze executables, disassemble code, find functions, extract strings, patch binaries, debug programs, and explore firmware. Supports persistent sessions for large binaries to avoid re-analysis. Use when the user wants to reverse engineer, disassemble, analyze, debug, or patch any binary file including ELF, PE, Mach-O, firmware, or shellcode.
TypeScript performance optimization guidelines for build times, type-checking, declaration emit, and editor responsiveness. This skill should be used when writing, reviewing, or optimizing TypeScript code and tsconfig settings. Triggers on tasks involving slow builds, slow type-checking, CI timeouts, editor lag, tsserver memory issues, monorepo configuration, project references, incremental builds, declaration emit, isolatedDeclarations, --noCheck flag, TypeScript 5.6+ features, TypeScript 7 migration, or any TypeScript performance investigation.
Son degisiklikler logu. Check when debugging or understanding recent fixes.
Use when you need to inspect detailed execution flow of a Python program, stepping through functions and inspecting variable contents with pdb. Triggers include requests to debug Python scripts, trace execution, or inspect runtime state using the pdb debugger.
GameTooltip integration for showing "Archived" status on items and world objects. Covers TooltipDataProcessor hooks, index lookups (O(1) performance), item vs object detection, GUID parsing, title normalization, and enable/disable settings. Use when debugging tooltip issues or implementing similar tooltip integration. Triggers: tooltip, GameTooltip, Archived, TooltipDataProcessor, item tooltip, object tooltip.
4-phase debugging framework preventing "guess-and-check" fixing. Load when debugging fails or for complex bug investigation.
Expert-level Rust performance optimization guidelines for build profiles, allocation, synchronization, and I/O. This skill should be used when writing, reviewing, or optimizing Rust code for performance. Triggers on tasks involving slow Rust code, large binary size, long compile times, LTO configuration, release profile tuning, allocation reduction, clone avoidance, lock contention, BufReader/BufWriter, flamegraph analysis, or any Rust performance investigation.
Use when Python code runs slowly, needs profiling, requires async/await patterns, or needs concurrent execution - covers profiling tools, optimization patterns, and asyncio; measure before optimizing (plugin:python@dot-claude)
Debug “backend won’t start / first request 500 / ports stuck” quickly. Use when uvicorn reload behaves strangely, ports 8000/3000 are blocked, or you see first-request errors like “unexpected keyword argument” due to stale bytecode caches.
Hypothesis testing, root cause analysis, and debugging techniques. Use when debugging, testing hypotheses, validating solutions, proving correctness, or performing root cause analysis on failures.
Identify vulnerabilities in internet-facing systems using Shodan. Use for vulnerability assessment, CVE discovery, and security auditing. Triggers on requests for "vulnerability scan", "find vulns", "CVE check", or "security assessment".
ALWAYS USE FIRST when exploring, searching, or researching this codebase. Use symbol_tree MCP tool before grep/glob/read. Provides instant architecture overview, function relationships, and call graphs without reading full implementations.
Expanded smart-grep playbook for token-efficient rg --json searches with examples and budgeting.
Use when animation feels wrong and you need to diagnose which principle is failing or being misapplied
Start real-time log streaming from connected Android device using adb logcat. Shows only app's log messages. Use when monitoring app behavior, debugging, or viewing Android logs.
Initial reconnaissance on binaries including checksec, file analysis, strings, and symbols. First step for any new target.
Use when working with Ruby metaprogramming features including dynamic method definition, method_missing, class_eval, define_method, and reflection.
