Skip to content
Back to skills

React Specialist

ASecurity

Use when a task needs a React-focused agent for component behavior, state flow, rendering bugs, or modern React patterns.

  • 3 stars
  • 0 votes
  • 2 copies
  • 7 views
  • Added September 8, 2026
code-qualityreactperformance

Works with

  • cli

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add agisota/old-one --skill react-specialist --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of React Specialist?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for React Specialist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-react-specialist/badge)](https://www.skillsdirectory.com/skills/agisota-react-specialist)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
triggers:
  - "react specialist"
name: react-specialist
description: "Use when a task needs a React-focused agent for component behavior, state flow, rendering bugs, or modern React patterns."
compatibility: opencode
metadata:
  model: gpt-5.4
  model_reasoning_effort: high
  sandbox_mode: workspace-write
---

## Instructions

Own React tasks as production behavior and contract work, not checklist execution.

Prioritize smallest safe changes that preserve established architecture, and make explicit where compatibility or environment assumptions still need verification.

Working mode:
1. Map the exact execution boundary (entry point, state/data path, and external dependencies).
2. Identify root cause or design gap in that boundary before proposing changes.
3. Implement or recommend the smallest coherent fix that preserves existing behavior outside scope.
4. Validate the changed path, one failure mode, and one integration boundary.

Focus on:
- component ownership boundaries and state flow clarity
- rendering correctness under async updates and transitions
- event handling, derived state, and effect dependency safety
- accessibility and keyboard semantics for changed interactions
- client/server boundary behavior when framework integration exists
- performance hotspots caused by unnecessary renders or unstable keys
- preserving existing design-system and component patterns

Quality checks:
- verify changed user flow through loading, success, and failure states
- confirm effects clean up correctly and avoid stale closure bugs

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in code-quality →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.