modus-react-best-practices

modus-react-best-practices is a cursor rule for Cursor from julianoczkowski/create-trimble-app. It costs 0 tokens per session (3,088 once invoked), scanned A, original, MIT.

Detailed React best practices for creating reusable, configurable components with the Modus Design System. It also covers semantic colors, web-component events, themes, and Vite with SWC, a fast code compiler.

In plain words
What is it for?
Use it when designing component APIs or reviewing React UI code built with Modus.
Why use it?
It helps prevent repeated component code and inconsistent styling while keeping interactions and themes predictable.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when designing component APIs or reviewing React UI code built with Modus.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/julianoczkowski/create-trimble-app/modus-react-best-practices
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.

Clone the repo
git clone --depth 1 https://github.com/julianoczkowski/create-trimble-app

Made for: Cursor.

Wrote 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.

agentmods badge for modus-react-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-react-best-practices.svg)](https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-react-best-practices)
Your own site
<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-react-best-practices"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-react-best-practices.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,088 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.03088
Opus 5 $0.00000 $0.01544
Sonnet 5 $0.00000 $0.00618
Haiku 4.5 $0.00000 $0.00309

Measured 4d ago against content hash c8b911cd0dc9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

modus-react-best-practices 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

templates/react/.cursor/rules/modus-react-best-practices.mdc · 509 lines

How it starts

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

Modus React Best Practices for Vite + SWC

🏗️ Component Architecture

Single Configurable Component Pattern

CRITICAL: Create one configurable component instead of multiple specific components.

// ✅ CORRECT: Single configurable component
function ModusButton({
  variant = "primary",
  size = "md",
  disabled = false,
  children,
  ...props
}: ModusButtonProps) {
  const baseClasses =
    "inline-flex items-center justify-center font-medium transition-colors focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring disabled:pointer-events-none disabled:opacity-50";

  const variantClasses = {
    primary: "bg-primary text-primary-foreground hover:bg-primary/90",
    secondary: "bg-secondary text-secondary-foreground hover:bg-secondary/90",
    destructive:
      "bg-destructive text-destructive-foreground hover:bg-destructive/90",
    outline:
      "border border-border bg-background hover:bg-muted hover:text-muted-foreground",
    ghost: "hover:bg-muted hover:text-muted-foreground",
    link: "text-primary underline-offset-4 hover:underline",
  };

  const sizeClasses = {
    sm: "h-9 px-3 text-sm",
    md: "h-10 px-4 py-2",
    lg: "h-11 px-8",
    icon: "h-10 w-10",
  };

  return (
    <ModusWcButton
      className={`${baseClasses} ${variantClasses[variant]} ${sizeClasses[size]}`}
      disabled={disabled}
      {...props}
    >
      {children}
    </ModusWcButton>
  );
}

// ❌ WRONG: Multiple specific components
function PrimaryButton({ children, ...props }) {
  /* ... */
}
function SecondaryButton({ children, ...props }) {
  /* ... */
}
function DestructiveButton({ children, ...props }) {
  /* ... */
}

Component Composition Pattern

// ✅ CORRECT: Component composition
function Card({ children, className, ...props }: CardProps) {
  return (
    <div
      className={`bg-card text-card-foreground border border-border rounded-lg ${className}`}
      {...props}
    >
      {children}
    </div>
  );
}

function CardHeader({ children, className, ...props }: CardHeaderProps) {
  return (
    <div className={`flex flex-col space-y-1.5 p-6 ${className}`} {...props}>
      {children}
    </div>
  );
}

function CardTitle({ children, className, ...props }: CardTitleProps) {
  return (
    <div
      className={`text-2xl font-semibold leading-none tracking-tight ${className}`}
      {...props}
    >
      {children}
    </div>
  );
}

function CardContent({ children, className, ...props }: CardContentProps) {
  return (
    <div className={`p-6 pt-0 ${className}`} {...props}>
      {children}
    </div>
  );
}

// Usage
<Card>
  <CardHeader>
    <CardTitle>Card Title</CardTitle>
  </CardHeader>
  <CardContent>
    <div>Card content</div>
  </CardContent>
</Card>;

Read the full file on GitHub · 509 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. 4d ago First seen · 509 lines · 0 tokens per session scan A c8b911cd0dc9

Subscribe to this mod's changes

modus-react-best-practices is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,088 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-09-03.