dayz-mod-workflowlisted
Install: claude install-skill willy92wins/DayZ-Modding-Knowledge-Pack
# DayZ Mod Implementation & Debug Protocol
Process skill for implementing and fixing DayZ mods. Does not contain domain
knowledge (that lives in domain skills). Ensures domain knowledge is correctly
applied and gaps are detected before they become bugs.
(until 1.29: the six-layer debug hierarchy, SyncVar rules, and E01–E20 catalog below remain the 1.29 contract.) (since 1.30: client start also gates on `CanBeStarted()`; vanilla water uses `CCTLiquid`; CE adds `MotorbikeScript`/`HouseDestructible`; `cfggameplay.json` gained lock/sandstorm keys. Details: [dayz-1-30-mod-workflow.md](references/dayz-1-30-mod-workflow.md).)
---
## 1. ACTIVATION CHECK
Pre-code ceremony routing (which gate applies when — Grill A → `dayz-feature-spec` → Grill B → this skill) is fixed by the single source: `<vault>\AI\00_System\workflow.md` §Árbol de decisión pre-código. Do not self-declare this skill mandatory without that context. (SP-050)
Before writing or fixing ANY code:
- [ ] Is there an approved plan/design? If NO -> plan first.
- [ ] Which domain skills apply? Load them NOW (not from memory):
- Enforce Script -> `enforce-script-reference`
- UI/layout -> `dayz-ui-development`
- Particles -> `dayz-particles`
- 3D models -> `dayz-model-pipeline`
- PBO packaging -> `dayz-pbo-build`
- Physics/collision/raycast -> `dayz-physics-engine`
- Sound/CfgSoundSets -> `dayz-sound-system`
- AI/infected/creature behavior -> `dayz-ai-patterns`
- Build+deploy+launch loop -> `dayz-test-ing