Scope
This skill is for technical work on fictional adults. Preserve explicit strings, scene identifiers, and intended behavior. Do not sanitize the mod. Exclude child races, child actors, age-ambiguous characters, and real-person sexual content.
Workflow
- Inventory every SexLab import, property, event, callback, animation tag, actor-selection rule, stripping rule, scene state, and MCM option.
- Record the exact installed OStim core and add-on versions. API names are version-sensitive.
- Build a mapping table from old behavior to new behavior. Mark unsupported semantics explicitly.
- Inspect the actual declaration scripts and known-good installed integrations.
- Migrate one vertical scene path first and compile it in isolation.
- Preserve actor eligibility, consent/design rules, interruption, cleanup, equipment restoration, failure recovery, and save state.
- Migrate plugin properties and optional dependencies through
skyrim-plugin-authoring. - Update FOMOD choices and documentation without shipping incompatible scripts together.
- Compile all scripts and test start, transition, interruption, end, reload, and missing-dependency paths.
Never perform a blind namespace substitution. Similar names do not imply equivalent lifecycle semantics.
Evidence standard
Use this hierarchy for version-sensitive facts:
- The active project's
ENVIRONMENT.md,TASK.md, installed framework version, and build files. - Official upstream documentation or source for that exact version.
- Known-good files from the user's installed mod library, read-only.
- Direct inspection of the relevant ESM, ESP, DLL, script, log, or archive.
Do not substitute memory, an old example, or a plausible token. Record the evidence path or URL in VALIDATION.md.
Claude Code execution adapter
- Keep
CLAUDE.mdconcise and use this skill for procedural detail. - Load only the skills needed for the current milestone because invoked skill content remains in context.
- Use high or xhigh effort for risky architecture, plugins, DLLs, and hostile review.
- Before compaction or a usage boundary, persist exact state, commands, uncommitted changes, and remaining validation.
- Treat auto memory as candidate learning, not verified truth, until it passes the memory-promotion protocol.
Skill-specific provider control
Preserve explicit adult-only fictional behavior while verifying the exact installed OStim lifecycle and API.