Agent skill · writing content · aiskillstore
file-boundaries
Pattern for respecting file ownership boundaries during implementation. Prevents conflicts in parallel work.
Why this skill is useful
Codifies a specific file ownership pattern to prevent conflicts in parallel work, which the AI could infer but now has clear guidelines.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
File Boundaries Skill Pattern for respecting file ownership in parallel work. When to Load This Skill You are implementing code with defined boundaries You're working in parallel with other agents You need to avoid file conflicts Boundary Rules Files You OWN You CAN: Read these files Modify these files Create new files in these paths Delete these files Files You READ You CAN: Read these files for reference Import from these files You CANNOT: Modify these files If you need changes → report BLOCKED Checking Boundaries Before modifying any file: 1. Is this file in my owns list? 2. If NO → STOP, don't modify 3. If need to modify → report BLOCKED with details Reporting Boundary Violations If you need to modify a file outside boundaries: Parallel Work Safety Boundaries exist to enable parallel work: Agent A owns src/auth/ Agent B owns src/api/ Both can work simultaneously without conflict If boundaries are unclear or need changes: STOP and report BLOCKED Don't assume or proceed Principles Strict ownership - Only touch what you own Explicit boundaries - No implicit permissions Block, don't break - Report issues, don't work around
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/file-boundaries