realtimevideogen
Copilot instructions10 starsChanged 7 months agoMITView on GitHub
See AGENTS.md for full repository instructions. Key rules are summarised below. Real-Time Multi-Modal Generation — modular, adaptive serving stack for video/audio/image generation on a Kubernetes cluster with GPU nodes.
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,336 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 repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this copilot-instructions.md into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 11
Async first: use async/await and aiofiles for I/O.
- Very specific: line 12
Logging: use the logger from console_utils.py.
- Very specific: line 13
K8s namespace: always rtgen.
- Distinctive: line 14
No secrets in source: use environment variables or Azure Key Vault.
- Distinctive: line 26
Must: add or update tests for every functional change.
- Very specific: line 27
Must: keep services.json valid (python -m json.tool services.json).
- Distinctive: line 28
Never: commit credentials, tokens, or secrets.
- Distinctive: line 29
Never: remove or weaken existing tests.
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 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
See AGENTS.md for full repository instructions. Key rules are summarised below.
Project
Real-Time Multi-Modal Generation — modular, adaptive serving stack for video/audio/image generation on a Kubernetes cluster with GPU nodes.
Quick reference
- Python 3.12; all functions must have type annotations (
mypystrict). - Line length: 120 characters max (flake8).
- Async first: use
async/awaitandaiofilesfor I/O; Quart as the web framework. - Logging: use the logger from
console_utils.py; no f-strings in log calls. - K8s namespace: always
rtgen. - No secrets in source: use environment variables or Azure Key Vault.
Lint & test (run before every PR)
flake8 . tests
mypy --install-types --non-interactive --ignore-missing-imports .
pytest --ignore=tests/simulator --ignore=tests/streamwise --ignore=tests/streamwise_app -vvMust / Never
- Must add or update tests for every functional change.
- Must keep
services.jsonvalid (python -m json.tool services.json). - Never commit credentials, tokens, or secrets.
- Never remove or weaken existing tests.
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.

