Scopes & lock files
Where files are installed and how the lock files work.
| Scope | Install path (Kiro target) | Lock file |
|---|---|---|
| Workspace (default) | .kiro/steering/<name>.md | steering-lock.json |
Global (-g) | ~/.kiro/steering/<name>.md | ~/.steering/steering-lock.json |
Each target format installs into its own directory (e.g. .cursor/rules/ for
Cursor); the paths above are for the Kiro target. The global lock lives in a
neutral ~/.steering/ directory since installs can span multiple formats.
The workspace lock is minimal (no hashes or timestamps) to avoid git merge
conflicts. Update detection recomputes the installed file's blob SHA when you
run check / update.
Commit steering-lock.json to your repo: it's what lets your team restore the
same context.