Moss-Mcp-Transaction
Copilot instructions1 starsChanged 3 months agoMITView on GitHub
Notes: - Do not use alternatives like YES/NO unless space constraints force it. - Do not misspell RPC as PRC. - Keep System Error as a phrase; do not split into separate terms unless required by layout.
In this repository5 other files it gives its agents.
The file
Show its rules and text
We split this copilot-instructions.md into the rules it gives an agent
20 rules. About 0 are common, 13 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Do not put long text on edges.
- Distinctive: line 9
Avoid inline edge labels whenever possible.
- Distinctive: line 10
If an edge label is required, keep it one word and single-line.
- Distinctive: line 11
Prefer moving explanatory text into nodes.
- Very specific: line 12
Do not use <br/> inside edge labels.
- Very specific: line 13
Keep decision labels short: Yes, No, Retry, Back.
- Very specific: line 14
Keep transition labels short: Sign, Reject, Revert, Error.
- Distinctive: line 16
If clipping appears, first shorten/remove edge labels.
- Distinctive: line 17
Only after label shortening, adjust spacing values:
- Very specific: line 21
If GitHub still clips text, force short line breaks inside nodes (for example System<br/>Error, React<br/>UI) and increase diagramPadding.
- Very specific: line 32
Do not use alternatives like YES/NO unless space constraints force it.
- Very specific: line 33
Do not misspell RPC as PRC.
- Very specific: line 34
Keep System Error as a phrase.
- Distinctive: line 38
Keep English and Chinese diagram logic synchronized.
- Distinctive: line 39
Keep node and edge counts aligned across EN/ZH versions.
- Distinctive: line 40
Prefer stable GitHub-compatible Mermaid syntax.
- Distinctive: line 41
Avoid advanced Mermaid features that render inconsistently on GitHub.
- Distinctive: line 45
Put details in node text blocks.
- Distinctive: line 46
Keep arrows mostly unlabeled.
- Distinctive: line 47
Use labels only for critical branch decisions.
≈ “Common” is an estimate: at least 1 in 5 of the 3,827 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.
Files
Repository Copilot Instructions
Scope
These rules apply when generating or editing Mermaid diagrams, especially in README files.
Mermaid Anti-Clipping Rules (GitHub Renderer)
- Do not put long text on edges.
- Avoid inline edge labels whenever possible.
- If an edge label is required, keep it one word and single-line.
- Prefer moving explanatory text into nodes.
- Do not use
<br/>inside edge labels. - Keep decision labels short:
Yes,No,Retry,Back. - Keep transition labels short:
Sign,Reject,Revert,Error. - For Chinese labels, keep to 2-4 characters where possible.
- If clipping appears, first shorten/remove edge labels.
- Only after label shortening, adjust spacing values:
- increase
nodeSpacingslightly - increase
rankSpacingslightly
- For status diagrams, prefer plain single-line node labels (no emoji, no
<br/>) for:Pending,System Error,Awaiting Signature. - If GitHub still clips text, force short line breaks inside nodes (for example
System<br/>Error,React<br/>UI) and increasediagramPadding.
Canonical Terminology (Use Exactly)
YesNoPendingSystem ErrorUI
Notes:
- Do not use alternatives like
YES/NOunless space constraints force it. - Do not misspell
RPCasPRC. - Keep
System Erroras a phrase; do not split into separate terms unless required by layout.
README Diagram Editing Checklist
- Keep English and Chinese diagram logic synchronized.
- Keep node and edge counts aligned across EN/ZH versions.
- Prefer stable GitHub-compatible Mermaid syntax.
- Avoid advanced Mermaid features that render inconsistently on GitHub.
Preferred Pattern
- Put details in node text blocks.
- Keep arrows mostly unlabeled.
- Use labels only for critical branch decisions.
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.

