A 58-LINE PROMPT TURNS OPUS 5.5 + REA INTO A CLEAN-ROOM LAB FOR ANY APP ON YOUR LAPTOP most builders still use Opus like a chat window. this prompt makes it drive REA down to the binary and come back with evidence the flow from @N01ennn's prompt: MAP > reads the whole app first, then picks one seed: a module, a string or a symbol PATH > follows the real route from your click to the result, down to one function EVIDENCE > every line gets a label. OBSERVATION cites the file, function and line, INFERENCE says what it follows from, UNKNOWN stays on the list and never shrinks SPEC > writes SPEC.md from behaviour only, with inputs, outputs, state, edge cases and errors BUILD > implements your version from the spec alone. when the spec runs out it goes back to investigate instead of filling gaps from memory VERIFY > runs the tests until they pass, then plants one wrong answer. if the tests still pass, they were blind REA picks the engine by target. Node for JS, Electron and .NET, Ghidra, Hopper or IDA for native binaries, JADX for Android APKs, a Chrome browser for websites the scope line sits in the prompt itself. lawful research, interop, preservation or software you own. outside t
▶ ♫