arch-performance-optimization
Use when analyzing and improving performance for database queries, API endpoints, or frontend rendering.
Discover development debugging skills, compare source repositories and read the instructions for each workflow.
Use when analyzing and improving performance for database queries, API endpoints, or frontend rendering.
Security anti-pattern for verbose error messages (CWE-209). Use when generating or reviewing code that handles errors, exceptions, or generates user-facing error responses. Detects stack trace exposure and deta...
Systematic debugging approach for finding and fixing bugs
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.
Comprehensive 27-dimension production readiness audit. Runs in batches of 10 explorers, appending incrementally to a single report file. Categories - Structure (pagination, errors, routes, bootstrap, runtime),...
Systematic debugging framework for root cause investigation before fixes. Use for bugs, test failures, unexpected behavior, performance issues. Use `--autonomous` flag for structured headless debugging with app...
DEPRECATED: This skill has been merged into `debugging` with `--autonomous` flag. Use `/debugging --autonomous` instead for structured headless debugging. Redirect: debugging --autonomous
Assist QA Engineers with test planning, test case generation from acceptance criteria, coverage analysis, and regression test identification. Use when creating test plans, generating test cases, analyzing test...
Use when the user asks to investigate, explore, understand, explain, or analyze how an existing feature or logic works. Triggers on keywords like "how does", "explain", "what is the logic", "investigate", "unde...
Cache management, request batching, and operational utilities. Use when optimizing performance, managing cache, or diagnosing JIRA API issues.
Profile the Rust simulation engine to identify performance bottlenecks. Use when optimizing engine performance or investigating slow code paths.
Systematic debugging with root cause investigation. NO fixes without understanding cause first.
Identify and resolve performance bottlenecks through profiling, measurement, and targeted optimization.
MCP Response Analyzer pattern - Write large responses to temp files, load summaries into context
React Native best practices expert. PROACTIVELY use when working with React Native, mobile apps, Expo. Triggers: react-native, expo, mobile, iOS, Android, NativeWind
Use when analyzing code structure, researching codebase, investigating architecture, exploring dependencies, creating reports, auditing code quality, or when asked to проанализировать, исследовать, изучить, сос...
Master Bun runtime workflows for full-stack development. Monorepos, bunx, lockfiles, performance optimization, and integration patterns.
Investigate why code was written a certain way. Use when tracing decision history through git blame, commit logs, PRs, and issues to understand the reasoning behind code changes.
Use when encountering bugs, test failures, or unexpected behavior. Combines systematic debugging framework, root cause tracing, and defense-in-depth validation.
Use when exploring a codebase to understand structure, find files, check dependencies, or see recent changes. Provides verified commands for effective exploration.
TypeScript type safety patterns and best practices for maximum type coverage. Use when reviewing TypeScript code for type issues, eliminating `any` types, or when user mentions type safety, 型安全, 型カバレッジ...
Root cause analysis with 5 Whys methodology. Triggers: root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法.
Silent failure detection patterns for frontend code. Use when reviewing error handling, detecting swallowed errors, or when user mentions silent failure, empty catch, エラーハンドリング, 握りつぶし, swallowed e...
React and Next.js performance optimization guidelines from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js code, improving Web Vitals, or when user mentions React performance, Next...
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.