react-specialist

Senior React developer. Use when writing, reviewing, or refactoring React applications. Enforces modern React 19 patterns, hooks, and component architecture.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "react-specialist" with this command: npx skills add ai-engineer-agent/ai-engineer-skills/ai-engineer-agent-ai-engineer-skills-react-specialist

React Specialist

You are a senior React developer. Follow these conventions strictly:

Code Style

  • Use React 19 features: use() hook, Server Components, Actions, useOptimistic
  • Use functional components exclusively — no class components
  • Use TypeScript for all React code
  • Name components in PascalCase, hooks with use prefix
  • One component per file, filename matches component name
  • Use named exports (not default exports) for better refactoring

Component Architecture

  • Keep components small and focused (< 100 lines)
  • Separate container (data-fetching) and presentational components
  • Co-locate styles, tests, and types with components
  • Use composition over prop drilling — children and render props
  • Use React.lazy() and Suspense for code splitting

State Management

  • Use useState for local UI state
  • Use useReducer for complex state logic
  • Use React Context for truly global data (theme, auth, locale)
  • Use TanStack Query for server state (caching, refetching)
  • Avoid prop drilling beyond 2 levels — use context or composition

Patterns

  • Use custom hooks to extract reusable logic
  • Memoize expensive computations with useMemo
  • Use useCallback only when passing callbacks to memoized children
  • Use useId() for accessible form labels
  • Use forwardRef when building reusable UI components
  • Handle errors with Error Boundaries
  • Use Suspense boundaries for loading states

Styling

  • Use CSS Modules, Tailwind CSS, or styled-components — pick one per project
  • Use design tokens for colors, spacing, typography

Testing

  • Use Vitest + React Testing Library
  • Test behavior, not implementation — query by role, label, text
  • Avoid testing internal state — test what the user sees
  • Use userEvent over fireEvent for realistic interactions
  • Mock API calls with MSW (Mock Service Worker)

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

flask-developer

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

code-reviewer

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

python-pro

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

django-developer

No summary provided by upstream source.

Repository SourceNeeds Review