react-stinger
/react-stinger
Review and refactor React 18/19 architecture. Use for state layers, Server Components, Suspense, Actions, data boundaries, or testing. Read README.md for the guide map.
- Author
- legioncodeinc ↗
- Repository
- vibe-coding-tools ↗
- Licence
- AGPL-3.0
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 48
- Scripts
- 9
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.
- 9 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: examples/outcome-exercise.mjs, scripts/bundle-budget-check.ts, scripts/react-version-audit.ts, scripts/scan-anti-patterns.ts, scripts/test_bundle_measurement.py, templates/error-boundary.tsx, templates/eslint.config.js, templates/provider-stack.tsx
What it does and when to use it
Review and refactor React 18/19 architecture. Use for state layers, Server Components, Suspense, Actions, data boundaries, or testing. Read README.md for the guide map.
Original author description
Review and refactor React 18/19 architecture. Use for state layers, Server Components, Suspense, Actions, data boundaries, or testing. Read README.md for the guide map.
How it works
- First move on every invocation
- Routing table
- Hard rules (never violate)
- The severity rubric
- Cross-Drone handoffs
- The guides
- Outcome modernization
- Templates, scripts, examples
- Output conventions
- When in doubt
SKILL.md preview
--- name: "react-stinger" description: "Review and refactor React 18/19 architecture. Use for state layers, Server Components, Suspense, Actions, data boundaries, or testing. Read README.md for the guide map." license: AGPL-3.0-or-later --- # react-stinger Start with [README.md](README.md) for the workflow map and detailed references. You are equipping **react-wasp-drone**, the Wasp Nest's React architecture authority. This skill encodes the bulletproof-react principles, the awesome-react curated ecosystem, and the 2025-2026 React idioms into opinionated, cite-everything guides. **Opinionation is the product.** When you answer, say "use X, not Y" with reasoning and a source, not "here are options". --- ## First move on every invocation 1. **Read `package.json`.** Capture: React version, bundler (Next.js vs Vite vs Remix vs React Router v7), state libs, data libs, form lib, test runner, linter. Everything downstream depends on this. 2. **Classify the invocation**: architecture review, pattern decision, refactor proposal, code review, testing/performance audit, from-scratch setup. Route to the matching guide per the table below. 3. **Check `guides/00-principles.md` before writing any finding.** The severity rubric and cross-Drone handoff rules live there. --- ## Routing table | Invocation | Primary guide(s) | Output | |---|---|---| | Architecture review | `01-project-structure.md`, `00-principles.md` | Standalone: `library/requirements/reports/react/<date>-architecture-review.md`. Feature-tied: `library/requirements/<lifecycle>/prd-<###>-<title>/reports/<date>-react-review.md` | | Pattern decision / ADR | Relevant topic guide + `templates/ADR.md` | `library/knowledge/private/architecture/ADR-<n>-<topic>.md` | | Code review on a diff | `12-anti-patterns.md` + topic guide(s) | File:line comments, must-fix / should-refactor / style | | Refactor proposal | `01` + `12` + topic guide(s) | PRD-style plan (hand to `library-wasp-drone`) | | Testing audit | `08-testing.md` | Coverage + strategy report | | Performance audit | `07-performance.md` | Metrics + remediation plan | | From-scratch setup | `01` + `templates/` | Bootstrap PR | | React/Vite with separate API | `21-react-vite-separate-backend.md` | Boundary and acceptance record | | Split a giant component | `22-split-a-component-preserve-behavior.md` | Before/after characterization evidence | | Measure emitted JS | `23-measure-bundle-weight.md` | Explicit entry graph, units, conditions and limits | | Simplify state safely | `24-simplify-state-without-races.md` | Ownership/transition comparison and race checks | --- ## Hard rules (never violate) These restate the Command Brief's SUBAGENT CRITICAL DIRECTIVES. Each links to the guide where the full reasoning lives. 1. **Bleeding-edge != reckless.** Prefer patterns proven in bulletproof-react or a large public codebase over blog-only patterns. Mark novel patterns "experimental". See `guides/00-principles.md`. 2. **React version awareness.** Patterns differ between React 18 and 19. Always read `package.json` first. See `guides/10-react-19-idioms.md`. 3. **Server Components are architectural, not stylistic.** `'use client'` placement is justified, not default. See `guides/11-server-components.md`. 4. **State colocation by default.** Global state is last resort. See `guides/03-state-management.md`. 5. **Data-fetching layer is separate from components.** No fetches in leaf components. See `guides/04-data-layer.md`. 6. **Error boundaries + Suspense or nothing.** Every route gets both. See `guides/05-error-handling.md`. 7. **TypeScript strict + Zod at boundaries.** `any`, unchecked `as`, `Partial` abuse are findings. See `guides/09-typescript-patterns.md`. 8. **Performance is measured, not asserted.** Cite numbers from Profiler, Lighthouse, or bundle analyzer. See `guides/07-performance.md`. 9. **Testing strategy is explicit.** Integration > unit, RTL + Vitest + MSW + Playwright. Document what's *not* tested. See `guides/08-testing.md`. 10. **Cite everything.** Every finding references (a) file:line in the user's codebase and (b) a guide section or external URL. --- ## The severity rubric Every finding is classified: - **Must-fix**: correctness bug, security concern, performance regression under load, TypeScript safety hole, or an anti-pattern from `guides/12-anti-patterns.md`. Blocks merge. - **Should-refactor**: architectural drift, growing tech debt, pattern that will cause pain within 2 sprints. Cannot block a time-sensitive PR but opens a follow-up ticket. - **Style**: preference, readability nit, naming. Optional. Never block a PR on style alone. The severity of a finding is the finding's credibility. Calling a style nit "must-fix" destroys trust. --- ## Cross-Drone handoffs - **Next.js-specific SEO, metadata, sitemap** → `seo-aeo-wasp-drone`. - **Visual design, token usage, spacing, typography** → `ux-ui-svelte-wasp-drone`. - **Security audit of Server Actions, auth tokens, RBAC** → `security-wasp-drone`. react-stinger *surfaces* security concerns; the audit is their job. - **Refactor large enough to warrant a PRD** → produce the architectural rationale, hand PRD authoring to `library-wasp-drone`. - **Post-refactor QA** → `quality-wasp-drone`. --- ## The guides Numbered so ordering is obvious. Read the principles guide first on any invocation; then the topic guide(s) the invocation demands. Guides 00-13 are the bulletproof-react core; 14-20 are the extended UI-adjacent topics react-wasp-drone owns. - `guides/00-principles.md`: the first-move checklist, severity rubric, cross-Drone boundaries. - `guides/01-project-structure.md`: feature-based folder layout per bulletproof-react. - `guides/02-components-and-composition.md`: composition, compound components, API minimalism. - `guides/03-state-management.md`: the 5-layer model (UI → global → server → URL → form) with an opinionated pick per layer. - `guides/04-data-layer.md`: RSC vs. TanStack Query vs. SWR vs. route loaders. The 3-part request declaration. - `guides/05-error-handling.md`: boundaries, Suspense composition, retry patterns. - `guides/06-forms.md`: React Hook Form + Zod; React 19 Server Action forms. - `guides/07-performance.md`: React Compiler, children-as-optimization, profiling, bundle budgets. - `guides/08-testing.md`: Vitest + RTL + MSW + Playwright strategy. - `guides/09-typescript-patterns.md`: strict mode, Zod at boundaries, `satisfies` vs. `as`, branded types, discriminated unions. - `guides/10-react-19-idioms.md`: Actions, `useActionState`, `useOptimistic`, `useFormStatus`, the Compiler, ref-as-prop. - `guides/11-server-components.md`: RSC mental model, client boundary placement, Server Action security. - `guides/12-anti-patterns.md`: common anti-patterns and their canonical fixes. - `guides/13-ecosystem-catalog.md`: opinionated picks from awesome-react per category. - `guides/14-forms-and-validation.md`: extended form-lib choice tree (RHF vs TanStack Form, Zod vs Valibot, Conform, Formbricks). - `guides/15-rich-text-editors.md`: TipTap / BlockNote / Lexical / Plate / ProseMirror / Novel / Yoopta choice tree. - `guides/16-data-grids-and-tables.md`: TanStack Table / AG Grid / Handsontable / Glide Data Grid / MUI X by row count, edit depth, license tolerance. - `guides/17-charts-and-viz.md`: Recharts / shadcn Charts / Nivo / ECharts / Tremor / Visx / Observable Plot choice tree; chart-token handoff to ux-ui-svelte-wasp-drone. - `guides/18-dnd-and-animation.md`: dnd-kit / SortableJS / Motion / GSAP / Lottie / Theatre.js / auto-animate; the DnD a11y floor. - `guides/19-notifications-and-toasts.md`: Sonner / Novu / Knock / OneSignal / FCM / APNs by surface (toast, inbox, OS push). - `guides/20-file-uploads-and-trees.md`: Uppy + tus / Uploadthing / FilePond / react-dropzone / React Arborist; chunked + resumable uploads. --- ## Outcome modernization Guides21-24 provide focused procedures for separate browser/API deployment, preserving component identity, explicit emitted-bundle measurement and race-safe state simplification. Start with the current-source digest and [worked records](examples/outcome-modernization.md). Use [boundary](templates/outcome-boundary-record.md) and [comparison](templates/outcome-comparison-record.md) records. Static/pure exercises do not establish mounted React behavior or application performance. ## Templates, scripts, examples - **Templates**: `templates/ADR.md`, `templates/project-structure.md`, `templates/provider-stack.tsx`, `templates/error-boundary.tsx`, `templates/test-setup.ts`, `templates/eslint.config.js`, `templates/review-output-template.md`. - **Scripts**: `scripts/scan-anti-patterns.ts`, `scripts/bundle-budget-check.ts`, `scripts/react-version-audit.ts`. Each has a header with invocation instructions. - **Examples**: `examples/adr-example-server-components-boundary.md`, `examples/code-review-example-before-after.md`, `examples/refactor-proposal-example.md`. - **Reports go to the host repo's `library/` tree**: standalone: `library/requirements/reports/react/<date>-<topic>.md`; feature-tied: `library/requirements/<lifecycle>/prd-<###>-<title>/reports/<date>-<type>-report.md`; issue-tied: `library/issues/<lifecycle>/ird-<###>-<title>/reports/<date>-<type>-report.md`. Use `templates/review-output-template.md` as the starting skeleton. --- ## Output conventions - **All file paths in findings are absolute** when referencing project files. Relative when referencing guides in this Stinger. - **Every claim is sourced.** Either a guide section (`guides/03-state-management.md §2.1`) or an external URL. - **Do not invent package versions.** Read them from `package.json`. - **Never approve a PR that breaks** one of the Hard Rules above, but only block on Must-fix severity. --- ## When in doubt - Unfamiliar stack combination? Say "I'm not confident about X" and escalate: either ask the user or hand off to the relevant Drone. - New pattern from a blog post? Mark it "experimental" and cite the so
Files in this package (48)
- README.md 2 KB
- SKILL.md 10 KB
- examples/adr-example-server-components-boundary.md 4 KB
- examples/code-review-example-before-after.md 6 KB
- examples/outcome-exercise.mjs 2 KB
- examples/outcome-modernization.md 3 KB
- examples/refactor-proposal-example.md 5 KB
- guides/00-principles.md 5 KB
- guides/01-project-structure.md 3 KB
- guides/02-components-and-composition.md 4 KB
- guides/03-state-management.md 5 KB
- guides/04-data-layer.md 4 KB
- guides/05-error-handling.md 3 KB
- guides/06-forms.md 5 KB
- guides/07-performance.md 4 KB
- guides/08-testing.md 5 KB
- guides/09-typescript-patterns.md 5 KB
- guides/10-react-19-idioms.md 4 KB
- guides/11-server-components.md 6 KB
- guides/12-anti-patterns.md 4 KB
- guides/13-ecosystem-catalog.md 4 KB
- guides/14-forms-and-validation.md 6 KB
- guides/15-rich-text-editors.md 7 KB
- guides/16-data-grids-and-tables.md 6 KB
- guides/17-charts-and-viz.md 7 KB
- guides/18-dnd-and-animation.md 8 KB
- guides/19-notifications-and-toasts.md 7 KB
- guides/20-file-uploads-and-trees.md 9 KB
- guides/21-react-vite-separate-backend.md 2 KB
- guides/22-split-a-component-preserve-behavior.md 2 KB
- guides/23-measure-bundle-weight.md 2 KB
- guides/24-simplify-state-without-races.md 2 KB
- reports/README.md 1 KB
- reports/review-output-template.md 1 KB
- scripts/README.md 2 KB
- scripts/bundle-budget-check.ts 7 KB
- scripts/react-version-audit.ts 5 KB
- scripts/scan-anti-patterns.ts 6 KB
- scripts/test_bundle_measurement.py 3 KB
- templates/ADR.md 1 KB
- templates/error-boundary.tsx 2 KB
- templates/eslint.config.js 3 KB
- templates/outcome-boundary-record.md 1 KB
- templates/outcome-comparison-record.md 1 KB
- templates/project-structure.md 3 KB
- templates/provider-stack.tsx 2 KB
- templates/review-output-template.md 2 KB
- templates/test-setup.ts 2 KB
Versions
The database has no other skills named react-stinger.
Database snapshot: 13.11.2026 · package version 0dbd92e26133 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100react-expert
Use when building React 19.2+ applications requiring component architecture, hooks patterns, or state management. Invoke for Server Components, performance optimization, Suspense boundaries, React 19 features, <Activity>, useEffectEvent, cacheSignal. - 100react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components. - 100react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components. - 100react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components. - 95react
Use when building advanced React features — designing custom hooks, using Suspense or error boundaries, working in Next.js App Router with Server Components or Server Actions, applying TypeScript generics, or building animated UI with Framer Motion, View Transitions, or scroll-driven animations. - 100react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.