react-components

A set of rules for writing React components, which are reusable parts of a web interface. It describes patterns for TypeScript, Tailwind CSS, component properties, and loading or error states.

In plain words
What is it for?
It helps create small React components with typed properties, reusable styling, sensible defaults, and clear loading and error handling.
Why use it?
It gives coding sessions consistent expectations for component structure and styling. This reduces guesswork when adding or changing interface code.

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/technickai/ai-coding-config/react-components
Clone the repo
git clone --depth 1 https://github.com/TechNickAI/ai-coding-config

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 521 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.00521
Opus 5 $0.00000 $0.00260
Sonnet 5 $0.00000 $0.00104
Haiku 4.5 $0.00000 $0.00052

Measured yesterday against content hash 982be497a5ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

react-components 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/frontend/react-components.mdc · 108 lines

How it starts

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

React Components

Component Structure

import { cn } from "@/lib/utils";

interface ComponentProps {
  className?: string;
  children: React.ReactNode;
  variant?: "default" | "primary" | "secondary";
}

export function Component({
  className,
  children,
  variant = "default",
}: ComponentProps) {
  return (
    <div
      className={cn(
        "rounded-lg bg-background p-4",
        "hover:bg-muted/50 transition-colors",
        {
          "border-blue-500": variant === "primary",
          "border-gray-300": variant === "default",
        },
        className
      )}
    >
      {children}
    </div>
  );
}

Best Practices

We use TypeScript and Tailwind CSS. We use cn() for conditional classes, define clear prop interfaces with sensible defaults, keep components focused and small, use composition over inheritance, and implement proper loading and error states.

Props Pattern

interface Props {
  // Required props first
  id: string;
  title: string;

  // Optional props with defaults
  className?: string;
  variant?: "default" | "primary";
  disabled?: boolean;

  // Functions and callbacks
  onClick?: () => void;
  onSubmit?: (data: FormData) => Promise<void>;

  // Children and render props
  children?: React.ReactNode;
  renderHeader?: () => React.ReactNode;
}

State Management

// Use hooks for state
const [isOpen, setIsOpen] = useState(false);
const [data, setData] = useState<Data | null>(null);

// Use useEffect for side effects
useEffect(() => {
  fetchData().then(setData);
}, [dependency]);

// Custom hooks for reusable logic
const { user, loading, error } = useAuth();

Conditional Rendering

// Loading state
if (loading) return <Spinner />;

// Error state
if (error) return <ErrorMessage error={error} />;

// Empty state
if (!data.length) return <EmptyState />;

// Success state
return <DataDisplay data={data} />;

Testing

We test component rendering, user interactions, different states (loading, error, empty, success), and accessibility.

Read the full file on GitHub · 108 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 · 108 lines · 0 tokens per session scan A 982be497a5ee

Subscribe to this mod's changes

react-components is a cursor rule published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 521 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-30.