create-component

A command for creating typed React components with Tailwind CSS and accessibility attributes. Components are reusable pieces of a user interface, such as buttons, inputs, cards, or page layouts.

In plain words
What is it for?
Creating UI, feature, and layout components, defining their properties, adding visual styles and ARIA attributes, supporting needed states or variants, and exporting them consistently.
Why use it?
It gives new components a consistent structure and reminds the developer to account for typing, accessibility, and common loading, error, and empty states.

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

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 334 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.00334
Opus 5 $0.00000 $0.00167
Sonnet 5 $0.00000 $0.00067
Haiku 4.5 $0.00000 $0.00033

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

Security

Grade A, and why

create-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 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/commands/create-component.md · 53 lines

What it actually says

Create Component

Overview

Create a new React component following project standards with TypeScript, Tailwind CSS, and proper accessibility.

Steps

  1. Determine component type

    • UI component (buttons, inputs, cards)
    • Feature component (user profiles, product cards)
    • Layout component (headers, sidebars)
  2. Generate component structure

    • Create TypeScript interface for props
    • Use functional component with proper typing
    • Add Tailwind CSS classes
    • Include accessibility attributes (ARIA labels, roles)
  3. Add component features

    • Loading state (if async)
    • Error state (if can fail)
    • Empty state (if displays data)
    • Variants (if multiple styles needed)
  4. Export properly

    • Use named export
    • Place in appropriate directory (components/ui or components/features)

Template

interface [ComponentName]Props {
  // Define props based on requirements
  className?: string;
  children?: React.ReactNode;
}

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

Checklist

  • TypeScript interface defined
  • Proper naming (PascalCase)
  • Tailwind CSS styling
  • Accessibility attributes added
  • Loading/error states (if needed)
  • Named export used
  • File placed in correct directory
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 · 53 lines · 0 tokens per session scan A 8305e2009d92

Subscribe to this mod's changes

create-component is a command 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 334 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.