@archiveexplorer X analytics

Archive@archiveexplorer·13.9K followers·29d ago

THIS IS A PURE F*CKING GOLDMINE the best REA trick almost nobody runs yet. The idea: REA takes the app apart, Jev keeps only what's proven, and a fresh Opus 5.5 rebuilds the feature from that alone. Nothing gets copied and no guess makes it into the code, because the builder never sees the original, only the spec Jev signed off on. You just connect REA like this: npx rea-agents setup here's the split: → REA reads the feature down to the binary and writes every rule into SPEC.md → Jev checks each rule against REA's evidence and sends back anything unproven → a fresh Opus 5.5 session gets only SPEC.md and rebuilds the feature → Haiku 5.5 runs the tests against 3 intentionally broken versions Opus only shows up at three moments: → rebuilding from the approved spec → the checks Jev marks as unclear → signing off before anything ships REA reads. Jev judges. Opus rebuilds. That's the clean-room rule in one line: the model that saw the original never writes the code, and the model

Archive@archiveexplorer·13.9K followers·28d ago

It is becoming f*cking dangerous: you can now reverse-engineer any repo with one command - a YC-backed tool with 127k stars maps the whole codebase, and your agent walks the map instead of reading files 1. Clone the project you want to understand 2. Install graphify: uv tool install graphifyy 3. Run graphify install (it detects Claude Code, Cursor, Codex or Gemini CLI) 4. Open the project and type /graphify . 5. Open graph.html: the architecture map nobody ever documented 6. Read GRAPH_REPORT.md: what everything flows through and the connections you didn't know were there 7. Ask: graphify path "A" "B" traces how two things connect, graphify explain shows everything one of them touches Code is mapped locally with no LLM, and every link says whether it was read or inferred Turn your agent into a reverse engineer that knows the whole project before it touches a single file Find the repo in the reply below