component-patterns

component-patterns is a cursor rule for Cursor from girijashankarj/cursor-handbook. It costs 0 tokens per session (895 once invoked), scanned A, original, MIT.

A set of patterns for building React user-interface components. It covers how to organize components, define their inputs, and implement them with functions and hooks.

In plain words
What is it for?
It helps create buttons, forms, layouts, feature components, and shared interface elements in React.
Why use it?
It gives a project a consistent structure for reusable interface pieces. This makes components easier to find, reuse, and maintain.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It helps create buttons, forms, layouts, feature components, and shared interface elements in React.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/girijashankarj/cursor-handbook/component-patterns
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/girijashankarj/cursor-handbook

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 component-patterns

README.md
[![agentmods](https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/component-patterns/github.svg)](https://agentmods.dev/rules/girijashankarj/cursor-handbook/component-patterns)
Your own site
<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/component-patterns"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/component-patterns/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 component-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/component-patterns"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/component-patterns.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 895 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.00895
Opus 5.5 $0.00000 $0.00358
Sonnet 5.5 $0.00000 $0.00179
Haiku 4.5 $0.00000 $0.00089

Measured 1mo ago against content hash 5bddcbfb37ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

component-patterns 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 1mo 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/rules/frontend/component-patterns.mdc · 131 lines

How it starts

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

Frontend Component Patterns

Component Structure

src/components/
├── ui/                    # Atomic/base components
│   ├── Button/
│   │   ├── Button.tsx
│   │   ├── Button.test.tsx
│   │   ├── Button.stories.tsx
│   │   └── index.ts
│   ├── Input/
│   └── Modal/
├── features/              # Feature-specific components
│   ├── Auth/
│   ├── Dashboard/
│   └── Settings/
├── layout/                # Layout components
│   ├── Header/
│   ├── Sidebar/
│   └── Footer/
└── shared/                # Shared/utility components
    ├── ErrorBoundary/
    ├── LoadingSpinner/
    └── ProtectedRoute/

Component Guidelines

Functional Components Only

  • Use functional components with hooks — no class components
  • Use React.FC or explicit return types
  • Destructure props at the function signature level

Props

  • Define props interface above the component
  • Use descriptive prop names
  • Provide default values where appropriate
  • Document complex props with JSDoc comments
interface ButtonProps {
  /** Button label text */
  label: string;
  /** Visual style variant */
  variant?: 'primary' | 'secondary' | 'danger';
  /** Disabled state */
  disabled?: boolean;
  /** Click handler */
  onClick: () => void;
}

export const Button: React.FC<ButtonProps> = ({
  label,
  variant = 'primary',
  disabled = false,
  onClick,
}) => {
  return (
    <button
      className={`btn btn-${variant}`}
      disabled={disabled}
      onClick={onClick}
    >
      {label}
    </button>
  );
};

State Management

  • Local state: useState for component-scoped state
  • Shared state: Context API or state library (Zustand, Redux Toolkit)
  • Server state: React Query / TanStack Query
  • Form state: React Hook Form or Formik
  • NEVER prop-drill more than 2 levels — use context or state management

Performance

  • Memoize expensive computations with useMemo
  • Memoize callbacks with useCallback when passing to child components
  • Use React.memo for pure presentational components
  • Lazy load routes and heavy components with React.lazy
  • Virtualize long lists (react-window or react-virtuoso)

Read the full file on GitHub · 131 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. 1mo ago First seen · 131 lines · 0 tokens per session scan A 5bddcbfb37ba

Subscribe to this mod's changes

component-patterns is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (33 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 895 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.