react

Enforces functional React components with typed props and naming conventions.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/0r0loo/my-claude-code-toolkit --skill react-0r0loo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react
Source: https://github.com/0r0loo/my-claude-code-toolkit/tree/main/.claude/skills/React
Command: npx skills add https://github.com/0r0loo/my-claude-code-toolkit --skill react-0r0loo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide and set of rules for designing and developing React components, ensuring consistency, maintainability, and adherence to best practices.

Core Features & Use Cases

  • Component Design Principles: Enforces functional components, explicit prop typing, Single Responsibility Principle, and size limits.
  • Prop Design Guidelines: Promotes minimal props, clear callback naming, and avoiding passing entire objects unnecessarily.
  • Naming Conventions: Standardizes naming for components, hooks, utilities, and event handlers.
  • Prohibited Practices: Lists common anti-patterns and anti-practices to avoid in React development.
  • Use Case: When building a new feature with React, consult this Skill to ensure all new components are structured correctly, props are managed efficiently, and naming conventions are followed, leading to a cleaner and more scalable codebase.

Quick Start

Follow the React Skill's guidelines to create a new functional component named UserProfile that accepts name and avatarUrl as props.

Frequently Asked Questions about react

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best practices for structuring React components and props?

React functional components require explicit prop typing, single responsibility adherence, and standardized naming conventions for hooks and event handlers. This combination enforces maintainable and scalable frontend development by prohibiting anti-patterns like `any` types, inline styles, and improper `useEffect` usage.

How do I avoid common anti-patterns when using React hooks and useEffect?

To avoid anti-patterns when using React hooks and useEffect, enforce functional component usage and prohibit inline styles or `any` types. Proper hook design relies on standardized naming conventions and explicit prop typing to prevent improper `useEffect` usage and maintain scalable code.

Does this React development guide work with TypeScript for frontend applications?

Yes, this React development guide works seamlessly with TypeScript by enforcing explicit prop typing and prohibiting `any` types. It directs frontend development by applying strict typing rules to functional components, hooks, and event handlers to build robust applications.

What is the best way to name React components, hooks, and event handlers?

The best way to name React components, hooks, and event handlers is to follow standardized naming conventions enforced by functional component rules. Standardized naming for utilities and callbacks ensures consistency, clear callback identification, and maintainable frontend architecture across the codebase.

When should I not use inline styles or any types in React component design?

You should not use inline styles or `any` types in React component design when building scalable features. These are prohibited practices that bypass explicit prop typing and degrade maintainability, leading to unmanageable codebases and unpredictable frontend rendering behavior.