SuperAPI AI Directory

skyrim-versioned-workspace

Coding & development

View repository

Updated 10-30 17:19

About this skill

Versioned Skyrim workspace

Workspace selection

The workspace root is the directory the user opened, supplied, or explicitly selected. Do not assume a drive letter, username, folder name, or separate provider-owned workspace.

Several AI applications may work in the same workspace. They share one authoritative project root and one active version. Switching applications is not a reason to clone or relocate the project.

Project layout

<WORKSPACE_ROOT>\<Mod Display Name>\
  WORKSPACE_OWNERSHIP.md
  CHANGELOG.txt
  CURRENT.txt
  PLAN.md
  STATE.md
  VALIDATION.md
  MEMORY\
  <Mod Display Name> 1.0.0\
    VERSION.txt
  <Mod Display Name> 1.0.1\
    VERSION.txt

Before editing

  1. Resolve the authoritative project from CURRENT.txt, ownership records, supplied archives, and read-only installed evidence.
  2. Reject deployed, staging, save, profile, and installed-tool paths as writable roots.
  3. Read CURRENT.txt, CHANGELOG.txt, STATE.md, and known-good records.
  4. Choose the semantic version bump.
  5. Fully copy the current snapshot into the new version folder.
  6. Update CURRENT.txt.
  7. Create or update the new snapshot's VERSION.txt.
  8. Start the changelog entry before modifying the new snapshot.
  9. Edit only the new snapshot.

Preflight guard

scripts/guard.py is bundled with this skill. It refuses the three failures that prose alone has not prevented: writing into a read-only realm, launching a GUI tool, and destroying UTF-8 through a PowerShell round-trip.

Run it before the write, not after:

python scripts/guard.py path "<intended write target>"
python scripts/guard.py cmd  "<intended shell command>"

Exit 0 allows the action. Exit 2 blocks it and prints the reason and the supported alternative. python scripts/guard.py --selftest verifies the rules.

The guard identifies deployed and managed realms from filesystem evidence (SkyrimSE.exe, ModOrganizer.ini, Vortex.exe in an ancestor directory), so no drive letter, username, or folder name is assumed. Set SKYRIM_GUARD=off only when the user explicitly asks to bypass it, and report that you did.

Claude Code installs this same script as a PreToolUse hook and it blocks automatically. Every other application must call it explicitly before the action.

Rules

  • Never overwrite the previous version.
  • Never mark a partial copy as current.
  • Record the AI application, model, reasoning mode, parent version, intended changes, changed files, commands, validation, runtime status, and unresolved risks.
  • Regenerate disposable build caches after moving or duplicating projects.
  • Scan generated projects for stale absolute paths.
  • Preserve the previous version for rollback and binary comparison.
  • Record ownership transfers explicitly. A transfer changes the owner record, not the physical workspace merely because another AI is used.

Completion

Report the workspace root, project root, parent version, active version, copied file count, changelog status, build status, final package hash, and remaining risks.

Claude Code execution adapter

  • Keep CLAUDE.md concise 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

Resolve authoritative ownership before the first write and never author inside deployed game or manager paths.

Authority and handoff gate

Before copying a version, inventory the active project, supplied archives, and read-only installed/deployed evidence. Explain which parent is authoritative.

After a move or copy, regenerate disposable build caches and scan for absolute paths outside the active snapshot. Cross-application handoffs record exact paths, hashes, active version, last successful build, and next required command.