Discover research debugging skills, compare source repositories and read the instructions for each workflow.
Parallel CLI stress testing using orchestrated subagents. Spawns specialized agents to test different CLI domains simultaneously, aggregating results into structured reports. Supports discovery mode (agents ana...
Dart static analysis and linting for aviation-grade code quality. Use when configuring analysis_options.yaml, enforcing strict type safety, creating custom lint rules, or setting up code metrics for Flutter pro...
React and Next.js performance optimization guidelines from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js code.
Deep forensic debugging that never stops until root cause is found or visibility limit is proven. Use when user wants to understand exactly why something is broken, not work around it. Activates on "why is this...
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 r...
Use before committing code or after major changes to verify performance. Catches expensive operations before they cause frame drops.
This skill should be used when dealing with "race conditions in tests", "Redis timing issues", "WebSocket connection timing", "async test failures", "flaky tests due to timing", "test synchronization problems",...
This skill should be used when the user asks to "debug this issue", "find the root cause", "investigate the bug", "systematic debugging", "troubleshoot the problem", or needs help with systematic problem-solvin...
This skill should be used when encountering "flaky tests", "test maintenance issues", "slow test suites", "brittle tests", "test code smells", "test debugging problems", or when tests are hard to understand, ma...
This skill should be used when the user asks to "analyze costs", "optimize infrastructure spending", "reduce operational expenses", "monitor API costs", "audit cloud resources", "optimize database queries", or...
This skill should be used when the user asks to "track ROI", "measure cost savings", "calculate return on investment", "analyze efficiency gains", "measure automation impact", or needs comprehensive ROI measure...
Systematically trace bugs backward through call stack to find original trigger
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Setup structured logging, performance monitoring, and error tracking. Use when user needs logging system, error tracking, performance monitoring, or says "setup logging", "add error tracking", "monitor performa...
Comprehensive code review and health check. Use when user needs project audit, code quality check, conflict detection, or says "review code", "check project", "audit codebase", "health check", "find issues", "c...
Performance monitoring and optimization. Use when user needs N+1 detection, slow query analysis, memory profiling, or says "performance issue", "slow queries", "N+1 problem", "optimize performance", "memory lea...
Omniscient hyper-elite software engineering command center. Triggers: write code, debug, fix bug, build app, create API, design system, architect, deploy, secure, optimize, refactor, review code, test, CI/CD, D...
Elite software engineering toolkit for building production-grade applications. Use when developing, debugging, optimizing, or deploying code—especially for API development, database design, performance tuning,...
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when encountering bugs, test failures, or unexpected behavior - find root cause before fixing
Analyze test coverage requirements and assess whether code meets testing standards. Use when reviewing test plans, evaluating test coverage, or assessing testing quality.
Use when writing, reviewing, or refactoring React/Next.js components, pages, or data fetching where performance, bundle size, or render efficiency is a concern.
Use when reviewing UI, accessibility, or UX in web interfaces and you need to audit components against web design best practices.
Runs and interprets exit graph consistency scans (dangling exits, orphan locations, missing reciprocal exits). Use when exits/navigation look wrong or when changing location graph data.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.