Fix sandbox errors: use relative paths for cross-project file access

Skills used absolute paths (~/dev/claude/projects/claude-foundations/...)
which get blocked by Claude Code's sandbox when running from other projects.
Changed to relative paths (../claude-foundations/) with local-first fallback
and inline defaults so skills work regardless of sandbox restrictions.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Paul O'Reilly
2026-03-15 22:33:47 +13:00
parent ee5f4b23ce
commit bb6fb72705
3 changed files with 7 additions and 7 deletions

View File

@@ -15,19 +15,19 @@ You are extracting generalisable best practices from project-specific memory fil
## Pre-gathered context
### Distill state
!`cat ~/dev/claude/projects/claude-foundations/best-practices/.distill-state.json 2>/dev/null || echo "{}"`
!`cat ../claude-foundations/best-practices/.distill-state.json 2>/dev/null || echo "{}"`
### Settings
!`cat ~/dev/claude/projects/claude-foundations/settings.yaml 2>/dev/null || echo "No settings file found"`
!`cat settings.yaml 2>/dev/null || cat ../claude-foundations/settings.yaml 2>/dev/null || echo "No settings file found"`
### Current best-practices index
!`cat ~/dev/claude/projects/claude-foundations/BESTPRACTICES.md 2>/dev/null || echo "No index found"`
!`cat ../claude-foundations/BESTPRACTICES.md 2>/dev/null || echo "No index found"`
### Available best-practices files
!`ls -1 ~/dev/claude/projects/claude-foundations/best-practices/ 2>/dev/null || echo "No best-practices directory"`
!`ls -1 ../claude-foundations/best-practices/ 2>/dev/null || echo "No best-practices directory"`
### Projects directory listing
!`ls -1d ~/dev/claude/projects/*/ 2>/dev/null || echo "No projects directory"`
!`ls -1d ../*/ 2>/dev/null || echo "No projects directory"`
## Instructions