← ClaudeAtlas

dayz-mod-workflowlisted

DayZ mod implementation and debugging protocol. Governs HOW to implement and fix, not WHAT. Client/server data mapping (mandatory before each feature), anti-confabulation (verify every API), debug hierarchy (top-down 6-layer diagnosis), edge case checklists, error catalog of verified recurring mistakes, checkpoint/handoff system for context degradation. Use ALONGSIDE domain skills (enforce-script-reference, dayz-ui-development, dayz-particles, etc.), not instead of them. Triggers: "implement", "write the code", "build the mod", "fix the bug", "debug this", "it doesn't work", "actions not showing", sprint execution, or any transition from plan to code/fix. Concurrent sessions, skill snapshot, live promote during an open session. Also: CanBeStarted, CCTLiquid, MotorbikeScript, HouseDestructible, cfggameplay ExternalLockData/SandstormData, PluginUndergroundTriggerManager, NVTypes underground/sandstorm, IsHeadless.
willy92wins/DayZ-Modding-Knowledge-Pack · ★ 25 · AI & Automation · score 78
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