Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
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 | new-culture |
| description | 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. |
| argument-hint | ["culture-id"] |
End-to-end authoring of a culture's visible-in-game armor + troops + recruitment. Read the authoritative guide first: docs/ai-includes/new-culture-authoring.md. This skill is the entry point + checklist; the guide has the full per-phase detail (modeled on the Dale session, ~11 commits).
GoT re-skin (2026-06-13): DOTS is now Game of Thrones (Robert's Rebellion). Culture model is region = culture, great house = clan โ use the GoT StringIds in ADR-011 /
.claude/rules/xml-data.md(e.g. the North'sculture=value issturgia, notnorth/stark). The armor half of this flow (Phases 0โ1) below still describes the retired LOTRLOME pipeline (generate_dale_armor.py,LOTRLOME_items/). The new armor source is A Dance of Dragons Armory (ModuleData/ADOD-Assets/region files); the ADoD armor-wiring pipeline is re-established in the conversion's Phase B. Until then, the culture definition + troop tree + recruitment steps (Phases 2โ4) are the live, GoT-ready parts.
.tpac armor pack to wire in, ORIf creating a net-new dots_spcultures.xml Culture object, read docs/cultures.md FIRST (the ~80 culture attributes + 16 NPC files). This flow picks up after the culture definition exists.
.claude/rules/xml-data.md, NOT a lore name for vanilla-base cultures); decide tier cap; pick 3โ4 ASOIAF/Westeros lore citations; identify the culture's ADoD item folder (North.xml, Dorne.xml, โฆ).tools/tpac_skeleton_scan.py --all-types) โ clone tools/generate_dale_armor.py โ emit XML โ register the <culture>/ folder in LOTRLOME_Armory/SubModule.xml.troops_<culture>.xml โ register in Main/_Module/SubModule.xml.spcultures.xslt (every CultureObject template/troop attr), dots_partyTemplates.xml (9 templates), VolunteerRecruitmentService.cs (culture + optional settlement/clan pools), add tests.python tools/validate_all_troop_refs.py (underwear-bug gate), then /ship.chivlary/infrantry).LOTRLOME_items/*/ for the item prefix before authoring; first folder with that prefix wins (CLAUDE.md per-prefix table). Wrong folder = duplicate-ID shadowing.covers_legs="true", gloves covers_hands="true", or the mesh doesn't render (bare legs/hands).<Flags UseTeamColor="true" /> on every armor item for banner tint./xslt-check after editing spcultures.xslt.