refactor-component

A six-pass procedure for improving an existing React component, a reusable piece of a web interface, when triggered with `/refactor [ComponentName]`. It checks structure, types, styling tokens, and other code-quality rules in a fixed order.

In plain words
What is it for?
Use it to refactor a component under `src/components`, split overly large JSX sections, clean up props and types, replace hardcoded styling values, and verify dark-mode tokens.
Why use it?
It makes a large refactoring task repeatable and prevents important quality checks from being skipped. Separate commits make each pass easier to review.

Cursor rule

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 rules/alexgilev/agentic-ui/refactor-component
Clone the repo
git clone --depth 1 https://github.com/alexgilev/agentic-ui
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 841 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.00024 $0.00841
Opus 5 $0.00012 $0.00420
Sonnet 5 $0.00005 $0.00168
Haiku 4.5 $0.00002 $0.00084

Measured 2d ago against content hash 7f6635ae94c5, 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.

ai/cursor-rules/refactor-component.mdc · 92 lines

How it starts

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

/refactor [ComponentName]

When the user types /refactor [ComponentName], execute the full quality refactoring pipeline on that component.

Setup

  1. Locate the component at src/components/[ComponentName]/
  2. Read .ai/refactoring.md for the 6-pass checklist
  3. Read .ai/code-quality-rules.md for anti-pattern detection and architecture rules

Execution

Run all 6 passes in order. One commit per pass. Never combine passes. Never skip a pass.

Pass 1 — Structural Integrity

  • Extract sub-components if any JSX block exceeds 50 lines
  • Single responsibility per component
  • Props hygiene: remove unused, no drilling past 2 levels, max 7-8 props
  • Flatten nested ternaries into named variables
  • No any, no unjustified as Type
  • Types in .types.ts, constants at top or in .constants.ts

Commit: refactor([ComponentName]): structural cleanup

Pass 2 — Token Fidelity Audit

  • Grep all .css and .tsx for hardcoded colors (#, rgb, rgba, hsl) → replace with var(--)
  • Grep for raw px values not in var() → replace with token
  • Verify 3-tier aliasing: primitive → semantic → component (no skipped tier)
  • Verify dark mode token resolution under [data-theme="dark"]
  • Generate token coverage report

Commit: refactor([ComponentName]): token compliance

Pass 3 — Performance & Memoization

  • React.memo() only on components receiving non-primitive props from parents
  • useMemo() / useCallback() only where justified — no over-memoization
  • Remove duplicate CSS declarations and unused classes
  • Single-class specificity only, zero !important
  • Verify named exports for tree-shaking

Commit: refactor([ComponentName]): performance

Pass 4 — Accessibility Hardening

  • Semantic HTML (<button> not <div onClick>)
  • Keyboard: Tab order, Enter/Space, Escape, arrow keys for composites
  • aria-label on icon-only controls, aria-live for dynamic content
  • Contrast ≥ 4.5:1 normal text, focus ring visible in all themes
  • Run jest-axe on all stories → zero violations

Read the full file on GitHub · 92 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 · 92 lines · 24 tokens per session scan A 7f6635ae94c5

Subscribe to this mod's changes

refactor-component is a cursor rule published in the GitHub repository alexgilev/agentic-ui (23 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 841 once invoked, about $0.0001 per session on Opus 5. 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-30.