file-boundaries

Pattern for respecting file ownership boundaries during implementation. Prevents conflicts in parallel work.

242 stars

Best use case

file-boundaries is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Pattern for respecting file ownership boundaries during implementation. Prevents conflicts in parallel work.

Pattern for respecting file ownership boundaries during implementation. Prevents conflicts in parallel work.

Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.

Practical example

Example input

Use the "file-boundaries" skill to help with this workflow task. Context: Pattern for respecting file ownership boundaries during implementation. Prevents conflicts in parallel work.

Example output

A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.

When to use this skill

  • Use this skill when you want a reusable workflow rather than writing the same prompt again and again.

When not to use this skill

  • Do not use this when you only need a one-off answer and do not need a reusable workflow.
  • Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/file-boundaries/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/clouder0/file-boundaries/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/file-boundaries/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How file-boundaries Compares

Feature / Agentfile-boundariesStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Pattern for respecting file ownership boundaries during implementation. Prevents conflicts in parallel work.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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
```yaml
boundaries:
  owns: [src/auth/login.ts, src/auth/logout.ts]
```

You CAN:
- Read these files
- Modify these files
- Create new files in these paths
- Delete these files

### Files You READ
```yaml
boundaries:
  reads: [src/types/user.ts, src/utils/crypto.ts]
```

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:
```yaml
status: blocked
blocked_reason: boundary_violation
blocked_details:
  description: "Need to modify src/types/user.ts to add new type"
  needs: "Permission to modify or contract update"
  suggested_resolution: "Add UserSession type to user.ts"
```

## 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

Related Skills

file-organization

242
from aiskillstore/marketplace

Organize project files and folders for maintainability and scalability. Use when structuring new projects, refactoring folder structure, or establishing conventions. Handles project structure, naming conventions, and file organization best practices.

file-uploads

242
from aiskillstore/marketplace

Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: file upload, S3, R2, presigned URL, multipart.

file-path-traversal

242
from aiskillstore/marketplace

This skill should be used when the user asks to "test for directory traversal", "exploit path traversal vulnerabilities", "read arbitrary files through web applications", "find LFI vu...

file-path-traversal-testing

242
from aiskillstore/marketplace

This skill should be used when the user asks to "test for directory traversal", "exploit path traversal vulnerabilities", "read arbitrary files through web applications", "find LFI vulnerabilities", or "access files outside web root". It provides comprehensive file path traversal attack and testing methodologies.

azure-storage-file-share-ts

242
from aiskillstore/marketplace

Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations. Use for creating shares, managing directories, uploading/downloading files, and handling file metadata. Supports Azure Files SMB protocol scenarios. Triggers: "file share", "@azure/storage-file-share", "ShareServiceClient", "ShareClient", "SMB", "Azure Files".

azure-storage-file-share-py

242
from aiskillstore/marketplace

Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud. Triggers: "azure-storage-file-share", "ShareServiceClient", "ShareClient", "file share", "SMB".

azure-storage-file-datalake-py

242
from aiskillstore/marketplace

Azure Data Lake Storage Gen2 SDK for Python. Use for hierarchical file systems, big data analytics, and file/directory operations. Triggers: "data lake", "DataLakeServiceClient", "FileSystemClient", "ADLS Gen2", "hierarchical namespace".

create-skill-file

242
from aiskillstore/marketplace

Guides Claude in creating well-structured SKILL.md files following best practices. Provides clear guidelines for naming, structure, and content organization to make skills easy to discover and execute.

writing-config-files

242
from aiskillstore/marketplace

Use this skill when you need to write configuration files in `src/config` for the Next.js app

when-profiling-performance-use-performance-profiler

242
from aiskillstore/marketplace

Comprehensive performance profiling, bottleneck detection, and optimization system

file-header-guardian

242
from aiskillstore/marketplace

文件头三行契约注释。触发:create file、新建文件、编写代码。

devflow-file-standards

242
from aiskillstore/marketplace

File naming conventions, directory structure, and YAML frontmatter standards for CC-DevFlow. Consolidates shared conventions from all agents.