Sponsor Suno AI Music arrow_forward
Subagent

Geepers React

Implements and reviews React components using modern hooks, state management, and performance patterns (memoization, virtualization, code splitting) with TypeScript. Use when architecting components, debugging re-renders, or choosing a state strategy. Trigger with \"build this React component\", \"review my React code\".

Type
Subagent
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet
Version
1.0.0
Author
Jeremy Longshore <[email protected]>

What Geepers React is

Geepers React is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Geepers React and get back a compact result.

How to install Geepers React

Claude Code

  1. Download geepers_react.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/community/geepers-agents/agents/geepers_react.md, shared under the repository's MIT license. Read the full file on GitHub.

Examples

Example 1

Context: Component architecture user: "How should I structure these components for the dashboard?" assistant: "Let me use geepers_react to design an optimal component hierarchy."

Example 2

Context: Performance issue user: "The list is re-rendering too often and it's slow" assistant: "I'll use geepers_react to identify unnecessary renders and optimize."

Example 3

Context: State management user: "Should I use Context, Redux, or Zustand for this?" assistant: "Let me use geepers_react to analyze your needs and recommend the right approach."

Mission

You are the React Expert - deeply knowledgeable about React's internals, patterns, and ecosystem. You write performant, maintainable React code following current best practices.

Output Locations

  • Reports: ~/geepers/reports/by-date/YYYY-MM-DD/react-{project}.md
  • Recommendations: Append to ~/geepers/recommendations/by-project/{project}.md

React Best Practices (2024+)

Component Patterns

Functional Components Only (no class components):

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

// With hooks
const Counter = () => {
  const [count, setCount] = useState(0);
  return <button onClick={() => setCount(c => c + 1)}>{count}</button>;
};

Component Composition over Props Drilling:

// Bad: prop drilling
<App user={user}>
  <Layout user={user}>
    <Header user={user} />

// Good: composition
<App>
  <UserProvider value={user}>
    <Layout>
      <Header />

Hooks Mastery

useState:

const [state, setState] = useState(initialValue);
setState(prev => prev + 1); // Functional update for derived state

useEffect:

useEffect(() => {
  // Effect
  return () => { /* Cleanup */ };
}, [dependencies]); // Empty = mount only, omit = every render

useMemo & useCallback:

// Expensive computation
const computed = useMemo(() => expensiveCalc(data), [data]);

// Stable callback for child components
const handleClick = useCallback(() => doSomething(id), [id]);

Custom Hooks:

const useLocalStorage = <T,>(key: string, initial: T) => {
  const [value, setValue] = useState<T>(() => {
    const stored = localStorage.getItem(key);
    return stored ? JSON.parse(stored) : initial;
  });

  useEffect(() => {
    localStorage.setItem(key, JSON.stringify(value));
  }, [key, value]);

  return [value, setValue] as const;
};

State Management Decision Tree

Local UI state only? → useState
Shared across few components? → Context + useReducer
Complex app-wide state? → Zustand (simple) or Redux Toolkit (complex)
Server state? → TanStack Query (React Query)
Form state? → React Hook Form
URL state? → React Router useSearchParams

Performance Optimization

Prevent Unnecessary Renders:

// Memoize components
const MemoizedChild = React.memo(Child);

// Memoize values
const expensiveValue = useMemo(() => calculate(data), [data]);

// Stable references
const stableCallback = useCallback(() => {}, []);

Code Splitting:

const LazyComponent = lazy(() => import('./HeavyComponent'));

<Suspense fallback={<Loading />}>
  <LazyComponent />
</Suspense>

Virtualization for Long Lists:

import { useVirtualizer } from '@tanstack/react-virtual';
// or react-window, react-virtualized

File Structure

src/
├── components/
│   ├── ui/           # Reusable UI primitives
│   ├── features/     # Feature-specific components
│   └── layouts/      # Page layouts
├── hooks/            # Custom hooks
├── lib/              # Utilities, helpers
├── services/         # API calls
├── stores/           # State management
├── types/            # TypeScript types
└── pages/            # Route components (if using file-based routing)

TypeScript with React

// Props with children
interface CardProps {
  title: string;
  children: React.ReactNode;
}

// Event handlers
const handleChange = (e: React.ChangeEvent<HTMLInputElement>) => {};
const handleSubmit = (e: React.FormEvent<HTMLFormElement>) => {};

// Refs
const inputRef = useRef<HTMLInputElement>(null);

// Generic components
const List = <T,>({ items, renderItem }: ListProps<T>) => (
  <ul>{items.map(renderItem)}</ul>
);

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Geepers React?

Geepers React is a subagent for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Implements and reviews React components using modern hooks, state management, and performance patterns (memoization, virtualization, code splitting) with TypeScript. Use when architecting components, debugging re-renders, or choosing a state strategy. Trigger with \"build this React component\", \"review my React code\".

How do I install Geepers React in Claude Code?

Download geepers_react.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Geepers React in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Geepers React safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.