tikzlisted

# TikZ Collision Audit > **Attribution.** Adapted from Scott Cunningham's `/tikz` skill in [MixtapeTools](https://github.com/scunning1975/MixtapeTools) (licensed "Use freely. Attribution appreciated."). Stripped MixtapeTools-specific tool references (`/beautiful_deck`, `~/mixtapetools/...`) for this template's generic paper-writing context. **Purpose**: Find and fix residual visual collisions in TikZ figures in a given `.tex` file. Labels on arrows, text inside boxes, arrows crossing arrows — this skill catches them using measurement, not intuition. **The fundamental rule**: Claude cannot reliably eyeball where TikZ elements land. All placement must be verified mathematically before declaring it safe. --- ## Critical context: this is a repair tool, not the primary defense `/tikz` runs **after** TikZ has been generated. It audits existing code and fixes what it finds. But it cannot reliably fix diagrams that were never built with measurement in mind. **The upstream defense is [`PREVENTION.md`](PREVENTION.md)** (in this skill directory), which describes writing safe TikZ from the start: 1. Every `\node` declares explicit `minimum width` and `minimum height` (Rule P1) 2. Every edge label carries a directional keyword (`above`, `below`, etc.) (Rule P4) 3. A coordinate map comment block precedes every `tikzpicture` (Rule P2) 4. Standard diagram types use the canonical safe templates in `.claude/rules/tikz-snippets/` (Rule P5) 5. `scale` is never used alone on complex diagr