react-stinger — Claude Code skill: what it does, how to install
react-stinger audits React 18 and 19 architectures, pinpoints code anti-patterns, and delivers direct structural recommendations for Server Components and state layers.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install web-development-tools@wasp-nestWhat react-stinger 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.
What it helps with
- 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 for the agent
- 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.
How to install react-stinger
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install web-development-tools@wasp-nestThis installs the whole web-development-tools plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill react-stinger -a claude-code3Manually: put the files in place
~/.claude/skills/react-stinger/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/react-stinger/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill react-stinger -a codex2Manually: put the files in place
.agents/skills/react-stinger/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill react-stinger -a cursor2Manually: put the files in place
.cursor/skills/react-stinger/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/web-development-tools/skills/react-stinger2Manually: put the files in place
.github/skills/react-stinger/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill react-stinger -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/web-development-tools/skills/react-stingerManually: put the files in place
.devin/skills/react-stinger/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about react-stinger
How do I install react-stinger in Claude Code?
Register the catalog using /plugin marketplace add legioncodeinc/vibe-coding-tools, then install the package via /plugin install web-development-tools@wasp-nest.
What does react-stinger do?
It reviews React 18 and 19 architectures, evaluates data boundaries, and recommends specific refactoring steps grounded in established ecosystem guides.
How are code review findings prioritized?
Issues are categorized as must-fix defects, should-refactor debt, or optional style nits. Style comments are explicitly forbidden from blocking merges.