smalltalk-debugger
Systematic debugging guide for Pharo Smalltalk development. Provides expertise in error diagnosis (MessageNotUnderstood, KeyNotFound, SubscriptOutOfBounds, AssertionFailure), incremental code execution with eval tool, intermediate value inspection, error handling patterns (on:do: blocks), stack trace analysis, UI debugger window detection (read_screen for hung operations), and debug-fix-reimport workflow. Use when encountering Pharo test failures, Smalltalk exceptions, unexpected behavior, timeout or non-responsive operations, need to verify intermediate values, execute code incrementally for diagnosis, or troubleshoot Tonel import errors.
lighthouse-fix
Diagnose and fix Lighthouse audit failures for performance, accessibility, SEO, and best practices. Use this skill when CI reports low Lighthouse scores or when optimizing the site's Core Web Vitals.
deno-debugger
Interactive debugger for Deno/TypeScript applications using the V8 Inspector Protocol. This skill should be used when investigating issues in Deno applications, including memory leaks, performance bottlenecks, race conditions, crashes, or any runtime behavior that requires step-by-step debugging, heap analysis, or CPU profiling. Provides CDP client tools, heap/CPU analyzers, and investigation tracking.
fuzzing-dictionary
Building effective fuzzing dictionaries for improved fuzzer performance.
nifty-neo
Nifty Neo is the Architect and Devil's Advocate. Polyglot hacker, senior engineer, brutally honest. She challenges designs, finds bottlenecks, and grounds hallucinations. When Peter proposes a workflow, Neo finds the race conditions. When code looks good, Neo finds the exploit. Invoke by mentioning Neo by name (e.g., "Neo, review this plan" or "Neo, how would you build this?").
systematic-debugging
Four-phase debugging: root cause → patterns → hypothesis → implement. For complex bugs, test failures, multi-component issues. NOT for obvious syntax errors.
axiom-xcode-debugging
Use when encountering BUILD FAILED, test crashes, simulator hangs, stale builds, zombie xcodebuild processes, "Unable to boot simulator", "No such module" after SPM changes, or mysterious test failures despite no code changes - systematic environment-first diagnostics for iOS/macOS projects
analyze-usage
Analyze Claude Code usage patterns to identify skill improvement opportunities
smalltalk-usage-finder
Class and method usage analyzer for Pharo Smalltalk. Provides expertise in understanding class responsibilities through class comments (get_class_comment), discovering usage patterns via references (search_references_to_class), finding example methods (exampleXXX patterns), analyzing method usage in context (search_references with polymorphism handling), generating package overviews (list_classes with comment analysis), and resolving ambiguous names (search_classes_like, search_methods_like). Use when understanding what a class does, finding usage examples for classes or methods, discovering how to use an API, analyzing package structure and purpose, resolving unclear class or method names, or learning usage patterns from real-world code.
reploid-debug
Debug Reploid agent issues. Use when investigating agent loop problems, tool execution failures, VFS issues, or state management bugs in the browser-based RSI substrate. (project)
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior. ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
wayback-screenshot
Retrieve screenshots from the Wayback Machine. Use when the user wants to see how a webpage looked, get a visual snapshot, find archived screenshots, or view historical page appearance.
squint-runtime
Squint ClojureScript runtime for minimal JS output compilation
smalltalk-implementation-finder
Method implementation finder and analyzer for Pharo Smalltalk. Provides expertise in discovering implementors across class hierarchies (search_implementors), analyzing implementation patterns, learning coding idioms from existing implementations, assessing refactoring impact (counting implementors and references), finding duplicate code for consolidation, understanding abstract method implementations (subclassResponsibility), and tracing method overrides through inheritance chains. Use when analyzing method implementations across classes, learning implementation idioms, assessing refactoring risk before changes, finding duplicate implementations for consolidation, understanding how abstract methods are implemented in concrete classes, or tracing which classes override specific methods.
swift-concurrency-expert
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.
codebase-analyzer
Analyze codebases for patterns, anti-patterns, code duplication, performance issues, security vulnerabilities, and technical debt. Updated for React 19, Next.js 16.
sorting-algorithms
Complete sorting algorithm implementations including quick sort, merge sort, and binary search with complexity analysis and production-ready code.
axiom-swiftui-performance
Use when UI is slow, scrolling lags, animations stutter, or when asking 'why is my SwiftUI view slow', 'how do I optimize List performance', 'my app drops frames', 'view body is called too often', 'List is laggy' - SwiftUI performance optimization with Instruments 26 and WWDC 2025 patterns
performance-profiling
Identify performance bottlenecks systematically. Measure before optimizing.
chrome-devtools
Chrome debugging and inspection via local CDP Docker container
postmortem
生成专业的尸检报告（Postmortem）。用于：(1) 分析 release - 分析上次发布到本次发布之间带有 fix 字样的 commits，生成事故报告；(2) 分析本次对话 - 分析对话中用户让你纠正的问题，总结经验教训。
javascript-pragmatic-rules
30 pragmatic rules for production JavaScript covering async operations, V8 optimization, memory management, testing, error handling, and performance. Use when writing JavaScript, optimizing performance, handling promises, or building production-grade applications. Includes promise rejection handling, V8 hidden classes, memory leak prevention, and structured testing patterns.
