Mike Swanson
dd0ef45645
- Split CODING_GUIDELINES.md into 19 indexed standards files under .claude/standards/ - 9 from CODING_GUIDELINES (conventions, powershell, security, api, git, gururmm) - 10 from session log tribal knowledge (syncro, ssh, gitea, python, client, gururmm) - Add .claude/standards/index.yml for cheap relevance-based lookup - Add /inject-standards command: load targeted standards per task instead of full guidelines - Add /shape-spec command: pre-implementation spec for GuruRMM features (plan.md, shape.md, references.md, standards.md) with mandatory out-of-scope gate - Add docs/tech-stack.md and docs/mission.md for ClaudeTools API - Add projects/msp-tools/guru-rmm/docs/tech-stack.md and mission.md for GuruRMM - Update CLAUDE.md commands table with /inject-standards and /shape-spec Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
85 lines
2.8 KiB
Markdown
85 lines
2.8 KiB
Markdown
---
|
|
name: windows-runtime
|
|
description: Use `py` on Windows (not python3/python); use jq for JSON extraction; use Python scripts over heredocs with apostrophes
|
|
applies-to: all
|
|
---
|
|
|
|
# Python on Windows
|
|
|
|
## Interpreter command
|
|
|
|
On Windows (DESKTOP-0O8A1RL, GURU-BEAST-ROG), use `py` to invoke Python:
|
|
|
|
```bash
|
|
# Correct
|
|
py script.py
|
|
py -c "import hashlib; print(hashlib.sha384(b'test').hexdigest())"
|
|
py -m bot.main
|
|
|
|
# Wrong — not in PATH on this machine
|
|
python3 script.py
|
|
python script.py
|
|
```
|
|
|
|
`python3` and `python` are not in Git Bash's PATH on the Windows machines in this MSP. The Windows Launcher (`py.exe`) is the correct entry point and selects the installed Python version automatically. Store aliases are also disabled in this environment.
|
|
|
|
## JSON extraction — use jq, not Python
|
|
|
|
For JSON extraction in shell scripts, use `jq` rather than a Python one-liner. `jq` is installed at:
|
|
```
|
|
C:/Users/guru/AppData/Local/Microsoft/WinGet/Links/jq
|
|
```
|
|
|
|
```bash
|
|
# Correct — jq for JSON extraction
|
|
COMMAND=$(echo "$INPUT" | jq -r '.tool_input.command')
|
|
|
|
# Acceptable for complex extraction when jq is insufficient
|
|
py -c "import json,sys; d=json.load(sys.stdin); print(d['tool_input']['command'])"
|
|
```
|
|
|
|
## Heredocs with apostrophes — use Write + py script
|
|
|
|
If a heredoc payload contains apostrophes (single quotes) in the content, Git Bash `<<'EOF'` terminates early at the apostrophe. Workaround: write the content to a file using the Write tool, then read it with Python:
|
|
|
|
```bash
|
|
# Write the file with Write tool first, then:
|
|
py script.py
|
|
```
|
|
|
|
Or use Python to build and send the payload without a heredoc at all:
|
|
|
|
```bash
|
|
py -c "
|
|
import urllib.request, json
|
|
data = json.dumps({'body': \"It's a note about John's machine\"}).encode()
|
|
req = urllib.request.Request(url, data=data, headers={'Content-Type': 'application/json'})
|
|
urllib.request.urlopen(req)
|
|
"
|
|
```
|
|
|
|
## Sending HTTP requests via Python (avoids backslash hook)
|
|
|
|
The pre-bash-backslash hook blocks commands with Windows-style backslash paths. Python's `urllib.request` is a clean alternative to curl for sending POST requests that include backslash-containing paths in the payload:
|
|
|
|
```bash
|
|
py -c "
|
|
import urllib.request, json
|
|
url = 'http://172.16.3.30:8001/api/coord/messages'
|
|
data = json.dumps({'to_session': 'target', 'body': 'message'}).encode()
|
|
req = urllib.request.Request(url, data=data, headers={'Content-Type': 'application/json'})
|
|
resp = urllib.request.urlopen(req)
|
|
print(resp.status, resp.read())
|
|
"
|
|
```
|
|
|
|
## Unicode in log files
|
|
|
|
When reading log files that may contain non-UTF8 bytes (Windows logs, PowerShell output):
|
|
|
|
```python
|
|
sys.stdout.buffer.write(output.encode('utf-8', errors='replace'))
|
|
```
|
|
|
|
Do not use `open(file, 'r')` without specifying encoding on Windows — the default encoding varies by system locale and may not be UTF-8.
|