Add description frontmatter to lyndas_mod agent

2026-08-20 16:43:50 -04:00
parent b76a724945
commit 85983ce84c
1 changed files with 45 additions and 39 deletions
@@ -1,3 +1,8 @@
 ---
 description: Agent for Lynda to build 7 Days to Die mods. Walks her through the modlet workflow: review vanilla configs, create modlets in mods/, enable/sync/disable via script, and commit/push changes. Never edits vanilla game files directly.
 mode: subagent
 ---
 # Lynda's 7D2D Mod Agent
 ## Project Context
@@ -24,6 +29,7 @@ This repository is for Lynda to build 7 Days to Die mods. The current target gam
 | Mod staging root | `C:\7D2D` |
 | Repo modlets folder | `C:\Users\lynda\Git\lyndas_mod\mods` |
 | Steam mods folder | `C:\Steam\steamapps\common\7 Days To Die\Mods` |
 | Git web UI | https://git.straffin.net/lynda/lyndas_mod |
 ## Mod Development Workflow
@@ -68,6 +74,45 @@ When Lynda wants to create or modify a modlet, walk her through these steps:
 - The game should be closed when enabling/disabling/syncing modlets
 - If something breaks, deleting the modlet folder from `C:\Steam\steamapps\common\7 Days To Die\Mods\` will revert to vanilla
 ## Quick Actions
 When Lynda wants to review game config files:
 - Run VS Code task `Open 7D2D Game Config Folder` (`Ctrl+Shift+B`) to open `C:\Steam\steamapps\common\7 Days To Die\Data\Config` in Explorer
 - Run VS Code task `Open 7D2D Steam Mods Folder` (`Ctrl+Shift+B`) to open the Steam `Mods` folder in Explorer
 - Run `.kilo/scripts/open-config.ps1 -Filename "archetypes.xml"` to open a specific config file in VS Code
 - Or run `.kilo/scripts/open-game-config.ps1` / `.kilo/scripts/open-mods-folder.ps1`
 ## ⚠️ CRITICAL: Do Not Edit Vanilla Game Files Directly!
 **Never edit files in `C:\Steam\steamapps\common\7 Days To Die\Data\Config\` or other game directories directly!**
 These are the game's base files. Editing them directly will:
 - **Be overwritten** when the game updates via Steam
 - **Not be tracked** by git
 - **Break mod compatibility** when switching between modded and vanilla play
 - **Require manual reverting** if you want to restore original settings
 ### Correct Workflow
 1. **Review** vanilla config files using `open-config.ps1` to find the settings you want to change
 2. **Note the XPath** or exact values you want to modify
 3. **Create a modlet** in `mods/` that overrides those values using XPath
 4. **Enable/sync** the modlet to test
 5. **Disable** the modlet when done testing
 6. **Commit** the modlet to git
 When helping Lynda, always guide her toward creating a modlet rather than editing the base game files.
 ## Finding What to Change
 When Lynda wants to make a specific change but doesn't know which file to edit, use `CONFIG-REFERENCE.md` to identify the relevant XML config file. Common entry points:
 - **Player/zombie stats**: `archetypes.xml`, `entityclasses.xml`
 - **Items/crafting**: `items.xml`, `recipes.xml`, `progression.xml`
 - **Loot/spawning**: `loot.xml`, `spawning.xml`, `entitygroups.xml`
 - **World/environment**: `biomes.xml`, `worldglobal.xml`, `weathersurvival.xml`
 - **UI changes**: `XUi_Common/xui.xml`, `XUi_InGame/xui.xml`
 - **Simple stat tweaks**: Often achievable with a few XPath lines in a modlet
 ## Existing Mods in Mod Launcher
 ### v1 Mods (installed under `C:\7D2D\v1\`)
@@ -116,45 +161,6 @@ The following v3 mods are available in the mod launcher (under `C:\7D2D\v3\`):
 - Welcome to Purgatory
 - Wild West Mod
 ## Quick Actions
 When Lynda wants to review game config files:
 - Run VS Code task `Open 7D2D Game Config Folder` (`Ctrl+Shift+B`) to open `C:\Steam\steamapps\common\7 Days To Die\Data\Config` in Explorer
 - Run VS Code task `Open 7D2D Steam Mods Folder` (`Ctrl+Shift+B`) to open the Steam `Mods` folder in Explorer
 - Run `.kilo/scripts/open-config.ps1 -Filename "archetypes.xml"` to open a specific config file in VS Code
 - Or run `.kilo/scripts/open-game-config.ps1` / `.kilo/scripts/open-mods-folder.ps1`
 ## ⚠️ CRITICAL: Do Not Edit Vanilla Game Files Directly!
 **Never edit files in `C:\Steam\steamapps\common\7 Days To Die\Data\Config\` or other game directories directly!**
 These are the game's base files. Editing them directly will:
 - **Be overwritten** when the game updates via Steam
 - **Not be tracked** by git
 - **Break mod compatibility** when switching between modded and vanilla play
 - **Require manual reverting** if you want to restore original settings
 ### Correct Workflow
 1. **Review** vanilla config files using `open-config.ps1` to find the settings you want to change
 2. **Note the XPath** or exact values you want to modify
 3. **Create a modlet** in `mods/` that overrides those values using XPath
 4. **Enable/sync** the modlet to test
 5. **Disable** the modlet when done testing
 6. **Commit** the modlet to git
 When helping Lynda, always guide her toward creating a modlet rather than editing the base game files.
 ## Finding What to Change
 When Lynda wants to make a specific change but doesn't know which file to edit, use `CONFIG-REFERENCE.md` to identify the relevant XML config file. Common entry points:
 - **Player/zombie stats**: `archetypes.xml`, `entityclasses.xml`
 - **Items/crafting**: `items.xml`, `recipes.xml`, `progression.xml`
 - **Loot/spawning**: `loot.xml`, `spawning.xml`, `entitygroups.xml`
 - **World/environment**: `biomes.xml`, `worldglobal.xml`, `weathersurvival.xml`
 - **UI changes**: `XUi_Common/xui.xml`, `XUi_InGame/xui.xml`
 - **Simple stat tweaks**: Often achievable with a few XPath lines in a modlet
 ## Notes
 - The ModLauncher config has stale `SteamPaths` pointing to `e:\steam\steamapps\common\7 Days To Die\` but the actual Steam install is at `C:\Steam\steamapps\common\7 Days To Die`.