React Patterns workflow skill. Use this skill when the user needs Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
React Patterns workflow skill. Use this skill when the user needs Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-bundle-web-wizard/skills/react-patterns from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
React Patterns > Principles for building production-ready React applications. ---
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: 2. Hook Patterns, 3. State Management Selection, 4. React 19 Patterns, 5. Composition Patterns, 7. Error Handling, 8. TypeScript Patterns.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
This skill is applicable to execute the workflow or actions described in the overview.
Use when the request clearly matches the imported source intent: Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Use when copied upstream references, examples, or scripts materially improve the answer.
Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: 2. Hook Patterns
When to Extract Hooks
Pattern
Extract When
useLocalStorage
Same storage logic needed
useDebounce
Multiple debounced values
useFetch
Repeated fetch patterns
useForm
Complex form state
Hook Rules
Hooks at top level only
Same order every render
Custom hooks start with "use"
Clean up effects on unmount
Examples
Example 1: Ask for the upstream workflow directly
Use @react-patterns-v3 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @react-patterns-v3 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @react-patterns-v3 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @react-patterns-v3 using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Type - Use - State
Server - Data fetching, static - None
Client - Interactivity - useState, effects
Presentational - UI display - Props only
Container - Logic/state - Heavy state
One responsibility per component
Props down, events up
Imported Operating Notes
Imported: 1. Component Design Principles
Component Types
Type
Use
State
Server
Data fetching, static
None
Client
Interactivity
useState, effects
Presentational
UI display
Props only
Container
Logic/state
Heavy state
Design Rules
One responsibility per component
Props down, events up
Composition over inheritance
Prefer small, focused components
Imported: 6. Performance Principles
When to Optimize
Signal
Action
Slow renders
Profile first
Large lists
Virtualize
Expensive calc
useMemo
Stable callbacks
useCallback
Optimization Order
Check if actually slow
Profile with DevTools
Identify bottleneck
Apply targeted fix
Imported: 9. Testing Principles
Level
Focus
Unit
Pure functions, hooks
Integration
Component behavior
E2E
User flows
Test Priorities
User-visible behavior
Edge cases
Error states
Accessibility
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-bundle-web-wizard/skills/react-patterns, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@3d-web-experience-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@canvas-design-v4 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@form-cro-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@frontend-design-v5 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: 3. State Management Selection
Complexity
Solution
Simple
useState, useReducer
Shared local
Context
Server state
React Query, SWR
Complex global
Zustand, Redux Toolkit
State Placement
Scope
Where
Single component
useState
Parent-child
Lift state up
Subtree
Context
App-wide
Global store
Imported: 4. React 19 Patterns
New Hooks
Hook
Purpose
useActionState
Form submission state
useOptimistic
Optimistic UI updates
use
Read resources in render
Compiler Benefits
Automatic memoization
Less manual useMemo/useCallback
Focus on pure components
Imported: 5. Composition Patterns
Compound Components
Parent provides context
Children consume context
Flexible slot-based composition
Example: Tabs, Accordion, Dropdown
Render Props vs Hooks
Use Case
Prefer
Reusable logic
Custom hook
Render flexibility
Render props
Cross-cutting
Higher-order component
Imported: 7. Error Handling
Error Boundary Usage
Scope
Placement
App-wide
Root level
Feature
Route/feature level
Component
Around risky component
Error Recovery
Show fallback UI
Log error
Offer retry option
Preserve user data
Imported: 8. TypeScript Patterns
Props Typing
Pattern
Use
Interface
Component props
Type
Unions, complex
Generic
Reusable components
Common Types
Need
Type
Children
ReactNode
Event handler
MouseEventHandler
Ref
RefObject
Imported: 10. Anti-Patterns
❌ Don't
✅ Do
Prop drilling deep
Use context
Giant components
Split smaller
useEffect for everything
Server components
Premature optimization
Profile first
Index as key
Stable unique ID
Remember: React is about composition. Build small, combine thoughtfully.
Imported: Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
