Skip to content
Back to skills

React Tooling

ASecurity

Configure debugging, bundle analysis, and ecosystem tools for React applications. Use when setting up Vite/webpack build tooling, analyzing bundle size, debugging re-renders with React DevTools, or configuring ESLint and StrictMode for React projects.

  • 549 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added June 6, 2026
developmentreactdebugging

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned June 6, 2026

npx -y skills add HoangNguyen0403/agent-skills-standard --skill react-tooling --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of React Tooling?

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

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

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
---
name: react-tooling
description: Configure debugging, bundle analysis, and ecosystem tools for React applications. Use when setting up Vite/webpack build tooling, analyzing bundle size, debugging re-renders with React DevTools, or configuring ESLint and StrictMode for React projects.
metadata:
  triggers:
    files:
    - 'package.json'
    keywords:
    - devtool
    - bundle
    - strict mode
    - profile
---
# React Tooling

## **Priority: P2 (OPTIONAL)**

## Debugging Workflow

1. **Enable StrictMode** to catch side-effect bugs during development.
2. **Profile** with React DevTools Flamegraph to identify expensive components.
3. **Trace re-renders** using "Highlight Updates" or `why-did-you-render`.
4. **Analyze bundle** with `source-map-explorer` or `rollup-plugin-visualizer` before shipping.

## Setup

See [implementation examples](references/example.md#strictmode--why-did-you-render-setup) for StrictMode, why-did-you-render, and custom hook debug label setup.

## Implementation Guidelines

- **Analysis**: Use `source-map-explorer` or `webpack-bundle-analyzer` / `rollup-plugin-visualizer` (Vite).
- **Linting**: Mandate `eslint-plugin-react-hooks` (exhaustive-deps) and Prettier.
- **Environment**: Use Vite over CRA. Manage environment variables with `.env`.
- **Build**: Configure Terser for production minification. Use `vite-plugin-pwa` for service workers.

## Anti-Patterns

- **No production profiling**: Remove `why-did-you-render` and debug tools before production builds.
- **No skipping StrictMode**: Keep `<React.StrictMode>` in dev to surface side effects early.
- **No CRA for new projects**: Use Vite for faster builds and better DX.

Files in this skill

  • SKILL.md1.6 KB
  • evals/evals.json2 KB
  • references/example.md751 B

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.

Comments

Loading comments…

Newsletter

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