You know how in GTA you type “HESOYAM” and you get full health, armor, and $250k? No menus, no explanations, just a code that triggers everything at once. I accidentally discovered the same thing works with AI coding agents. There are specific words that trigger comprehensive, structured outputs — no long paragraphs needed. The cheat codes Here are the ones I use daily: “kitchen sink” — Give me EVERY case. Every edge case, every state, every variation. Nothing missing. Instead of writing: “Please make sure to cover all possible states including loading, error, empty, success, and also think about edge cases like network timeout, invalid data, concurrent requests…” You just say: “kitchen sink” . Done. The agent covers everything. “wireframe” — Show me what the user sees. ASCII UI layout. Instead of: “Can you draw the interface showing where the search bar goes, what the sidebar looks like, how the buttons are arranged…” You say: “wireframe” . You get: ┌─────────────────────────────────┐ │ ⌕ search… │ ├──────────┬──────────────────────┤ │ ▸ item 1 │ Detail view │ │ item 2 │ │ │ item 3 │ │ ├──────────┴──────────────────────┤ │ ⌘C copy ⌘V paste ↵ select │ └─────────────────────────────────┘ “blueprint” — The full spec. Wireframe + state diagram + interaction map, all in one. Like architectural blueprints but for UI. “prototype” — Just the type signatures. No implementation, no body. Just the API surface so you can see the shape of the code. Instead of: “Show me what functions and types we need, but don’t write the implementation yet…” You say: “prototype” . You get: swift protocol RecordingEngine { func start() async throws -> Session func stop() -> Recording func pause() var isRecording: Bool { get } } Clean. No noise. “decision matrix” — When you’re stuck between options. Criteria × options, scored. Instead of: “Compare Redis vs SQLite vs in-memory cache, considering speed, persistence, simplicity…” You say: “decision matrix” . You get: CRITERIA WEIGHT Redis SQLite Memory ──────── ────── ───── ────── ────── Speed 3 ✓✓✓ ✓✓ ✓✓✓ Persistence 2 ✓✓✓ ✓✓✓ ✗ Simplicity 3 ✓ ✓✓ ✓✓✓ “before/after” — Show me what changed. Not a paragraph explaining the change, literally show the two states side by side. “trace” — Step-by-step state changes. Like a debugger, but for understanding flow. [t0: init] [t1: request] [t2: response] state: idle → state: loading → state: success data: null data: null data: {…} Why this works These words aren’t random. They’re borrowed from established fields — architecture (blueprint, wireframe), testing (kitchen sink), software design (prototype). The AI already knows what they mean because they have precise definitions in their training data. It’s like speaking a shared language. Instead of describing what you want in 5 sentences, you use 1 word that both you and the AI understand perfectly. Try it yourself Next time you’re prompting, instead of writing a paragraph, try dropping one of these: “kitchen sink” when you want exhaustive coverage “wireframe” when you want to see the UI “blueprint” when you want the full spec “prototype” when you want just the API surface “decision matrix” when comparing options “before/after” when showing changes “trace” when understanding flow One word. Full output. GTA cheat codes for AI. What are yours? I’m genuinely curious — what single words or short phrases have you found that trigger specific behaviors? I can’t be the only one who stumbled onto this. Drop your cheat codes in the comments. I want to steal them all :D submitted by /u/_yemreak
Originally posted by u/_yemreak on r/ClaudeCode