new-component

A set of instructions for creating new React user-interface components. It covers planning the component, checking existing patterns, and organizing its files.

In plain words
What is it for?
Use it when building pages, forms, dialogs, data containers, display components, or error boundaries in a React application.
Why use it?
It helps keep new components consistent with the project's structure, reusable code, and interface conventions.

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/kubev2v/forklift-console-plugin/new-component
Clone the repo
git clone --depth 1 https://github.com/kubev2v/forklift-console-plugin

Made for: Cursor.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,036 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.00006 $0.01036
Opus 5 $0.00003 $0.00518
Sonnet 5 $0.00001 $0.00207
Haiku 4.5 $0.00001 $0.00104

Measured 2d ago against content hash e6aae8754ca9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

new-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 2d 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/workflows/new-component.mdc · 153 lines

How it starts

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

Creating a New Component

Invoke with: "create a component", "new component", "build a component for"

Follow this comprehensive workflow when creating new components. For coding conventions, see AGENTS.md.


1. Planning Phase

Understand Requirements

  • What is the component's purpose?
  • What data does it need?
  • What actions can users perform?
  • What states does it have (loading, error, empty)?
  • How does it fit into the existing UI?

Identify Component Type

  • Page Component: Top-level route component
  • Container Component: Fetches data, manages state
  • Presentational Component: Pure UI, receives props
  • Modal Component: Overlay dialog
  • Form Component: User input handling (react-hook-form)
  • Error Boundary: Class component with componentDidCatch

Check Existing Patterns

  • Look for similar components in codebase
  • Identify reusable hooks from @utils/ or feature-specific hooks
  • Find existing utility functions
  • Check PatternFly for appropriate components
  • Use custom Select from @components/common/Select (not PatternFly Select directly)

2. Folder Structure

src/{feature}/components/{component-name}/
  ComponentName.tsx       # Main component
  component-name.scss     # Styles
  components/             # Sub-components
    SubComponent.tsx
  hooks/                  # Component-specific hooks
    useComponentLogic.ts
  utils/                  # Component-specific utilities
    helpers.ts
    constants.ts

Naming Conventions

  • Folder: lowercase kebab-case (provider-details-page)
  • Component file: PascalCase (ProviderDetailsPage.tsx)
  • SCSS file: lowercase kebab-case (provider-details-page.scss)
  • Hook files: camelCase with use prefix (useProviderDetails.ts)
  • No barrel files -- import directly from the source file

3. Component Implementation

Component Structure Order

  1. Imports (external, then internal, then styles)
  2. Type definitions (using type, not interface)
  3. Constants (if small, otherwise separate file)
  4. Component function (using FC type)
  5. Default export

Read the full file on GitHub · 153 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. 2d ago First seen · 153 lines · 6 tokens per session scan A e6aae8754ca9

Subscribe to this mod's changes

new-component is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 6 tokens to every session and 1,036 once invoked, about $0.0000 per session on Opus 5. 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.