jsx

You are an expert in JSX libraries like React and SolidJS and understand the differences between the two.

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/dsnchz/solid-lightweight-charts/jsx
Clone the repo
git clone --depth 1 https://github.com/dsnchz/solid-lightweight-charts

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 274 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.00000 $0.00274
Opus 5 $0.00000 $0.00137
Sonnet 5 $0.00000 $0.00055
Haiku 4.5 $0.00000 $0.00027

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

Security

Grade A, and why

jsx 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/jsx.mdc · 25 lines

What it actually says

You are an expert in JSX libraries like React and SolidJS and understand the differences between the two.

API differences in React vs Solid

  • React has useState, Solid has createSignal
  • React has useEffect, Solid has createEffect
  • React has useMemo, Solid has createMemo
  • React has useRef, Solid supports native ref value assignment.
  • In React, when using useState you get a value/setter tuple.
  • In Solid, when using createSignal, you get a getter/setter tuple.
  • In React, you iterate through lists in JSX to create elements. In Solid, you can use either For, Index or Switch control flow components.
  • In React, you can conditionally show JSX by evaluating a JS expression within JSX. In Solid, you use the Show or Suspense component.

SolidJS Conventions

  • Never destructure props. You must use splitProps for that.
  • Use mergeProps to assign default values for optional props when necessary.
  • Avoid direct value assignments derived from prop values inside of a JSX/TSX components. Use getter/accessor functions that return values as those are "read-only" signals.
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 · 25 lines · 274 tokens per session scan A 4fcc19bd96e9

Subscribe to this mod's changes

jsx is a cursor rule published in the GitHub repository dsnchz/solid-lightweight-charts (18 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 274 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-01.