agentleFS
Sign inStart free
sandraschisandraschi/songgeneration-mcp/.github/copilot-instructions.md

songgeneration-mcp

Copilot instructions4 starsChanged 32 days agoMITView on GitHub

Local open-weight music generation: Tencent SG2/LeVo2 via Studio, plus Lyria, ACE-Step, MusicGen, Stable Audio backends. Before starting work: 1. Check backend state: GET /api/v1/diagnostics 2. Skill: skills/SKILL.md (also served at GET /api/skills) At end of work: - Unload VRAM: unloadmodels if no further generations planned - Never invent model names - listmodels first

We split this copilot-instructions.md into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check backend state: GET /api/v1/diagnostics

    line 6
  2. Very specific:

    Never invent model names - list_models first

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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
copilot-instructions.md

Session Context (songgeneration-mcp)

Local open-weight music generation: Tencent SG2/LeVo2 via Studio, plus Lyria, ACE-Step, MusicGen, Stable Audio backends.

Before starting work:

  1. Check backend state: GET /api/v1/diagnostics
  2. Skill: skills/SKILL.md (also served at GET /api/skills)

At end of work:

  • Unload VRAM: unload_models if no further generations planned
  • Never invent model names - list_models first

Download now (ZIP)

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 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 repository7 other files it gives its agents.

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