Protect Local Boundary
Keep private .local state usable without letting it become a dependency of shared project behavior.
When to use
Section titled “When to use”Protect a repository’s .local/ privacy boundary whenever work may create, read, write, copy, move, derive, watch, build, test, package, document, or promote .local content. Use for every planned or actual operation involving .local; do not use for a conceptual mention with no operation.
Link this skill
Section titled “Link this skill”arcantry skills link protect-local-boundary --scope userThe standard destination is ~/.agents/skills. Codex reads this universal Agent Skills location directly.
Claude compatibility
Section titled “Claude compatibility”arcantry skills link protect-local-boundary --scope user --compat claudeThis keeps the universal link and adds a Claude alias to the same canonical package.
Learning outcomes
Section titled “Learning outcomes”- Resolve the private boundary even when .local does not exist yet.
- Choose private, shared, promotion, or outside-repository handling for each operation.
- Prevent private files and workarounds from entering tracked configuration, tooling, packages, or product behavior.
Examples
Section titled “Examples”Create private state for the first time
Section titled “Create private state for the first time”Prompt
Use the protect-local-boundary skill before creating a new .local workspace in this Git repository.
Expected outcome
The absent directory is treated as private, locally excluded before creation, and kept independent from tracked project configuration.
Promote one input without watcher leakage
Section titled “Promote one input without watcher leakage”Prompt
Use the protect-local-boundary skill to turn one approved file from .local into a project asset while a repository-wide development watcher is active.
Expected outcome
Only the approved item becomes a self-contained project asset, while temporary work stays outside the repository and shared tooling remains independent from .local.