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.
npx agentmods add rules/goranerhartic/cursor-development-rules/componentsgit clone --depth 1 https://github.com/GoranErhartic/cursor-development-rulesWrote 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.
[](https://agentmods.dev/rules/goranerhartic/cursor-development-rules/components)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/components"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/components.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00014 | $0.00433 |
| Opus 5 | $0.00007 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
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.
What it actually says
Component Design Patterns
Structure
- Functional components; extend native props where appropriate (
React.ButtonHTMLAttributes<HTMLButtonElement>); spread...propsonto DOM element; usecn()or similar for class merging - Variants: use discriminated props (e.g.
variant: 'primary' | 'secondary') and map to styles; avoid boolean prop proliferation
Composition Over Configuration
- Prefer composition:
<Card><CardHeader>...</CardHeader><CardContent>...</CardContent></Card>over<Card title="..." content="..." /> - Small, focused subcomponents (CardHeader, CardContent, CardFooter) give flexibility and clarity
Compound Components
- Parent holds state (e.g. active tab); provide via Context; child components consume with
useContextor custom hook; throw if used outside provider - Example:
Tabs(state) +TabsList+Tab+TabPanel; shareactiveTab/setActiveTabvia context
Render Props / Slots
- When composition needs access to internal state:
children(value)orrender(value); or use slot props:header,footeras render functions
Props Conventions
- Children:
React.ReactNodefor flexible content - Optional with defaults:
variant = 'primary' - Forwarding refs:
forwardRefwhen wrapping native elements (input, button) for focus or form libraries - Avoid: Boolean props that could be variants (e.g.
isPrimary→variant="primary")
Best Practices
- Single responsibility; composition; consistent prop naming; accessibility (see
accessibility.mdc)
Anti-Patterns
- Monolithic components with many optional props; prop drilling (use context or composition); missing ref forwarding for form/accessibility
See also: forms.mdc, accessibility.mdc, styling.mdc
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.
- yesterday First seen · 42 lines · 14 tokens per session scan A 1762638d8c28
components is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 433 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
general
Wonder Blocks design system conventions, component patterns, and coding standards.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
new-component
Workflow for creating new React components.
solana-transaction-safety
Safe Solana transaction submission patterns using Helius Sender.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.