reviewing-frontend-code
Reviews React and Next.js code for performance, accessibility, security, and adherence to project standards. Use when asked to review frontend PRs or components.
Découvrez les skills data ai debugging, comparez leurs dépôts et consultez leurs instructions.
Reviews React and Next.js code for performance, accessibility, security, and adherence to project standards. Use when asked to review frontend PRs or components.
Provides guidance on React design patterns like Composition, Render Props, and Custom Hooks. Use when architecting complex UI components.
Comprehensive code review with best practices, security, and maintainability checks. Use when reviewing pull requests, pre-commit code checks, learning code review techniques, improving code quality, or perform...
When reviewing coding test solutions. This Skill reviews coding test solutions and provides feedback. it adds an evaluation section to the README.md file in the problem-solving folder, including areas for impro...
Optimize API performance, database queries, caching, and profiling. Use when improving system performance to meet
Generate high-quality code in various programming languages following best practices. Use when the user asks to write, create, or generate code, functions, classes, or scripts.
Optimize API performance, database queries, caching, and profiling. Use when improving system performance to meet
Optimize API performance, database queries, caching, and profiling. Use when improving system performance to meet
Structured problem-solving workflow for debugging. Use after 3 failed attempts at solving an issue, when stuck on a problem, or when encountering repeated errors.
Analyze and improve database performance through safe, measurable query, index, and configuration optimizations.
Expert TypeScript development with advanced type safety, full-stack patterns, and build optimization. Use when designing or refactoring TypeScript, auditing type safety, or improving TS tooling and compile perf...
Structured code debugging through hypothesis formation and falsification planning. Use when diagnosing bugs, unexpected behaviour, or system failures where the root cause is unclear. Produces a hypothesis docum...
Complete guide to using Chrome DevTools MCP server for browser automation with Claude Code
Four-phase root cause analysis process to find bugs 10x faster
Four-phase root cause analysis process to find bugs 10x faster
Skill for hunting flaky tests and race conditions by running specific tests multiple times.
Automatic code quality and best practices analysis. Use proactively when files are modified, saved, or committed. Analyzes code style, patterns, potential bugs, and security basics. Triggers on file changes, gi...
[31] ANALYZE. Universal deep thinking methodology for any situation requiring quality reasoning. Use when solving problems, debugging, making decisions, analyzing code, planning, reviewing, or anytime you need...
[30] ANALYZE. Understand how changes impact the system — what's the core, what's affected, what depends on what. Use when planning changes, analyzing systems, debugging issues, or anytime you need to see the fu...
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/Vi...
Systematically debug and fix bugs through triage, reproduction, root cause analysis, and verified fixes. Use when asked to fix a bug, debug an issue, investigate a problem, or resolve an error.
Explores and maps Zalo Mini App codebases. Use when asked to understand project structure, find features, audit zmp-sdk/zmp-ui usage, or analyze a ZMP codebase.
Review code for best practices, bugs, and security issues. Use when the user asks to review code, check for problems, or analyze code quality.
Audits UI code for accessibility, performance, and UX compliance. Use when reviewing components, checking accessibility, or validating UI before shipping.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.