refactor-component

A procedure for improving an existing React component without changing what it does. It covers structure, duplicated code, TypeScript types, speed, accessibility, and tests.

In plain words
What is it for?
Use it to inspect a component, move logic into custom hooks, extract smaller components or utilities, remove any types, improve performance and accessibility, and update tests.
Why use it?
It helps make large or difficult components easier to understand and maintain while preserving their current behavior. It also identifies issues such as repeated logic, missing types, and keyboard-access problems.

Command for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/farzannajipour/cursor-react-rules/refactor-component
Clone the repo
git clone --depth 1 https://github.com/Farzannajipour/cursor-react-rules

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 541 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00541
Opus 5 $0.00000 $0.00270
Sonnet 5 $0.00000 $0.00108
Haiku 4.5 $0.00000 $0.00054

Measured 2d ago against content hash fbf99256ceb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

refactor-component scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/commands/refactor-component.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Refactor Component

Overview

Refactor an existing component to improve code quality, performance, and maintainability.

Steps

  1. Analyze current component

    • Identify code smells
    • Check component size (>200 lines?)
    • Look for duplicated logic
    • Review performance
  2. Extract logic

    • Move business logic to custom hooks
    • Extract sub-components
    • Create utility functions
  3. Improve types

    • Add missing TypeScript types
    • Remove 'any' types
    • Add JSDoc comments
  4. Optimize performance

    • Add React.memo if needed
    • Use useMemo for expensive calculations
    • Use useCallback for function props
  5. Improve accessibility

    • Add ARIA labels
    • Ensure keyboard navigation
    • Add semantic HTML

Refactoring Checklist

  • Component under 200 lines
  • No code duplication
  • Business logic in custom hooks
  • All TypeScript types defined
  • No 'any' types
  • Performance optimized
  • Accessibility improved
  • Tests updated
  • Functionality unchanged

Common Refactoring Patterns

Extract Custom Hook

// Before
function Component() {
  const [data, setData] = useState([]);
  const [loading, setLoading] = useState(false);
  
  useEffect(() => {
    // fetch logic
  }, []);
  
  return <div>{/* JSX */}</div>;
}

// After
function useData() {
  const [data, setData] = useState([]);
  const [loading, setLoading] = useState(false);
  
  useEffect(() => {
    // fetch logic
  }, []);
  
  return { data, loading };
}

function Component() {
  const { data, loading } = useData();
  return <div>{/* JSX */}</div>;
}

Extract Sub-component

// Before
function LargeComponent() {
  return (
    <div>
      <div className="header">{/* header JSX */}</div>
      <div className="content">{/* content JSX */}</div>
      <div className="footer">{/* footer JSX */}</div>
    </div>
  );
}

// After
function Header() { /* ... */ }
function Content() { /* ... */ }
function Footer() { /* ... */ }

function LargeComponent() {
  return (
    <div>
      <Header />
      <Content />
      <Footer />
    </div>
  );
}

Read the full file on GitHub · 106 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 106 lines · 0 tokens per session scan A fbf99256ceb8

Subscribe to this mod's changes

refactor-component is a command published in the GitHub repository Farzannajipour/cursor-react-rules (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 541 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.