# react-stinger

react-stinger audits React 18 and 19 architectures, pinpoints code anti-patterns, and delivers direct structural recommendations for Server Components and state layers.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 96 repo stars
- Author: Legion Code Inc.
- License: AGPL-3.0-or-later · policy=link-only · description only; the file stays with the author
- Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/web-development-tools/skills/react-stinger/SKILL.md
- Updated: 2026-10-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/react-stinger

## What it does

This skill acts as a strict architectural reviewer for React codebases. Instead of offering ambiguous lists of options, it insists on explicit choices backed by clear reasoning. Every run starts with `package.json`. It identifies your React version and bundler. Without an intact `package.json`, the assistant cannot ground its evaluation in your stack.

The workflow builds on bulletproof-react structure alongside modern React 19 patterns. It enforces isolated data fetching, inspects `'use client'` placement, and checks error boundaries across routes. Every finding receives a strict severity label. Correctness bugs and security oversights block integration, while style preferences stay strictly non-blocking.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add legioncodeinc/vibe-coding-tools
```
In the agent chat (not a shell):
```text
/plugin install web-development-tools@wasp-nest
```
This installs the whole web-development-tools plugin with all its skills

2. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill react-stinger -a claude-code
```

3. **Manually: put the files in place**
- File: `~/.claude/skills/react-stinger/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/react-stinger/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill react-stinger -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/react-stinger/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill react-stinger -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/react-stinger/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install legioncodeinc/vibe-coding-tools plugins/web-development-tools/skills/react-stinger
```

2. **Manually: put the files in place**
- File: `.github/skills/react-stinger/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill react-stinger -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/web-development-tools/skills/react-stinger
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/react-stinger/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/web-development-tools/skills/react-stinger/SKILL.md

## When to use it
- catch architectural anti-patterns before merging branches
- enforce strict boundaries around Server Components
- organize state layers according to explicit ownership
- formulate an integration testing plan for Vitest and Playwright

## Example prompts
- Review our project layout and flag architectural flaws in this pull request.
- Inspect our Server Component boundaries before upgrading to React 19.
- Draft a refactoring plan to break down this large component safely.

## Similar
- [react-best-practices](https://affpapa.org/en/nevibecode/skills/mastra-ai-react-best-practices.md) — skill · 2900 installs
- [react-router-code-review](https://affpapa.org/en/nevibecode/skills/react-router-code-review.md) — skill · 202 installs
- [typescript-react-reviewer](https://affpapa.org/en/nevibecode/skills/typescript-react-reviewer.md) — skill · 9000 installs
- [react-code-review](https://affpapa.org/en/nevibecode/skills/react-code-review.md) — skill · 4600 installs
- [narrow-react-prop-types](https://affpapa.org/en/nevibecode/skills/narrow-react-prop-types.md) — skill · 1500 installs
- [react-flow-code-review](https://affpapa.org/en/nevibecode/skills/react-flow-code-review.md) — skill · 329 installs

From the same set: [legioncodeinc/vibe-coding-tools](https://affpapa.org/en/nevibecode/by/legioncodeinc/vibe-coding-tools.md) — 172 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
