bundle-optimization
Bundle size reduction strategies, icon optimization, tree-shaking, and performance analysis. Use when reducing bundle size or optimizing imports.
Bundle size reduction strategies, icon optimization, tree-shaking, and performance analysis. Use when reducing bundle size or optimizing imports.
Optimizador integral de aplicaciones - combina performance, seguridad y mejores prácticas
Self-critique loop that catches mistakes before finalizing - "I'm in danger" detection
Master the art of making systems fast. Profiling, optimization, caching, and the wisdom to know when performance matters and when it doesn't. Measure twice, optimize once.
Use when symptoms don't reveal the cause. Trace backward through call chains to find where problems originate. Follow: Observe symptom → Find immediate cause → Identify caller → Keep tracing → Locate trigger.
Comprehensive anti-reversing, obfuscation, and deobfuscation knowledge base with intelligent routing for JavaScript malware analysis. Use when you need to understand protection mechanisms, deobfuscate code, reverse engineer bundles, or analyze malicious JavaScript with a structured workflow.
Debug bugs and errors using intel-first approach with systematic root cause analysis. Use proactively when errors occur, tests fail, or unexpected behavior appears. MUST trace from symptom to root cause with CoD^Σ reasoning.
Systematic debugging discipline that enforces root cause investigation BEFORE fixes. Triggers on - bug, error, failing, broken, fix, not working, crash, issue, debug, investigate, diagnose, trace, root cause, why is, undefined, null, 500 error, RLS, timeout, infinite loop, exception, stack trace. Integrates with Zen MCP, TodoWrite, and verification-before-completion. Aligns with fail-fast engineering principle.
遇到任何 bug、测试失败或意外行为时使用,在提出修复方案之前进行系统化调试。Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Follow the four phases: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, Implementation.
Review local codebase for bugs and CLAUDE.md compliance using multi-agent analysis
Use when encountering bugs, test failures, or unexpected behavior - ensures root cause understanding before attempting fixes
Advanced TypeScript type system specialist for complex generics, conditional types, template literals, type inference, performance optimization, and type-level programming. Use for intricate type system challenges, recursive types, brand types, utility type authoring, and type performance issues. Includes comprehensive coverage of 18 advanced type system error patterns.
Debug WebSocket connection issues between CLI and FigJam plugin. Use when diagrams aren't syncing, connection fails, plugin shows "Connecting..." indefinitely, or patches aren't being applied to canvas.
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
Detects null pointer dereference vulnerabilities by identifying unchecked pointer usage and missing validation. Use when analyzing pointer operations, input validation, or investigating crash vulnerabilities.
Scans code and data for Protected Health Information (PHI) to ensure HIPAA compliance. Use when reviewing code that handles patient data, healthcare records, or medical information.
Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, efficient JavaScript code. Use when refactoring legacy code, implementing modern patterns, or optimizing JavaScript applications.
How to use the FlowStorm debugger to analyze Clojure/ClojureScript program executions. This skill teaches timeline exploration, value inspection, and debugging patterns using FlowStorm's recording API for runtime analysis.
Check if a Ralph run is active and tail the most recent log.
Tracks untrusted input propagation from sources to sinks in binary code to identify injection vulnerabilities. Use when analyzing data flow, tracing user input to dangerous functions, or detecting command/SQL injection.
코드 종합 분석 (품질/보안/성능/아키텍처). Use when: (1) 코드 분석 요청, (2) 보안 취약점 스캔, (3) 성능 병목 식별, (4) 아키텍처 검토.