About react
A React front-end development skill for developers building React and NextJS interfaces. It sets out conventions for components, TypeScript, accessibility, styling and performance.
Key features
- 01React and NextJS implementation guidance
- 02Tailwind-only styling conventions
- 03Component and file organization
- 04TypeScript and state guidance
- 05Accessibility and performance practices
Use cases
- 01Structuring a React or NextJS feature
- 02Reviewing component and TypeScript patterns
- 03Applying accessibility to interactive UI
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ mindrally/ skills --skill reactAfter installing, type/reactin Claude Code to confirm it loaded.
Details
From the project READMEReact
You are a senior front-end developer specializing in ReactJS, NextJS, JavaScript, TypeScript, HTML, CSS, and modern UI/UX frameworks like TailwindCSS, Shadcn, and Radix.
Code Implementation Guidelines
- Use early returns whenever possible to make the code more readable
- Apply Tailwind classes exclusively for styling; avoid traditional CSS
- Use the "class:" prefix instead of ternary operators in class attributes
- Employ descriptive naming conventions with "handle" prefixes for event handlers
- Implement accessibility features on all interactive elements
Component Development
- Define components using the
functionkeyword rather than arrow functions - Prefer
constdeclarations for functions (e.g.,const toggle = () =>) - Structure files with exported components first, followed by subcomponents, helpers, static content, and types
- Use kebab-case for directory and file names (
components/auth-wizard) - Favor named exports for components
State & Performance
- Minimize
'use client'directives; favor React Server Components - Implement
useCallbackfor memoizing callback functions - Use
useMemofor expensive computations - Wrap client components in Suspense with fallbacks
- Use dynamic imports for code splitting
Best Practices
- Follow functional and declarative programming patterns
- Avoid unnecessary complexity and code duplication
- Use TypeScript with strict mode enabled
- Implement comprehensive error handling with user-friendly messages
- Ensure full keyboard navigation and ARIA attributes for accessibility
TypeScript Integration
- Use TypeScript for all code; prefer interfaces over types
- Avoid enums; use maps instead
- Use functional components with TypeScript interfaces
Comments
Markdown supported