react_skill

This skill analyzes React code against best practices for hooks, state, performance, accessibility, testing, and design patterns to improve reliability.
  • Python

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill yldgio/codereview-skills --skill react

  • SKILL.md4.3 KB

Overview

This skill captures practical React component patterns, hooks best practices, state management guidance, and performance optimization rules for building robust, maintainable UIs. It focuses on secure rendering, predictable hooks usage, accessible semantics, and scalable component design. The guidance is actionable and geared toward everyday developer workflows and code reviews.

How this skill works

The skill inspects common React pitfalls and prescribes concrete rules: sanitize user input, enforce hook discipline, prefer local and derived state, and apply memoization where needed. It also recommends accessibility standards, testing strategies, error handling, type safety, styling conventions, dependency hygiene, and documentation practices. Use it as a checklist during development, pull request reviews, or when designing reusable components and hooks.

When to use it

  • During code reviews to catch security, hooks, and performance issues
  • When designing new components, hooks, or state management solutions
  • Refactoring to reduce re-renders or remove redundant state
  • Onboarding developers to a React codebase or establishing team conventions
  • Prioritizing accessibility and testing before release

Best practices

  • Never render untrusted input directly; sanitize or escape to prevent XSS
  • Call hooks only at the top level; name custom hooks with a use prefix
  • Keep state local when possible; derive values instead of storing them
  • Use useMemo and useCallback to stabilize expensive computations and callbacks
  • Prefer composition and controlled components; avoid deep prop drilling

Example use cases

  • Reviewing a component that accepts rich user content to ensure proper sanitization
  • Refactoring a form to use controlled inputs and useReducer for complex logic
  • Optimizing a frequently re-rendered list with React.memo and stable props
  • Designing a compound component (parent + stateless children) for a complex widget
  • Adding tests for custom hooks and key user interactions using testing-library

FAQ

Use useReducer when state has multiple related sub-values or update logic that benefits from a centralized reducer and clearer action semantics.

How do I decide between Context and prop drilling?

Avoid prop drilling beyond two levels. Use Context for cross-cutting concerns like theme or auth, and co-locate provider logic with domain-specific hooks to keep usage explicit and testable.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational