메뉴
Use when reading or writing JSON in Python on Windows to avoid CP-1252 mojibake — the convention here is to copy this skill's json_io.py into the project and always open JSON as UTF-8.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Anthropic API rate limit handling - retry logic, backoff, throttling for batch workloads against Claude models
Use when building an automated test → issue → fix loop with Claude Code and GitHub issues — overnight auto-fixing, regression loops, self-healing CI.
Use when creating, editing, publishing, or deleting posts on Cyril's Workshop blog or the steponnopets.net devblog.
Use when writing or contributing a boofuzz network-protocol fuzzer in this repo — layout, formatting rules, and reading results.
Use when a task needs real-time control of a connected browser via the Browser Bridge Broker — submit JS jobs over HTTP that browsers eval and return.
Use when training a character LoRA (Chroma/Flux or Pony/SDXL) on a RunPod GPU and wiring it into the ComfyUI + pony_web render stack.
| name | Python JSON |
| description | Use when reading or writing JSON in Python on Windows to avoid CP-1252 mojibake — the convention here is to copy this skill's json_io.py into the project and always open JSON as UTF-8. |
Python's open() uses the system encoding, which on Windows is CP-1252, not UTF-8 — so reading/writing JSON that contains £, €, or accented letters produces mojibake and violates RFC 8259 (JSON must be UTF-8). Two rules fix it:
encoding='utf-8' when opening a JSON file.ensure_ascii=False when writing, so Unicode stays readable instead of becoming \uXXXX.Every Python project here that touches JSON gets a copy of json_io.py (in this skill directory) dropped into its utils/, then imports from it instead of calling json.load/json.dump directly:
from utils.json_io import load_json, save_json
data = load_json('config.json')
save_json('output.json', {'price': '£99.99'})
json_io.py is already correct — copy it, don't rewrite it.
£, €, é appearing in data → a UTF-8 file was read as CP-1252; add encoding='utf-8' (or use load_json).£ in written output → json.dump defaulted to ensure_ascii=True; pass ensure_ascii=False (or use save_json).