catlog22/Claude-Code-Workflow
1
0
Fork 0
mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-05 01:50:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: update Windows path format guidelines for MCP and Bash compatibility

Browse Source 
Clarified path format requirements:
- MCP tools require double backslash format (D:\path)
- Bash commands support forward slash (D:/path) or POSIX (/d/path)
- Added quick reference for common conversions

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
2025-10-16 10:39:40 +08:00
parent 25f6497933
commit 7ac5412c97
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
CLAUDE.md
View File

@@ -72,9 +72,11 @@ For all CLI tool usage, command syntax, and integration guidelines:
## Platform-Specific Guidelines
### Windows Path Conversion for Bash Commands
- **Windows paths** must convert to Git Bash format: `C:\path` → `/c/path`, `D:\path` → `/d/path`, `\` → `/`
- **Relative paths** (starting with `.` or `..`) require no conversion
### Windows Path Format Guidelines
- **MCP Tools**: Use double backslash `D:\\path\\file.txt` (MCP doesn't support POSIX `/d/path`)
- **Bash Commands**: Use forward slash `D:/path/file.txt` or POSIX `/d/path/file.txt`
- **Relative Paths**: No conversion needed `./src`, `../config`
- **Quick Ref**: `C:\Users` → MCP: `C:\\Users` | Bash: `/c/Users` or `C:/Users`
#### **Content Uniqueness Rules**