azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from GURU-BEAST-ROG at 2026-06-14 09:07:13

Browse Source 
Author: Mike Swanson
Machine: GURU-BEAST-ROG
Timestamp: 2026-06-14 09:07:13
This commit is contained in:
Mike Swanson
2026-06-14 09:07:18 -07:00
parent 4fd5688026
commit a6b6b4e80a
3 changed files with 74 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
.claude/ONBOARDING.md
View File

@@ -35,6 +35,20 @@ Some configuration files are **machine-local** (gitignored, not synced) because
|------|---------|---------------|
| `.claude/identity.json` | Your name, email, vault path | YES — during onboarding |
| `.claude/current-mode` | Work mode (dev, infra, client, etc.) | YES — defaults to "general" |
| `.claude/settings.local.json` | Per-machine env (`CLAUDETOOLS_ROOT`) + local permissions | env via provisioner (below) |
**`CLAUDETOOLS_ROOT` env — run once per machine after `identity.json` exists:**
```bash
py .claude/scripts/ensure-settings-env.py
```
This seeds `env.CLAUDETOOLS_ROOT` in `.claude/settings.local.json` from
`identity.json.claudetools_root`. Many skill docs invoke
`py "$CLAUDETOOLS_ROOT/.claude/skills/.../x.py"`; Claude Code injects the settings `env`
block into every Bash call, so without this the var is empty and those commands resolve to
the wrong path (the failure logged in `errorlog.md` on 2026-06-14). Idempotent; takes effect
at the next session start. The script is also safe to re-run any time the clone moves.
**`.claude/current-mode`** is used by coordination hooks to determine behavior:
- In `dev` mode: Hooks show active locks as warnings but don't block