stalker-soc-project-setuplisted
Install: claude install-skill webpnk/stalker-soc-skills
> `<skills>` below = the folder that contains this skill family (e.g. `%USERPROFILE%\.claude\skills` for a manual install, or the plugin's `skills` folder).
# SoC mod workspace setup
Everything here was verified on SoC 1.0006 (GOG, Russian, xrCore build 3312). Other skills in this
family: `stalker-soc-test-loop` (run and drive the game from Claude's shell), `stalker-soc-lua`,
`stalker-soc-npc`, `stalker-soc-quests`, `stalker-soc-items`, `stalker-soc-spawn`, `stalker-soc-art`.
## Golden rules
1. **Never modify the user's game install.** Work in a copy: `bin\` copied, `gamedata.db*` hard-linked
(same volume) so it costs no disk. Never write to the hard-linked `.db` files.
2. **Sources vs outputs.** Hand-edited sources live in `src\` (UTF-8). `game\gamedata\` is a build
output (cp1251), rebuilt by `src\tools\build.ps1`. Art and spawn are generated by scripts too.
3. **One prefix for everything new** (scripts, sections, info portions, string ids, spawn names),
e.g. `mymod_`. Easy to grep, no vanilla collisions.
4. **Override vanilla files by patch, not by copy-and-edit.** `src\tools\overrides.ps1` lists exact
find/replace edits applied to the vanilla file from `unpacked\`. Each anchor must match exactly
once or the build stops. Mark inserted code with `-- <PREFIX>:` / `<!-- <PREFIX>: -->`.
5. Commit after every task that works.
## Scaffold a workspace
```powershell
& "<skills>\stalker-soc-project-setup\scripts\new_workspace.ps1" `
-Root C:\stalker-mymod