react-functional-components-preference

react-functional-components-preference is a cursor rule for Cursor from holtwood/awesome-cursorrules-zh. It costs 0 tokens per session (431 once invoked), scanned A, original, MIT.

A React style rule that prefers function components with Hooks such as useState and useEffect over class components. Hooks are React functions for managing state and other component behavior.

In plain words
What is it for?
Use it when creating React components, extracting shared behavior into custom Hooks, and replacing class-based state or lifecycle code.
Why use it?
It keeps most components shorter and makes shared logic easier to reuse and test.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when creating React components, extracting shared behavior into custom Hooks, and replacing class-based state or lifecycle code.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/holtwood/awesome-cursorrules-zh/react-functional-components-preference
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.

Clone the repo
git clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zh

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for react-functional-components-preference

README.md
[![agentmods](https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/react-functional-components-preference/github.svg)](https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/react-functional-components-preference)
Your own site
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/react-functional-components-preference"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/react-functional-components-preference/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for react-functional-components-preference

Your own site · 80×15
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/react-functional-components-preference"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/react-functional-components-preference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 431 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00431
Opus 5 $0.00000 $0.00216
Sonnet 5 $0.00000 $0.00086
Haiku 4.5 $0.00000 $0.00043

Measured 6d ago against content hash c932641248c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

react-functional-components-preference 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 6d 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.

docs/rules/frontend/react/apollo-graphql/react-functional-components-preference.mdc · 34 lines

What it actually says

  • 始终使用带有 hooks 的函数式组件而不是类组件
    • 现代化开发:优先使用 React Hooks(如 useState, useEffect, useContext, useReducer, useCallback, useMemo 等)进行状态管理和副作用处理,以符合 React 官方推荐的现代化开发范式。
    • 代码简洁性:函数式组件通常比类组件更简洁,更易于阅读和理解,尤其是在处理逻辑复用时。
    • 逻辑复用:通过自定义 Hooks,可以方便地在不同组件之间共享状态逻辑,避免了高阶组件(HOCs)和渲染属性(Render Props)带来的嵌套问题。
    • 性能优化:结合 useCallbackuseMemo 等 Hooks,可以有效地进行性能优化,避免不必要的渲染。
    • 可测试性:函数式组件和 Hooks 更容易进行单元测试。
    • 示例
      // 函数式组件示例
      import React, { useState, useEffect } from 'react';
      
      function Counter() {
        const [count, setCount] = useState(0);
      
        useEffect(() => {
          document.title = `You clicked ${count} times`;
        }, [count]);
      
        return (
          <div>
            <p>You clicked {count} times</p>
            <button onClick={() => setCount(count + 1)}>
              Click me
            </button>
          </div>
        );
      }
      
    • 特殊情况:仅在极少数需要使用 getSnapshotBeforeUpdatecomponentDidCatch 等生命周期方法时,才考虑使用类组件,但大多数场景下 Hooks 都能提供替代方案(如错误边界)。
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. 6d ago First seen · 34 lines · 0 tokens per session scan A c932641248c4

Subscribe to this mod's changes

react-functional-components-preference is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (233 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 431 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-09-03.