This skill owns bulk generation and cross-framework audit. Exact syntax belongs to each dedicated framework skill.
Inputs
- exact installed framework versions;
- source plugins and deployed load-order manifest;
- resolved source plugin, local FormID, EditorID, record type, and intended filters;
- written balance/classification policy;
- known-good parser examples;
- expected parsed, rejected, unresolved, and skipped counts.
Typed pipeline
- Extract source records with a typed parser.
- Store a typed intermediate CSV/JSON manifest.
- Validate one positive and one negative target per source plugin.
- Map the desired record class to the framework's actual key:
- SPID inventory forms, including weapons and staves:
Itemor genericForm; - never manufacture
Weapon =merely because the source record is WEAP.
- SPID inventory forms, including weapons and staves:
- Generate deterministically.
- Run the dedicated linter before deployment.
- Resolve every exact form against a deployed-plugin manifest.
- Compare source manifest count, generated count, parser accepted count, rejected count, unresolved count, and intended exclusions.
- Fail release when an entire generated feature family is rejected or resolves zero targets.
- Inspect runtime logs after deployment.
Framework separation
- SPID
*///,meanings are field-specific. - FLM permits special
*FormList,#Group, and#Collectionforms. - CDF JSON
adduses exact forms and does not inherit FLM wildcard syntax. - BOS alphabetical priority is not semantic conflict resolution.
- SkyPatcher operation names and paths remain category/version-specific.
Never copy punctuation or selector conventions between frameworks because they look similar.
Bulk-change gate
A mass replacement such as Weapon = to Item = is permitted only after:
- proving the old key is unsupported in the target SPID parser;
- confirming every affected row intends inventory-form distribution;
- validating representative forms from every source plugin;
- writing a reversible diff;
- rerunning parser and runtime logs;
- reconciling accepted/rejected counts exactly.
Stale dependency handling
Classify unresolved rows:
- hard requirement missing;
- conditional requirement missing;
- optional integration absent;
- stale config left after mod removal;
- typo or wrong local FormID/EditorID.
Do not delete hundreds of rows merely to quiet logs. Preserve useful optional integrations when their guard conditions are correct. Remove or repair dead rows in the owning source when their target can never resolve in the intended build.
Commands
scripts\audit_configs.py <tree>
..\skyrim-distr-kid-validation\scripts\lint_framework_configs.py <tree>
..\skyrim-container-distribution\scripts\lint_cdf_json.py <tree>
..\skyrim-runtime-log-forensics\scripts\analyze_runtime_logs.py <logs>