REA: Claude Code shows how a feature in an app works, then builds your own version

Set up REA (Reverse Engineer Anything) in my Claude Code: an open-source tool (MIT license) that inspects apps and websites without their source code, github.com/morluto/rea. Use only the official sources: github.com/morluto/rea, rea.tools and the npm package named exactly rea-agents. The README warns that copies with similar names exist, so never use a fork, a mirror or a look-alike package. Work step by step:
1. Check that Node.js and npm are installed. REA needs Node.js 22.19 or newer, 24.11 or newer, or 26 and newer (23 and 25 don't work). If Node.js is missing or too old, tell me and, after my OK, install Node.js 24 LTS the way rea.tools/get-started recommends for my system. On Windows, if PowerShell refuses to run npx, use its .cmd version, as that page says. On Linux, check that the procps package is installed: REA needs its ps tool to inspect apps.
2. Check on npm that the rea-agents package points to the repository github.com/morluto/rea, and note its latest version. Use exactly that version in every REA command below, so what gets installed is what I approved.
3. Run REA's setup for Claude Code only (client claude_code) as a dry run with JSON output, so nothing changes yet. Show me the plan in plain words: which files it changes, which backups it makes and which skill it installs. Don't install Hopper or any other analysis engine now. Change nothing until I say OK.
4. After my OK, apply the same setup for Claude Code only, without Hopper. Your terminal isn't interactive, so use the setup option that confirms the plan I approved. Check that it finished. If setup says the configuration changed while it was working, run it again. Then tell me how to restart Claude Code and continue this same conversation.
5. After the restart, check that the REA tools are connected and list them for me in plain words.
6. First try, on the official practice app: download https://rea.tools/examples/notes-example.zip into a new folder called rea-practice in my home folder and unpack it. Don't run it. Use REA to find out what happens when I click Export notes: where notes.csv is written, which fields it has, and which files and lines prove it. Explain it simply.
7. Explain how to use REA on my own targets and what each one needs: a feature on a website (you open a separate browser window just for this, I click, REA records what happens), an app installed on my computer, and programs that need an analysis engine (the free Ghidra with Java, or Hopper or IDA under their own licenses). Give me three example requests, such as: find out how search works in an app, show me the evidence, and build a similar feature for my project.
Rules for every investigation: only software I own or am allowed to examine. Never help me get around logins, paywalls, license checks, DRM or anti-cheat, and don't copy someone else's code, images or texts into my project: build my own version from how it works. If a request crosses that line, stop and tell me. Before you inspect private files, remind me that you, Claude, will see the results.
If something fails, explain why and fix it. I'm not a developer: do everything you can do yourself.

Copy the prompt