ytmdesktop2 / rules
Cursor rule1.1k starsChanged 42 days agoCC0-1.0View on GitHub
tRPC React Query hook destructuring naming in renderer
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/react-render.mdcCursor rule
The file
We split this trpc-hooks.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Always destructure mutateAsync as the procedure name.
≈ “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: tRPC React Query hook destructuring naming in renderer
globs: src/renderer/**/*.{ts,tsx}
alwaysApply: false
---
# tRPC hook destructuring
Name hooks after the **procedure** (last segment of the path), not the mutation/query object.
## useMutation
Always destructure `mutateAsync` as the procedure name. Pull `error` / `isPending` (or `isLoading`) only when used.
```tsx
// ✅
const { mutateAsync: minimize } = trpc.app.minimize.useMutation();
const { mutateAsync: check, isPending: checkPending, error: checkError } = trpc.update.check.useMutation();
await minimize();
// ❌
const minimize = trpc.app.minimize.useMutation();
minimize.mutateAsync();
const minimizeMutation = trpc.app.minimize.useMutation();
```
## useQuery
Destructure `data` as the procedure name. Pull `error` / `isPending` / `isLoading` only when used.
```tsx
// ✅
const { data: isWin11 } = trpc.app.isWin11.useQuery();
const { data: updateInfo = null, isPending: updatePending } = trpc.update.get.useQuery();
// ❌
const updateQuery = trpc.update.get.useQuery();
updateQuery.data;
const { data } = trpc.update.get.useQuery(); // unnamed / generic
```
## Notes
- Alias = procedure key: `trpc.track.togglePlay` → `mutateAsync: togglePlay`
- Defaults on `data` OK: `data: updateDownloaded = false`
- Subscriptions stay `useSubscription`; this rule is for query/mutation only
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.

