Back to React & React Native

react-modernization

ReactHooksModernizationUpgradeClass ComponentsConcurrent ReactCodemodsFrontend
⭐ 36.8kπŸ“„ MITπŸ•’ 2026-06-16Source β†—

Install this skill

npx skills add wshobson/agents

Works across Claude Code, Cursor, Codex, Copilot & Antigravity

The React modernization skill manages the technical debt inherent in legacy React codebases by automating transitions to modern standards. It focuses on shifting from class-based components to functional components using hooks like useState and useEffect. The skill orchestrates version upgrades, specifically managing breaking changes introduced between React 16 and 18, such as the transition to the createRoot API and the removal of event pooling. It handles the refactoring of higher-order components into custom hooks and streamlines state management through context updates. By applying codemods and resolving lifecycle complexities, this skill updates legacy structures to support React 18 features like automatic batching and concurrent rendering, ensuring high performance while maintaining functional parity with the original codebase.

When to Use This Skill

  • β€’Upgrading an legacy enterprise React 16 application to React 18
  • β€’Replacing complex class-based lifecycle logic with cleaner hook-based functions
  • β€’Refactoring deep component trees to utilize modern Context API patterns
  • β€’Optimizing rendering performance by enabling React 18 concurrent features

How to Invoke This Skill

Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:

  • β€œMigrate this class component to functional style
  • β€œRefactor this legacy lifecycle code into useEffect
  • β€œUpgrade my React 16 project to version 18
  • β€œConvert this HOC to a custom hook
  • β€œUpdate my app to use the React 18 root API

Pro Tips

  • πŸ’‘Always upgrade React versions incrementally (e.g., 16 β†’ 17 β†’ 18) to isolate breaking changes and simplify debugging.
  • πŸ’‘Prioritize migrating complex, stateful class components to hooks first, as this often reveals opportunities for better state management and reusability.
  • πŸ’‘Leverage the React Strict Mode during development after an upgrade to identify potential issues related to concurrent features and side effects early.

What this skill does

  • β€’Automatic migration from class components to functional components
  • β€’Conversion of lifecycle methods like componentDidMount to useEffect patterns
  • β€’Implementation of the React 18 createRoot rendering API
  • β€’Refactoring higher-order components and render props into custom hooks
  • β€’Configuration of JSX transforms to eliminate explicit React imports

When not to use it

  • βœ•Projects requiring legacy browser support incompatible with React 18
  • βœ•Extremely small, static components that do not justify refactoring effort

Example workflow

  1. Analyze the current React version and dependency tree
  2. Run standard codemods to handle global JSX transformations
  3. Systematically refactor individual class components into functional components
  4. Replace componentDidUpdate and componentWillUnmount with cleanup-aware hooks
  5. Update entry point to use createRoot and verify concurrent rendering

Prerequisites

  • –Existing React codebase
  • –Defined unit tests for regression verification

Pitfalls & limitations

  • !Incorrect cleanup function logic in useEffect can cause memory leaks
  • !Over-reliance on automatic codemods can lead to non-idiomatic hook code
  • !React 18 strict mode double-invocations can expose hidden side effects in legacy code

FAQ

Why do my components trigger twice in React 18?
Strict Mode causes double-invocation of functional components in development to help you identify side effects that are not properly cleaned up.
Do I need to change my JSX after upgrading?
React 17 and later include a new JSX transform that allows you to omit importing React in every file.
How does automatic batching affect my state updates?
React 18 automatically groups multiple state updates into a single re-render, even inside asynchronous blocks like timeouts or promises.

How it compares

Generic prompts often fail to handle the edge cases of lifecycle cleanup or async state synchronization, whereas this skill applies specific patterns for hook-based refactoring that preserve state integrity.

Source & trust

⭐ 37k starsπŸ“„ MITπŸ•’ Updated 2026-06-16
πŸ“„ Full skill instructions β€” original source: wshobson/agents
# React Modernization

Master React version upgrades, class to hooks migration, concurrent features adoption, and codemods for automated transformation.

## When to Use This Skill

- Upgrading React applications to latest versions
- Migrating class components to functional components with hooks
- Adopting concurrent React features (Suspense, transitions)
- Applying codemods for automated refactoring
- Modernizing state management patterns
- Updating to TypeScript
- Improving performance with React 18+ features

## Version Upgrade Path

### React 16 β†’ 17 β†’ 18

**Breaking Changes by Version:**

**React 17:**

- Event delegation changes
- No event pooling
- Effect cleanup timing
- JSX transform (no React import needed)

**React 18:**

- Automatic batching
- Concurrent rendering
- Strict Mode changes (double invocation)
- New root API
- Suspense on server

## Class to Hooks Migration

### State Management

// Before: Class component
class Counter extends React.Component {
constructor(props) {
super(props);
this.state = {
count: 0,
name: "",
};
}

increment = () => {
this.setState({ count: this.state.count + 1 });
};

render() {
return (
<div>
<p>Count: {this.state.count}</p>
<button onClick={this.increment}>Increment</button>
</div>
);
}
}

// After: Functional component with hooks
function Counter() {
const [count, setCount] = useState(0);
const [name, setName] = useState("");

const increment = () => {
setCount(count + 1);
};

return (
<div>
<p>Count: {count}</p>
<button onClick={increment}>Increment</button>
</div>
);
}


### Lifecycle Methods to Hooks

// Before: Lifecycle methods
class DataFetcher extends React.Component {
state = { data: null, loading: true };

componentDidMount() {
this.fetchData();
}

componentDidUpdate(prevProps) {
if (prevProps.id !== this.props.id) {
this.fetchData();
}
}

componentWillUnmount() {
this.cancelRequest();
}

fetchData = async () => {
const data = await fetch(/api/${this.props.id});
this.setState({ data, loading: false });
};

cancelRequest = () => {
// Cleanup
};

render() {
if (this.state.loading) return <div>Loading...</div>;
return <div>{this.state.data}</div>;
}
}

// After: useEffect hook
function DataFetcher({ id }) {
const [data, setData] = useState(null);
const [loading, setLoading] = useState(true);

useEffect(() => {
let cancelled = false;

const fetchData = async () => {
try {
const response = await fetch(/api/${id});
const result = await response.json();

if (!cancelled) {
setData(result);
setLoading(false);
}
} catch (error) {
if (!cancelled) {
console.error(error);
}
}
};

fetchData();

// Cleanup function
return () => {
cancelled = true;
};
}, [id]); // Re-run when id changes

if (loading) return <div>Loading...</div>;
return <div>{data}</div>;
}


### Context and HOCs to Hooks

// Before: Context consumer and HOC
const ThemeContext = React.createContext();

class ThemedButton extends React.Component {
static contextType = ThemeContext;

render() {
return (
<button style={{ background: this.context.theme }}>
{this.props.children}
</button>
);
}
}

// After: useContext hook
function ThemedButton({ children }) {
const { theme } = useContext(ThemeContext);

return <button style={{ background: theme }}>{children}</button>;
}

// Before: HOC for data fetching
function withUser(Component) {
return class extends React.Component {
state = { user: null };

componentDidMount() {
fetchUser().then((user) => this.setState({ user }));
}

render() {
return <Component {...this.props} user={this.state.user} />;
}
};
}

// After: Custom hook
function useUser() {
const [user, setUser] = useState(null);

useEffect(() => {
fetchUser().then(setUser);
}, []);

return user;
}

function UserProfile() {
const user = useUser();
if (!user) return <div>Loading...</div>;
return <div>{user.name}</div>;
}


## React 18 Concurrent Features

### New Root API

// Before: React 17
import ReactDOM from "react-dom";

ReactDOM.render(<App />, document.getElementById("root"));

// After: React 18
import { createRoot } from "react-dom/client";

const root = createRoot(document.getElementById("root"));
root.render(<App />);


### Automatic Batching

// React 18: All updates are batched
function handleClick() {
setCount((c) => c + 1);
setFlag((f) => !f);
// Only one re-render (batched)
}

// Even in async:
setTimeout(() => {
setCount((c) => c + 1);
setFlag((f) => !f);
// Still batched in React 18!
}, 1000);

// Opt out if needed
import { flushSync } from "react-dom";

flushSync(() => {
setCount((c) => c + 1);
});
// Re-render happens here
setFlag((f) => !f);
// Another re-render


### Transitions

import { useState, useTransition } from "react";

function SearchResults() {
const [query, setQuery] = useState("");
const [results, setResults] = useState([]);
const [isPending, startTransition] = useTransition();

const handleChange = (e) => {
// Urgent: Update input immediately
setQuery(e.target.value);

// Non-urgent: Update results (can be interrupted)
startTransition(() => {
setResults(searchResults(e.target.value));
});
};

return (
<>
<input value={query} onChange={handleChange} />
{isPending && <Spinner />}
<Results data={results} />
</>
);
}


### Suspense for Data Fetching

import { Suspense } from "react";

// Resource-based data fetching (with React 18)
const resource = fetchProfileData();

function ProfilePage() {
return (
<Suspense fallback={<Loading />}>
<ProfileDetails />
<Suspense fallback={<Loading />}>
<ProfileTimeline />
</Suspense>
</Suspense>
);
}

function ProfileDetails() {
// This will suspend if data not ready
const user = resource.user.read();
return <h1>{user.name}</h1>;
}

function ProfileTimeline() {
const posts = resource.posts.read();
return <Timeline posts={posts} />;
}


## Codemods for Automation

### Run React Codemods

# Install jscodeshift
npm install -g jscodeshift

# React 16.9 codemod (rename unsafe lifecycle methods)
npx react-codeshift <transform> <path>

# Example: Rename UNSAFE_ methods
npx react-codeshift --parser=tsx \
--transform=react-codeshift/transforms/rename-unsafe-lifecycles.js \
src/

# Update to new JSX Transform (React 17+)
npx react-codeshift --parser=tsx \
--transform=react-codeshift/transforms/new-jsx-transform.js \
src/

# Class to Hooks (third-party)
npx codemod react/hooks/convert-class-to-function src/


### Custom Codemod Example

// custom-codemod.js
module.exports = function (file, api) {
const j = api.jscodeshift;
const root = j(file.source);

// Find setState calls
root
.find(j.CallExpression, {
callee: {
type: "MemberExpression",
property: { name: "setState" },
},
})
.forEach((path) => {
// Transform to useState
// ... transformation logic
});

return root.toSource();
};

// Run: jscodeshift -t custom-codemod.js src/


## Performance Optimization

### useMemo and useCallback

function ExpensiveComponent({ items, filter }) {
// Memoize expensive calculation
const filteredItems = useMemo(() => {
return items.filter((item) => item.category === filter);
}, [items, filter]);

// Memoize callback to prevent child re-renders
const handleClick = useCallback((id) => {
console.log("Clicked:", id);
}, []); // No dependencies, never changes

return <List items={filteredItems} onClick={handleClick} />;
}

// Child component with memo
const List = React.memo(({ items, onClick }) => {
return items.map((item) => (
<Item key={item.id} item={item} onClick={onClick} />
));
});


### Code Splitting

import { lazy, Suspense } from "react";

// Lazy load components
const Dashboard = lazy(() => import("./Dashboard"));
const Settings = lazy(() => import("./Settings"));

function App() {
return (
<Suspense fallback={<Loading />}>
<Routes>
<Route path="/dashboard" element={<Dashboard />} />
<Route path="/settings" element={<Settings />} />
</Routes>
</Suspense>
);
}


## TypeScript Migration

// Before: JavaScript
function Button({ onClick, children }) {
return <button onClick={onClick}>{children}</button>;
}

// After: TypeScript
interface ButtonProps {
onClick: () => void;
children: React.ReactNode;
}

function Button({ onClick, children }: ButtonProps) {
return <button onClick={onClick}>{children}</button>;
}

// Generic components
interface ListProps<T> {
items: T[];
renderItem: (item: T) => React.ReactNode;
}

function List<T>({ items, renderItem }: ListProps<T>) {
return <>{items.map(renderItem)}</>;
}


## Migration Checklist

### Pre-Migration

- [ ] Update dependencies incrementally (not all at once)
- [ ] Review breaking changes in release notes
- [ ] Set up testing suite
- [ ] Create feature branch

### Class β†’ Hooks Migration

- [ ] Identify class components to migrate
- [ ] Start with leaf components (no children)
- [ ] Convert state to useState
- [ ] Convert lifecycle to useEffect
- [ ] Convert context to useContext
- [ ] Extract custom hooks
- [ ] Test thoroughly

### React 18 Upgrade

- [ ] Update to React 17 first (if needed)
- [ ] Update react and react-dom to 18
- [ ] Update @types/react if using TypeScript
- [ ] Change to createRoot API
- [ ] Test with StrictMode (double invocation)
- [ ] Address concurrent rendering issues
- [ ] Adopt Suspense/Transitions where beneficial

### Performance

- [ ] Identify performance bottlenecks
- [ ] Add React.memo where appropriate
- [ ] Use useMemo/useCallback for expensive operations
- [ ] Implement code splitting
- [ ] Optimize re-renders

### Testing

- [ ] Update test utilities (React Testing Library)
- [ ] Test with React 18 features
- [ ] Check for warnings in console
- [ ] Performance testing


## Resources

- **references/breaking-changes.md**: Version-specific breaking changes
- **references/codemods.md**: Codemod usage guide
- **references/hooks-migration.md**: Comprehensive hooks patterns
- **references/concurrent-features.md**: React 18 concurrent features
- **assets/codemod-config.json**: Codemod configurations
- **assets/migration-checklist.md**: Step-by-step checklist
- **scripts/apply-codemods.sh**: Automated codemod script

## Best Practices

1. **Incremental Migration**: Don't migrate everything at once
2. **Test Thoroughly**: Comprehensive testing at each step
3. **Use Codemods**: Automate repetitive transformations
4. **Start Simple**: Begin with leaf components
5. **Leverage StrictMode**: Catch issues early
6. **Monitor Performance**: Measure before and after
7. **Document Changes**: Keep migration log

## Common Pitfalls

- Forgetting useEffect dependencies
- Over-using useMemo/useCallback
- Not handling cleanup in useEffect
- Mixing class and functional patterns
- Ignoring StrictMode warnings
- Breaking change assumptions

How to Use This Skill Unit

Option A: Project-Specific (Recommended)

  1. Click "Download" above
  2. In your project, create the directory: .agent/skills/react-modernization/
  3. Save the file as SKILL.md
  4. The agent will automatically discover the skill based on its description.

Option B: Global Installation (All Agents)

Save the file to these locations to make it available across all projects:

  • Claude Code: ~/.claude/skills/wshobson/agents/react-modernization/SKILL.md
  • Cursor: ~/.cursor/skills/wshobson/agents/react-modernization/SKILL.md
  • Antigravity: ~/.gemini/antigravity/skills/wshobson/agents/react-modernization/SKILL.md

πŸš€ Install with CLI:
npx skills add wshobson/agents

Read the Master Guide: Mastering Agent Skills β†’

Recommended Rules

View more rules β†’

Recommended Workflows

View more workflows β†’

Recommended MCP Servers

View more MCP servers β†’

Take It Further

Maximize your productivity with these powerful resources

πŸ“‹

Define Your Standards

Set up coding standards to ensure this workflow produces consistent, high-quality results.

Browse Rules Library
πŸ“–

Master Workflows

Learn how to create custom workflows, use Turbo Mode, and build your automation library.

Complete Guide

How to use this Skill in Claude Code & Cursor

For Claude Code (CLI)

To use this skill in Claude Code, copy the rule content into your project's custom instructions or follow our Add-Skill CLI guide. This ensures Claude follows your standards during every code generation.

For Cursor & Windsurf

For Cursor or Windsurf, individual skills are best used in the "Rules for AI" section. This specific unit helps the agent avoid react & react native issues, leading to cleaner, more efficient code.

Why the skill format matters: the standardized Agent Skills format lets your AI agent load detailed instructions only when they are relevant, keeping your prompt clean while improving results.

Source & attribution

This skill is categorized under React & React Native and is published by W. Shobson, maintained in wshobson/agents.

← Browse All Agent Skills
Sponsored AI assistant. Recommendations may be paid.