ytmdesktop2 / rules
Cursor rule1.1k starsChanged 42 days agoCC0-1.0View on GitHub
Renderer render hygiene — useMemo only for expensive work, stable props
Trending
More talk lately.thin dataabout the whole repository
Who's talking about Venipa/ytmdesktop2
- neverh8me/yt-music“Вхід через Google: не працює на macOS та iPhone, нестабільно на ПК”GitHub · Nov 10, 2026
- amnweb/yasb“Media widget not compatible with "Youtube Music for Desktop" (unofficial application)”GitHub · May 21, 2026
- XeroxDev/YTMD-StreamDeck“[QUESTION]: ytmdesktop repository is gone”GitHub · Mar 5, 2024
- nklayman/vue-cli-plugin-electron-builder“mac build: fsevents Unexpected character (1:0)”GitHub · Apr 20, 2021
The biggest 4 of 4 mentions linking to the repository that our crawl found. Each line is their own headline.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,243 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository2 other files it gives its agents.
- .cursor/rules/commit.mdcCursor rule
- .cursor/rules/trpc-hooks.mdcCursor rule
The file
We split this react-render.mdc into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use only for expensive derived work (loops over lists, sorting, formatting heavy structures, style objects rebuilt from many inputs) or …
- Very specific: line 27
Use when passing a function to a memoized child, or as a dependency of useEffect / another memo that would otherwise churn.
- Very specific: line 33
Keep list keys stable; avoid inline {} / [] / lambdas in hot JSX props when the child is memoized
≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
---
description: Renderer render hygiene — useMemo only for expensive work, stable props
globs: src/renderer/**/*.{ts,tsx}
alwaysApply: false
---
# Render + memo
Goal: right state/props change → right render. No blanket memo.
## useMemo — when
Use only for **expensive** derived work (loops over lists, sorting, formatting heavy structures, style objects rebuilt from many inputs) or when a **stable reference** is required by a child that depends on referential equality.
```tsx
// ✅ expensive / referential
const time = useMemo(() => formatTrackTime(progress, duration), [progress, duration]);
const rootStyle = useMemo((): CSSProperties => ({ backgroundImage: accent }), [accent]);
// ❌ cheap / noise
const label = useMemo(() => title ?? "Unknown", [title]);
const isPlaying = useMemo(() => !!state?.playing, [state?.playing]);
```
## useCallback — when
Use when passing a function to a memoized child, or as a dependency of `useEffect` / another memo that would otherwise churn. Do **not** wrap every handler by default.
## Prefer fixing data flow first
1. Narrow state — don't put unrelated fields in one object that re-renders everything
2. Derive cheap values inline during render
3. Keep list keys stable; avoid inline `{}` / `[]` / lambdas in hot JSX props when the child is memoized
4. Colocate state near the consumer; lift only when shared
```tsx
// ❌ new object every render into memoized child
<Panel style={{ opacity }} onClick={() => doThing(id)} />
// ✅ stable when it matters
const style = useMemo(() => ({ opacity }), [opacity]);
const onClick = useCallback(() => doThing(id), [id]);
<Panel style={style} onClick={onClick} />
```
## Don't
- Memo "just in case"
- `useMemo` around tRPC hook results (hooks already own caching)
- Duplicate server/cache state into local `useState` without a sync need
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

