timoncooltimoncool/YuE2-Studio/AGENTS.md

YuE2-Studio

AGENTS.md2k starsChanged 28 days agoMITView on GitHub

This is a native Windows desktop studio: Tauri 2 shell, Rust/Axum service and native C++/CUDA engines.

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 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.
- docs/llms.txtllms.txt
- llms.txtllms.txt

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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:
Do not add Python or Node.js to the runtime path.
line 5
Distinctive:
Keep OpenRouter model identifiers in provider configuration, not source code.
line 8
Distinctive:
Every local engine must expose install state, capability metadata, cancellation and progress before it reaches the UI.
line 9

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

AGENTS.md

YuE2 Studio guidelines

This is a native Windows desktop studio: Tauri 2 shell, Rust/Axum service and native C++/CUDA engines.

Do not add Python or Node.js to the runtime path.
Model engines are adapters; no UI or server code may hardcode one model's behaviour.
Provider choice is capability-level: music, ASR, LLM and cover art can independently be Local or OpenRouter.
Keep OpenRouter model identifiers in provider configuration, not source code.
Every local engine must expose install state, capability metadata, cancellation and progress before it reaches the UI.
Model weights, API keys, media and caches are runtime user data; never commit them.

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free