Use this skill when auditing SEO, analyzing Core Web Vitals, verifying meta tags, checking structured data, or troubleshooting analytics implementations. Covers Google Search Console, Google Analytics 4, Cloudflare Web Analytics, and technical SEO best practices.
Use when encountering dependency conflicts, CocoaPods/SPM resolution failures, "Multiple commands produce" errors, or framework version mismatches - systematic dependency and build configuration debugging for iOS projects. Includes pressure scenario guidance for resisting quick fixes under time constraints
Framework-specific troubleshooting, boot report analysis, common error patterns
Review dimtensor code for correctness, dimensional safety, and adherence to patterns. Use when reviewing new code or during consolidation phases.
Provides expertise for analyzing DWARF debug files and understanding the DWARF debug format/standard (v3-v5). Triggers when understanding DWARF information, interacting with DWARF files, answering DWARF-related questions, or working with code that parses DWARF data.
Applies a modified Fagan Inspection methodology to systematically resolve persistent bugs and complex issues. Use when multiple previous fix attempts have failed repeatedly, when dealing with intricate system interactions, or when a methodical root cause analysis is needed. Do not use for simple troubleshooting. Triggers after multiple failed debugging attempts on the same complex issue.
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
Use when asked to trace existing codepaths or explicitly asked to run the code-explorer subagent.
コードベース包括的レビュー。6観点（perf/sec/test/arch/cq/docs）を並列サブエージェントで実行し、優先度付きissueファイルをメモリディレクトリに生成。
Detects timing side-channel vulnerabilities in cryptographic code. Use when implementing or reviewing crypto code, encountering division on secrets, secret-dependent branches, or constant-time programming questions in C, C++, Go, Rust, Swift, Java, Kotlin, C#, PHP, JavaScript, TypeScript, Python, or Ruby.
Apple firmware and binary reverse engineering with the ipsw CLI tool. Use when analyzing iOS/macOS binaries, disassembling functions in dyld_shared_cache, dumping Objective-C headers from private frameworks, downloading IPSWs or kernelcaches, extracting entitlements, analyzing Mach-O files, or researching Apple security. Triggers on requests involving Apple RE, iOS internals, kernel analysis, KEXT extraction, or vulnerability research on Apple platforms.
Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and verification protocols. Use when encountering bugs, test failures, unexpected behavior, performance issues, or before claiming work complete. Prevents random fixes, masks over symptoms, and false completion claims. | Sử dụng khi gặp lỗi, bug, test fail, không hoạt động, crash, exception, sửa lỗi, debug.
Parallel 120-probe reconnaissance using G-2 RECON agents. Deploy 12 G-2s commanding 10 D&D-inspired probes each. Use for comprehensive codebase exploration.
Testing for timing side channels and constant-time implementation verification.
Autonomous browser control via Chrome DevTools Protocol and Accessibility Tree for full screen control like GPT Operator. Use when user requests "control my screen", "verify Lovable", "test scrapers", "debug DOM", "autonomous testing", or any browser automation task. NO screenshots - uses CDP + semantic queries for 10x faster, 100% reliable element targeting.
Connectivity troubleshooting with modern Rust-based tools - trippy (traceroute/mtr), gping (graphical ping), and ss (socket statistics). Preferred over legacy netstat/traceroute.
Expert knowledge in optimizing web application performance for speed, efficiency, and excellent user experience. Covers Core Web Vitals (LCP, FID/INP, CLS), loading optimization, runtime performance, bundle optimization, image optimization, caching strategies, lazy loading, and code splitting. Use when optimizing page load times or improving performance metrics.
Generate a visual spec-to-code coverage map showing which code files are covered by which specifications. Creates ASCII diagrams, reverse indexes, and coverage statistics. Use after implementation or during cleanup to validate spec coverage.
