DayZ-Modding-Knowledge-Pack
Copilot instructions20 starsChanged 40 days agoMITView on GitHub
Canonical agent file: AGENTS.md. Summary below. This repository is a DayZ (Enfusion) modding knowledge pack: 42 domain playbooks in skills/, thirteen Python tools in tools/, verified reference notes in knowledge/. Do not load the pack wholesale — it is ~4 MB. Read every skills/*/SKILL.md front-matter first (each description is a set of trigger conditions), load the one whole SKILL.md that matches, and open files under its references/ only when the procedure names them. 1. Never invent an API. DayZ fails…
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,349 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 repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- 3d-generation-harnessSkill
- ai-3d-to-dayzSkill
- ardy-motion-generationSkill
- blender-animationSkill
- blender-assemblySkill
- blender-visual-reviewSkill
- dayz-3d-viewerSkill
- dayz-ai-patternsSkill
- dayz-animation-pipelineSkill
- dayz-aviationSkill
- dayz-basebuildingSkill
- dayz-charactersSkill
- dayz-clothingSkill
- dayz-doorsSkill
- dayz-environment-hazardsSkill
- dayz-feature-specSkill
- dayz-mcp-verifySkill
- dayz-model-pipelineSkill
- dayz-mod-workflowSkill
- dayz-motorbikesSkill
- dayz-p3d-auditSkill
- dayz-p3d-inspectorSkill
- dayz-particlesSkill
- dayz-pbo-buildSkill
- dayz-pbo-reverse-engineeringSkill
- dayz-persistenceSkill
- dayz-physics-engineSkill
- dayz-preflightSkill
- dayz-proxy-alignSkill
- dayz-realistic-animation-directorSkill
- dayz-sound-systemSkill
- dayz-test-ingameSkill
- dayz-texture-pipelineSkill
- dayz-ui-developmentSkill
- dayz-undergroundSkill
- dayz-vehiclesSkill
- dayz-weaponsSkill
- enforce-script-referenceSkill
- mixamo-retargetSkill
- ovh-cloudSkill
- rigorous-data-auditSkill
- rip-vehicle-importSkill
- systematic-debuggingSkill
- task-observerSkill
- uv-clean-atlasSkill
The file
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
- could be automatic: a setting could enforce it
- Very specific: line 11
Do not load the pack wholesale — it is ~4 MB.
- Very specific: line 28
Every executable claim needs a build/commit and a path:line.
≈ “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
Copilot instructions
Canonical agent file: AGENTS.md. Summary below.
This repository is a DayZ (Enfusion) modding knowledge pack: 42 domain
playbooks in skills/, thirteen Python tools in tools/, verified reference
notes in knowledge/.
Routing
Do not load the pack wholesale — it is ~4 MB. Read every skills/*/SKILL.md
front-matter first (each description is a set of trigger conditions), load the
one whole SKILL.md that matches, and open files under its references/ only
when the procedure names them.
The four rules
- Never invent an API. DayZ fails silently on confabulation. Grep the
vanilla source (
P:\scripts\) or a reference here and citepath:linebefore writing any Enforce Script call, config class or.p3dselection. - Respect the client/server split. Decide which side owns each value first.
- In-game tests cost 3–10 minutes. Batch changes; have a plan B.
- Be honest about verification. State what you checked, how, and what you did not. "It compiles" is not "it works".
Editing this repository
Every executable claim needs a build/commit and a path:line. No private paths,
credentials, vanilla or third-party assets. The pack is MIT and takes no GPL,
DPL-ND or CC-NC material.
python -m packctl gate --root . --report-dir ../pack-gate-reportsThe report directory must be outside the repository and PACK_SKILLS_REF_ROOT
must point at the Agent Skills validator; see AGENTS.md §Gates for both.
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.