Menü
Give TAOM lords lore-driven skill values and traits via the TAOM SkillSet system. Use when a canonical lord has wrong stats or a culture roster needs a balance pass.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | lord-skills |
| description | Give TAOM lords lore-driven skill values and traits via the TAOM SkillSet system. Use when a canonical lord has wrong stats or a culture roster needs a balance pass. |
| argument-hint | ["lord-name|culture"] |
Assign lore-driven skill values + personality traits to TAOM lords. Read the authoritative guide: docs/ai-includes/lord-skills-authoring.md (modeled on the 16-culture / ~880-NPC sweep, #228–#245).
Hero stats come from skill_template="SkillSet.taom_...", NOT from the NPCCharacter's <skills> block — explicit <skills> on heroes are IGNORED by the engine (kept as documentation only). To change a hero's skills, edit the SkillSet (or repoint skill_template). See memory feedback_skill_template_overrides_explicit_skills.md — Boromir showed OneHanded=145 instead of 295 because someone hand-edited <skills>.
characters/lords.xml, lords.xslt, heroes.xslt for the name → NPCCharacter id. Classify the layer: lords.xml (TAOM-new, wins at runtime) > lords.xslt (vanilla override, loses to lords.xml on same id) > heroes.xslt (bio text, stat-irrelevant).CULTURES dict in tools/apply_culture_skills_traits.py.python tools/apply_culture_skills_traits.py --all-cultures --apply emits 3 outputs: taom_lord_skill_sets.xml, updated lords.xml + lords.xslt (skill_template swaps + populated blocks)./commit-split (data vs tool separate); one GitHub issue per culture via tools/generate_culture_issue_drafts.py.lords.xml and lords.xslt, the lords.xml version is live; the XSLT one is dead code.Main/_Module/ModuleData/**/*.xml for the OLD name (lore flavor text goes stale silently — memory feedback_rename_grep_all_moduledata.md).Root-cause native Bannerlord CTDs (AccessViolation in TaleWorlds.Native.dll) via Event Log offsets, offline disassembly, and live debugger forensics. No symbols needed.
Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results
Inspect all changed files, group by logical concern, and guide atomic per-concern commits following TAOM's 50/72 rule and commit trailer convention.
Load a snapshot saved by /context-save and present it so this session can pick up where the last one left off without re-deriving decisions.
Launch parallel deep-dive agents to review completed work for quality, standards, compatibility, completeness, and cross-system data flow
Respond to a Bannerlord engine update (Steam force-bump or deliberate migration) — preserve the decompile baseline, regen, diff, re-verify bindings and creature data, control-battle.