mod-workspace-organizationlisted
Install: claude install-skill SenjuWoo/Ultimate-AI-Starter-Bundle
# Mod workspace organization
A mod project is not one folder of files. It has four different kinds of
content that must never be mixed: **source**, **package**, **release** and
**state**. A FOMOD package is a valid package root; it is not automatically the
project root, and it is never the place for caches, old snapshots or notes.
Read `workspace-organization` first for `WORKSPACE_OWNERSHIP.md`, the one owner
and the publication boundary. This skill adds the mod-specific layout and the
safe repair pass.
## Canonical layout
```text
<project>/
WORKSPACE_OWNERSHIP.md owner and publication intent
README.md public page
CHANGELOG.md
LICENSE
.gitignore
VERSION one current version, or .uabs/state.json
src/ source: ESP source, Papyrus, C++, scripts
assets/ source art, audio, textures, meshes, blend files
package/ clean install tree: fomod/, 00 Core/, 01 ...
docs/ notes, plans, decisions, presentation/
dist/ release zips and archives (git-ignored)
.uabs/ state, build receipts, backups (git-ignored)
tools/ project-local build/package scripts
```
A small mod may put the package at the project root (`fomod/`, `00 Core/`,
`01 .../`) and keep `src/`, `docs/`, `dist/` and `.uabs/` beside it. That is
valid only when the root package is the **current** package and nothing else is
dumped there. Version sna