component-patterns

A collection of reusable templates for building React components, which are the reusable pieces that make up a web interface.

In plain words
What is it for?
Use it when creating basic React components or components with variants such as primary, secondary, small, medium, and large styles.
Why use it?
It reduces repeated setup work and helps components follow the project's existing conventions for properties, styling, sizes, and visual variations.

Cursor rule 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 rules/farzannajipour/cursor-react-rules/component-patterns
Clone the repo
git clone --depth 1 https://github.com/Farzannajipour/cursor-react-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,161 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.01161
Opus 5 $0.00000 $0.00580
Sonnet 5 $0.00000 $0.00232
Haiku 4.5 $0.00000 $0.00116

Measured yesterday against content hash 4577a881f356, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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/component-patterns.mdc · 199 lines

How it starts

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

Component Creation Patterns

Reusable templates for generating React components following project standards.

Pattern: Basic Component

interface [ComponentName]Props {
  children?: React.ReactNode;
  className?: string;
}

export function [ComponentName]({ children, className }: [ComponentName]Props) {
  return (
    <div className={cn('[base-classes]', className)}>
      {children}
    </div>
  );
}

Pattern: Component with Variants (CVA)

import { cva, type VariantProps } from 'class-variance-authority';
import { cn } from '@/lib/utils';

const [componentName]Variants = cva(
  '[base-classes]',
  {
    variants: {
      variant: {
        primary: '[primary-classes]',
        secondary: '[secondary-classes]',
      },
      size: {
        sm: '[sm-classes]',
        md: '[md-classes]',
        lg: '[lg-classes]',
      },
    },
    defaultVariants: {
      variant: 'primary',
      size: 'md',
    },
  }
);

interface [ComponentName]Props 
  extends React.HTMLAttributes<HTMLDivElement>,
    VariantProps<typeof [componentName]Variants> {}

export function [ComponentName]({ 
  className, 
  variant, 
  size,
  ...props 
}: [ComponentName]Props) {
  return (
    <div
      className={cn([componentName]Variants({ variant, size }), className)}
      {...props}
    />
  );
}

Pattern: Form Component with React Hook Form + Zod

import { useForm } from 'react-hook-form';
import { zodResolver } from '@hookform/resolvers/zod';
import { z } from 'zod';

const schema = z.object({
  email: z.string().email('Invalid email'),
  password: z.string().min(8, 'Min 8 characters'),
});

type FormData = z.infer<typeof schema>;

export function [FormName]({ onSubmit }: { onSubmit: (data: FormData) => Promise<void> }) {
  const { register, handleSubmit, formState: { errors, isSubmitting } } = useForm<FormData>({
    resolver: zodResolver(schema),
  });

  return (
    <form onSubmit={handleSubmit(onSubmit)} className="space-y-4">
      <div>
        <label htmlFor="email">Email</label>
        <input {...register('email')} id="email" type="email" />
        {errors.email && <p className="text-red-600">{errors.email.message}</p>}
      </div>
      
      <button type="submit" disabled={isSubmitting}>
        {isSubmitting ? 'Submitting...' : 'Submit'}
      </button>
    </form>
  );
}

Read the full file on GitHub · 199 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. yesterday First seen · 199 lines · 0 tokens per session scan A 4577a881f356

Subscribe to this mod's changes

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