Illustrated tutorial: take apart an app feature with REA, from observed behaviour down to implementation evidence图文教程：用 REA 拆解一个 App 的功能，从行为一路挖到实现证据

Make sure Node.js and npm are installed, then run npx rea-agents setup in your terminal.

Choose the agent you want to configure (Claude Code, Codex, Cursor, Gemini CLI, Grok Build and more). It shows the configuration changes it plans to make and backs up your existing configuration first.

Restart your agent afterwards. Native binary analysis needs an analysis engine: it can reuse an existing Hopper / Ghidra / IDA installation, and setup can install Hopper with your approval.

State the goal in plain language and explicitly demand evidence, for example: "Understand how global search works in this Electron app, list the evidence, and tell me which parts are inference."

REA picks the right analysis tools (JavaScript static analysis needs no native engine — just hand it the unpacked directory or the ASAR file) and returns modules, import relationships and Electron boundaries together with the evidence.

A key habit: make it separate "observed behaviour" from "inferred implementation" and cite where the evidence comes from. Do not accept conclusions without provenance.

To inspect the raw result yourself, use the terminal: npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json. The output is structured JSON, easy to archive or paste into a report.

For regular use, install the CLI: npm install --global rea-agents, then run rea --help to see the native analysis commands and provider selection.

REA iterates quickly, so remember to run rea update periodically (Bun global installs need Bun 1.2.17 or later) and re-run setup as instructed afterwards to refresh the registration.

Finally hand the requirement to the agent: "Based on that analysis, build a prototype of a similar feature in my project — propose a plan before writing code."

Because you already hold the evidence, this implementation is far more reliable than copying something by feel. Ask it to add tests once it is done.

This article is compiled from public sources and ships with the matching resource. Product features and pricing are subject to the official page. Resources are for learning and exchange only — please respect the original license.