html-react-rules

Coding rules for NotePlan plugins, including how to import modules, handle promises, and update notes. NotePlan is a note-taking application with its own JavaScript runtime and built-in APIs.

In plain words
What is it for?
Use them when creating or modifying NotePlan plugin code, especially code that waits for conditions, edits notes, or works with page elements.
Why use it?
They prevent compatibility problems caused by unsupported JavaScript features, incorrect imports, or using the wrong build process.

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/noteplan/plugins/html-react-rules
Clone the repo
git clone --depth 1 https://github.com/NotePlan/plugins

Made for: Cursor.

Per session 968 This file is loaded in full into every session.
When invoked 968 The same file — it is already loaded in full.
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.00968 $0.00968
Opus 5 $0.00484 $0.00484
Sonnet 5 $0.00194 $0.00194
Haiku 4.5 $0.00097 $0.00097

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

Security

Grade A, and why

html-react-rules 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/rules/html-react-rules.mdc · 87 lines

How it starts

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

  • For NotePlan code, never use require statements. Use import statements at the top of the file -- never inline/dynamically import modules. Rollup will not process them correctly.

  • You should not ever try to build the code with "npm run build" -- this will not work. The programmer will have to use Rollup to build the code. There is separate tooling for this described in @README.md. Leave the building to the programmer.

  • NotePlan has global variables that are available to all plugins such as DataStore, CommandBar, Editor, and NotePlan. You can use these variables to access the NotePlan API. You do not need to import them.

Do not commit or push any changes until I tell you to.

Any time you create or are working on a DIV, make sure that DIV has a human-understandable class name so we can debug more easily

Promise Polyfills

Do not use raw Promise.resolve, Promise.all, or Promise.race in plugin code—NotePlan's JSContext may not have them. Use polyfills from @helpers/promisePolyfill.js: initPromisePolyfills(), promiseResolve(), promiseAll(), promiseRace(), waitForCondition(), setTimeoutPolyfill(). After creating/modifying notes, call DataStore.updateCache(note, true).

React Function Memoization (CRITICAL)

ALWAYS wrap functions passed to React Context or child components in useCallback. This prevents infinite render loops that crash the app.

// ❌ WRONG - Causes infinite loops
const requestFromPlugin = (command: string, dataToSend: any = {}) => { ... }

// ✅ CORRECT - Stable function reference
const requestFromPlugin = useCallback((command: string, dataToSend: any = {}) => {
  // ... implementation
}, [dispatch]) // Minimal dependencies

Functions that MUST be memoized:

  • requestFromPlugin, sendActionToPlugin, sendToPlugin
  • Any function passed to AppProvider props
  • Any function used in useEffect dependency arrays

AppContext MUST use useMemo:

const contextValue = useMemo(() => ({
  sendActionToPlugin, sendToPlugin, requestFromPlugin, dispatch, pluginData
}), [sendActionToPlugin, sendToPlugin, requestFromPlugin, dispatch, pluginData])

Read the full file on GitHub · 87 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. yesterday First seen · 87 lines · 968 tokens per session scan A b5351d7979a1

Subscribe to this mod's changes

html-react-rules is a cursor rule published in the GitHub repository NotePlan/plugins (204 stars, last pushed 2d ago), licensed MIT. It adds 968 tokens to every session, about $0.0048 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.