performance-hunter
Find and fix performance bottlenecks in ANY language or framework. Use when applications are slow, memory usage is high, or you need to optimize critical paths.
Find and fix performance bottlenecks in ANY language or framework. Use when applications are slow, memory usage is high, or you need to optimize critical paths.
Analyzes any project to understand its structure, tech stack, patterns, and conventions. Use when starting work on a new codebase, onboarding, or when asked "how does this project work?" or "what's the architecture?"
This skill should be used when the user asks about "slow specs", "test performance", "parallel tests", "spec profiling", "let vs let!", "build vs create", "test optimization", or needs guidance on making RSpec tests faster.
Prometheus UI Development Skill for PCGS 2.0. Use for ANY UI work in Prometheus: (1) Positioning/layout changes using coordinate system, (2) Component creation within Content Zone, (3) Style modifications within doctrine, (4) Viewport configuration, (5) Frame element awareness. Enforces UI_DOCTRINE.md immutable elements. Triggers: position, layout, align, move, resize, coordinate, grid unit, vw, vh, UI component, Content Zone, frame, PKE interface.
Analyzes software bugs including root cause identification, severity assessment, impact analysis, reproduction steps validation, and fix recommendations. Performs bug triage, categorization, duplicate detection, and regression analysis. Use when investigating bugs, analyzing crash reports, triaging issues, debugging problems, reviewing error logs, or when users mention "analyze bug", "investigate issue", "debug problem", "bug report", "crash analysis", "root cause analysis", or "fix recommendation".
Comprehensive forensic analysis skill for enterprise codebases across Azure, Dynamics 365, C#, SAP, Mulesoft, Power Platform, and more. Covers security, performance, architecture, and compliance in multi-language, multi-system environments. Use this for deep-dive audits and refactoring insights.
Research and understand React projects and features. Use when asked to explore a React codebase, check if a feature exists, understand component relationships, or map project structure. Specialized for React/Vite/Next.js projects.
Log problems, bugs, and debugging processes with solutions. Use when encountering issues during development, debugging problems, or documenting solutions for future reference. Maintains DEBUG_LOG.md with structured problem-solution entries.
Systematically analyze a codebase to understand its structure, purpose, technologies, and architecture. Use this skill when users ask to "analyze this project", "explain this codebase", "what does this project do", or need a comprehensive overview of repository contents.
This skill provides a systematic approach for investigating and fixing bugs and issues in the codebase. Use this skill when users report bugs, unexpected behavior, test failures, or request fixes for specific issues. The skill guides through issue registration, root cause analysis, impact assessment, minimal code changes, quality validation, and E2E testing.
Create comprehensive forensic timelines from multiple data sources. Use when reconstructing event sequences, correlating activities across sources, or visualizing incident progression. Supports super timeline creation and analysis.
This skill should be used when the user reports a "bug", "not working", "fix this", "debug", "test failing", or when investigating unexpected behavior. Four-phase framework ensuring root cause understanding before attempting solutions.
Analyze project health including structural issues, security vulnerabilities, performance concerns, and code stability metrics. Use when auditing codebases, reviewing project quality, checking for security issues, identifying architectural problems, measuring code health, or generating quality reports.
Comprehensive React and Next.js performance optimization guide with 40+ rules for eliminating waterfalls, optimizing bundles, and improving rendering. Use when optimizing React apps, reviewing performance, or refactoring components.
Systematic debugging techniques including error classification, root cause analysis (5 Whys), reproduction strategies, and error documentation. Use when debugging errors, investigating failures, analyzing stack traces, fixing bugs, or documenting errors in error-log.md. (project)
Review architecture decisions and code changes against documented architecture principles. Use this skill before implementing new features or refactoring existing code to ensure compliance with layer boundaries, separation of concerns, and design patterns. Should be invoked when user requests "architecture review" or before making significant changes.
Diagnoses project health, architecture risks, and technical debt. Use when starting a new session or analyzing the codebase structure.
Systematic debugging expert for all languages and frameworks. Invoke for error investigation, troubleshooting, log analysis, root cause analysis. Keywords: debug, error, bug, traceback, exception, breakpoint.
Analyze Claude Code usage patterns, project structure, and discover community resources for workflow optimization
Analyzes code for performance issues including inefficient algorithms, unnecessary computations, memory leaks, large file sizes, slow queries, and missing caching. Returns structured performance issue reports with optimization suggestions.