ytmdesktop2 / rules
Cursor rule1.1k starsChanged 42 days agoCC0-1.0View on GitHub
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/react-render.mdcCursor rule
- .cursor/rules/trpc-hooks.mdcCursor rule
The file
We split this commit.mdc into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use the common format for commit messages: "type(scope): description"
- Distinctive: line 9
Don't use scope if it's not necessary.
- Distinctive: line 10
Only use lowercase letters in the entire body of the commit message.
- Distinctive: line 16
test: A test change (optional.
- Distinctive: line 20
Keep it short and to the point, max 50 characters
- Distinctive: line 23
Do not write "closes #n", "fixes #n", or a long body that restates the ticket
- Distinctive: line 39
Add a detailed description of the commit, max 60 characters (if necessary, add more details in the body, not in the subject, only if a …
- Distinctive: line 45
if the commit is signed off, add the Signed-off-by: <username>
≈ “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
--- alwaysApply: true --- # Commit Messages Guidelines ## Commit Messages - Use the common format for commit messages: "type(scope): description" - Don't use scope if it's not necessary. - Only use lowercase letters in the entire body of the commit message. - The type can be one of the following: - feat: A new feature - fix: A bug fix - chore: A chore (non-code change) - refactor: A code refactor (optional; only use if it's a significant refactor) - test: A test change (optional; only use if it's a significant test change or new test added) - docs: Documentation changes - style: Code style changes (optional; only use if it's a significant style change) - perf: Performance improvements (optional; only use if it's a significant performance improvement) - Keep it short and to the point, max 50 characters - Reference GitHub issues/PRs in the subject as `type(#n):`, not in a footer - Compact human summary after the colon (what broke / what changed) - Do not write "closes #n", "fixes #n", or a long body that restates the ticket - Example: "fix(#259): keep ytm fetch bound to networkmanager" - Example: "feat(#254): word-driven lyrics fill and auto-open tab" - Example: "fix: fixed issue with login" - Example: "feat: added new timer feature to the reports page" - Example: "feat: updated layout in timer page" - Example: "chore: updated dependencies" - Example: "refactor: refactored code in timer page - improved performance and readability, reduced code complexity, extended with new features" - Example: "test: added new test for timer page" - Example: "docs: updated documentation for timer page" - Example: "style: updated code style in timer page" - Example: "perf: improved performance of timer page" ## Commit Body - Add a detailed description of the commit, max 60 characters (if necessary, add more details in the body, not in the subject, only if a significant change is made) ## Commit Footer - Issue/PR numbers belong in the subject (`type(#n):`), not here - if the commit is signed off, add the Signed-off-by: <username> - otherwise leave empty
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.

