react-expert

Guidance for building modern React interfaces, where screens are composed from reusable JavaScript components. It covers React 18 and 19, hooks, component patterns, state management, performance, and Server Components.

In plain words
What is it for?
Use it when creating or refactoring React components, managing state, improving performance, or working with hooks, JSX, or Server Components.
Why use it?
It gives an agent focused context for common React design and implementation decisions. It can help when a component, hook, or state flow is difficult to structure or optimize.

Plugin for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code
/plugin marketplace add Miaoge-Ge/coding-agent-skills
agentmods
npx agentmods add plugins/miaoge-ge/coding-agent-skills/react-expert
Clone the repo
git clone --depth 1 https://github.com/Miaoge-Ge/coding-agent-skills

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin 86% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

react-expert scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

86% identical to github-master — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/react-expert/.claude-plugin/plugin.json · 13 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "react-expert",
  "displayName": "React Expert",
  "version": "1.0.0",
  "description": "Modern React (18/19): hooks, component patterns, state management, performance, and Server Components.",
  "author": { "name": "Miaoge-Ge", "email": "[email protected]" },
  "homepage": "https://github.com/Miaoge-Ge/coding-agent-skills",
  "repository": "https://github.com/Miaoge-Ge/coding-agent-skills",
  "license": "MIT",
  "keywords": ["react", "hooks", "jsx", "components", "state", "rsc"]
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 13 lines scan A ab54a281543d

Subscribe to this mod's changes

react-expert is a plugin published in the GitHub repository Miaoge-Ge/coding-agent-skills (5 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 86% identical to github-master, differing in 8 lines, and is treated as a copy.