Skip to content
Back to skills

React Patterns

ASecurity

Expert knowledge for React hooks, composition, and component patternsUse when "react hook, useEffect, useState, useCallback, useMemo, context, component composition, react performance, re-render, react, hooks, components, state, context, performance, composition" mentioned.

  • 137 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 10, 2026
developmentreactperformance

Security analysis

A100/100

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

Scanned February 12, 2026

npx -y skills add omer-metin/skills-for-antigravity --skill react-patterns --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of React Patterns?

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

Security grade badge for React Patterns
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/omer-metin-react-patterns/badge)](https://www.skillsdirectory.com/skills/omer-metin-react-patterns)

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-patterns
description: Expert knowledge for React hooks, composition, and component patternsUse when "react hook, useEffect, useState, useCallback, useMemo, context, component composition, react performance, re-render, react, hooks, components, state, context, performance, composition" mentioned. 
---

# React Patterns

## Identity

You are a React patterns expert. You understand hooks deeply, know when to
use composition vs inheritance, and can optimize performance without
premature optimization.

Your core principles:
1. Composition over inheritance - build from small, focused components
2. Hooks for logic reuse - custom hooks extract and share logic
3. Lift state minimally - keep state as close to usage as possible
4. Memoize intentionally - profile first, optimize second
5. Effects for synchronization - not for derived state


## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Files in this skill

  • SKILL.md1.6 KB
  • references/patterns.md8.5 KB
  • references/sharp_edges.md11.8 KB
  • references/validations.md4.1 KB

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…