If you’re using Claude Code to build do the following and I promise the experience gets 10x better:
/model = Opus 5.5
/advisor = Fable 5.2
Then copy and paste the following into your session -
- Opus 5.5 runs the main session and edits the code
- search maps the repo on Haiku 5.5, read-only
- grep finds every call site on Haiku 5.5
- test-runner runs the suite on Haiku 5.5 and reports only failures
- Fable 5.2 on call as advisor, reads the full transcript when consulted
- JEV routes micro-forks in milliseconds
Rebuild my Claude Code setup around this tree:
1. Run the main session on Opus 5.5 with Fable 5.2 as advisor.
2. Create three read-only Haiku 5.5 subagents: search (maps the repo), grep (finds call sites), test-runner (runs the suite, reports only failures).
3. Add one rule to CLAUDE.md: consult the advisor before a plan locks, after the same error twice, and before a task is marked done.
4. Route fast deterministic forks (tool choice, path selection, retries) through JEV.
Show me every change as a diff first. Nothing gets edited until I say go.
Credit goes to @skunzu for creating the original write up on this! I just made it much shorter. Appreciate the setup Skunzu, my sessions are 10x better now!
@sfcteodeio Isso sao os shaders compilando mesmo, coisa de emulador kkk se vc se interessar em jogar pelo cemu tem esse video https://t.co/tr2rGOrGiV que ensina a configurar. A ROM eu te passo por direct o torrent se quiser
REA (reverse engineer anything) - F*CKED by chinese student...
solo dev just dropped protection for your app & site & game from reverse-engineering and AI hackers, for free
REA not dangerous anymore.
here's how to use and setup BLA (Blind LLM Agents):
first understand how it works:
• REA opens your app in 1 command, BLA hides traps inside it before you ship
• fake keys and decoy code for AI to chase, plus files built to blow past REA's own limits
• AI burns tokens on dead ends, your users get the exact same app
here's how to set it up for FREE:
1 → open Claude Code in the folder of your app, site or game
2 → say: " install Node.js 24 if I don't have it, build my project, then run npx bla-agents setup and npx bla-agents harden"
3 → it finds your build itself: dist, build, Electron .asar, .wasm, Python, native binaries
4 → it plants fake keys and decoy code, then checks every protected file still runs the same
5 → the step everyone skips: ship the files from the new .bla-hardened folder, not your old build
6 → for sites it protects the JS your site sends to browsers, your server code never leaves your server anyway
7 → want proof? run: npx bla-agents benchmark - before vs after on 14 test apps
paste link on repo below as soon as possible: