rules--js-batch-dom-css

rules--js-batch-dom-css is a cursor rule for Cursor from ratnesh-maurya/cursor-claude-personas. It costs 0 tokens per session (465 once invoked), scanned A, original, MIT.

A browser performance rule for applying several CSS changes together instead of changing each style property separately. CSS controls the appearance and layout of web pages.

In plain words
What is it for?
Use it when updating several styles on an element, by applying a class or assigning the styles as one group.
Why use it?
It reduces the browser layout recalculations, called reflows, that can happen after individual style changes.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when updating several styles on an element, by applying a class or assigning the styles as one group.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ratnesh-maurya/cursor-claude-personas/rules-js-batch-dom-css
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/ratnesh-maurya/cursor-claude-personas

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 rules--js-batch-dom-css

README.md
[![agentmods](https://agentmods.dev/badge/rules/ratnesh-maurya/cursor-claude-personas/rules-js-batch-dom-css/github.svg)](https://agentmods.dev/rules/ratnesh-maurya/cursor-claude-personas/rules-js-batch-dom-css)
Your own site
<a href="https://agentmods.dev/rules/ratnesh-maurya/cursor-claude-personas/rules-js-batch-dom-css"><img src="https://agentmods.dev/badge/rules/ratnesh-maurya/cursor-claude-personas/rules-js-batch-dom-css/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for rules--js-batch-dom-css

Your own site · 80×15
<a href="https://agentmods.dev/rules/ratnesh-maurya/cursor-claude-personas/rules-js-batch-dom-css"><img src="https://agentmods.dev/badge/rules/ratnesh-maurya/cursor-claude-personas/rules-js-batch-dom-css.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 465 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.00465
Opus 5 $0.00000 $0.00233
Sonnet 5 $0.00000 $0.00093
Haiku 4.5 $0.00000 $0.00047

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

Security

Grade A, and why

rules--js-batch-dom-css 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 7d 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.

3d-frontend-developer/.cursor/rules/rules--js-batch-dom-css.mdc · 83 lines

What it actually says

Batch DOM CSS Changes

Avoid changing styles one property at a time. Group multiple CSS changes together via classes or cssText to minimize browser reflows.

Incorrect (multiple reflows):

function updateElementStyles(element: HTMLElement) {
  // Each line triggers a reflow
  element.style.width = '100px'
  element.style.height = '200px'
  element.style.backgroundColor = 'blue'
  element.style.border = '1px solid black'
}

Correct (add class - single reflow):

// CSS file
.highlighted-box {
  width: 100px;
  height: 200px;
  background-color: blue;
  border: 1px solid black;
}

// JavaScript
function updateElementStyles(element: HTMLElement) {
  element.classList.add('highlighted-box')
}

Correct (change cssText - single reflow):

function updateElementStyles(element: HTMLElement) {
  element.style.cssText = `
    width: 100px;
    height: 200px;
    background-color: blue;
    border: 1px solid black;
  `
}

React example:

// Incorrect: changing styles one by one
function Box({ isHighlighted }: { isHighlighted: boolean }) {
  const ref = useRef<HTMLDivElement>(null)
  
  useEffect(() => {
    if (ref.current && isHighlighted) {
      ref.current.style.width = '100px'
      ref.current.style.height = '200px'
      ref.current.style.backgroundColor = 'blue'
    }
  }, [isHighlighted])
  
  return <div ref={ref}>Content</div>
}

// Correct: toggle class
function Box({ isHighlighted }: { isHighlighted: boolean }) {
  return (
    <div className={isHighlighted ? 'highlighted-box' : ''}>
      Content
    </div>
  )
}

Prefer CSS classes over inline styles when possible. Classes are cached by the browser and provide better separation of concerns.

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. 7d ago First seen · 83 lines · 0 tokens per session scan A b2dc21bef3b5

Subscribe to this mod's changes

rules--js-batch-dom-css is a cursor rule published in the GitHub repository ratnesh-maurya/cursor-claude-personas (8 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 465 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.

Related

Other cursor rules, from other repositories

chakra-ui---theme-directory-rules

Rules for organizing a Chakra UI theme into an entry file, foundational settings, and component-specific styles. The theme controls shared colors, fonts, spacing, breakpoints, and component variants.

holtwood/awesome-cursorrules-zh · 0 tokens

chakra-ui-best-practices

A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.

holtwood/awesome-cursorrules-zh · 0 tokens

chakra-ui---accessibility-features

An accessibility rule for React interfaces built with Chakra UI, a component library. It covers semantic HTML, screen-reader labels, keyboard navigation, focus handling, and color contrast.

holtwood/awesome-cursorrules-zh · 0 tokens

chakra-ui---dark-mode-implementation

A Chakra UI rule for adding a light and dark color mode to React components. It covers switching modes, following the system preference, storing the choice, and preventing a flash of the wrong theme during loading.

holtwood/awesome-cursorrules-zh · 0 tokens

chakra-ui---responsive-design

Guidance for making Chakra UI layouts adapt to different screen sizes. It uses responsive style values, breakpoints, layout components, and conditional display rules for phones, tablets, and desktops.

holtwood/awesome-cursorrules-zh · 0 tokens

react-chakra-ui---folder-structure

A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.

holtwood/awesome-cursorrules-zh · 0 tokens