Menú
Author a culture's armor items and swap troop equipment rosters via the generator + validation pipeline. Use when adding/revamping armor. Enforces the canonical-folder + cover-attribute rules.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Give DOTS lords lore-driven skill values and traits via the DOTS SkillSet system. Use when a canonical lord has wrong stats or a culture roster needs a balance pass.
Author or revamp a DOTS culture's armor set, troop tree, and recruitment wiring end-to-end. Use for new cultures or troop-tree revamps. Follows docs/ai-includes/new-culture-authoring.md.
Use when reviewing an external repo or article to adopt practices into DOTS — security-vet first, map novel vs duplicative, port (never install), review, commit your changes.
Structured 4-phase self-debug for failing agent runs (looping, drifting, burning tokens). Capture, diagnose, contained recovery, report. Complements /investigate (which is for code bugs); this skill is for harness/agent failures.
Incrementally fix dotnet build errors with minimal diffs, one error at a time
Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results
| name | author-armor |
| description | Author a culture's armor items and swap troop equipment rosters via the generator + validation pipeline. Use when adding/revamping armor. Enforces the canonical-folder + cover-attribute rules. |
| argument-hint | ["culture"] |
Author or revamp a culture's armor items and re-point troop equipment rosters. This is the armor-only flow (revamps like #99 / #211 / #212 / #224). For a brand-new culture (armor + troops + recruitment + culture wiring), use /new-culture instead.
GoT re-skin (2026-06-13): the LOTRLOME armory is retired. DOTS now draws items from A Dance of Dragons Armory (
ModuleData/ADOD-Assets/region files:North.xml,Dorne.xml,Ironborn.xml, …). TheLOTRLOME_items/folder layout +sk_*prefix conventions below are legacy pending the ADoD armor-wiring pipeline (conversion Phase B). Use Westeros culture ids from ADR-011 /.claude/rules/xml-data.md.
Reference: CLAUDE.md "Equipment & Armory" + "Rebalancing Tools" tables.
Before authoring ANY item, grep all LOTRLOME_items/*/ subfolders for the item-id prefix:
grep -rl 'sk_<prefix>_' "<armory>/ModuleData/LOTRLOME_items/"
The first folder that already contains that prefix is the canonical home. Authoring into a different folder creates runtime duplicate-ID warnings (the engine silently shadows one). Even when the spec is named for culture X, the home may be a sub-culture — e.g. sk_dwarf_iron_* lives in iron_hills/, NOT erebor/ (caught in #211). CLAUDE.md has the full per-prefix → folder table. Memory: feedback_multi_folder_id_uniqueness.md.
tools/generate_<culture>_armor.py (--dry-run then --apply; --armory-path to target the Steam install).covers_legs="true", gloves covers_hands="true", or the engine equips but doesn't render the mesh (bare legs/hands). Memory: feedback_lotrlome_armor_cover_attributes.md.<Flags UseTeamColor="true" /> for banner tint.<EquipmentRosters> civ rosters need equipmentType="Civilian" (battle is the implicit default) — memory feedback_equipmenttype_civilian_required.md.tools/apply_<culture>_troop_revamp.py --dry-run / --apply — mechanical EquipmentRoster swap (+ any new troops / deletes).tools/cleanup_deleted_troops_*.py, tools/expand_party_templates_*.py).python tools/validate_all_troop_refs.py
Cross-checks every sk_*/ar_*/clo_urukscout_*/urukscout_* ref across all 7 culture troop XMLs against the Armory. Missing refs → characters spawn in underwear. Prefer this over the Gondor-only validate_gondor_refs.py.
/ship if any C# changed; otherwise /verify + CHANGELOG + issue.
feedback_verify_troop_ids_against_canonical_xml.md).LOTRLOME_Armory (NOT Armory_2 — being deleted).