Techniques for driving AI coding tools (Claude Code, Cursor, Cline, Aider, Copilot) effectively on PCX projects. Covers context loading, prompt discipline, and steering the AI to read docs before writing API calls. Always active when working with an AI on a PCX scripting project.
Mandatory doc router for all PCX scripting sessions. Triggers on any game hacking, game cheat, ESP, aimbot, triggerbot, radar, Enma, AngelScript, or Perception.cx work. Provides the full supported doc index (32,000+ lines across 123 docs) and enforces reading the relevant documentation before writing any API call. Load alongside game-cheat-script-master and game-cheat-guidelines on every PCX game-cheat session.
Runs the PCX AI Toolkit CLI directly from Claude Code. Use this for `/pcx update` or any other pcx command.
Use for Source 2 live MCP investigations with schema/interface evidence.
Use for Unity IL2CPP live MCP investigations with GameAssembly and global-metadata evidence.
Use for Unreal live MCP investigations with UObject/GName/vtable evidence.
Use when recording, verifying, or rendering machine-readable reverse-engineering claim/evidence graphs.
Routing guide for the 59 Perception MCP tools — which to pick for memory reads, scans, disassembly, PE/module walks, and the Enma scripting bridge to avoid slower or redundant calls. Always active when calling Perception MCP tools. Answers "which tool for this task" so the AI picks the cheapest tool with the required precision.