# AI use cases for Awesome REA (reacher-z/Awesome-REA) Repo: [reacher-z/Awesome-REA](https://github.com/reacher-z/Awesome-REA) | Use cases: 4 | Page: https://dedupedai.com/use-cases/reacher-z-awesome-rea/ A curated list of tools, case studies and research papers for reverse engineering websites, games, apps, binaries, firmware and communication protocols. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Extract a website's design system from its live pages: https://dedupedai.com/use-cases/reacher-z-awesome-rea/extract-website-design-system/ - Make minified JavaScript readable before auditing it: https://dedupedai.com/use-cases/reacher-z-awesome-rea/make-minified-javascript-readable/ - Turn captured app traffic into an API spec: https://dedupedai.com/use-cases/reacher-z-awesome-rea/turn-captured-traffic-into-api-spec/ - Study the legacy WhatsApp Web protocol from a documented case: https://dedupedai.com/use-cases/reacher-z-awesome-rea/study-legacy-whatsapp-web-protocol/ ## How to extract a website's design system from its live pages with Awesome REA Repo: [reacher-z/Awesome-REA](https://github.com/reacher-z/Awesome-REA) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Pull colors, type, spacing and component styles from a site's computed styles with Dembrandt. **Who it is for:** A front-end developer or designer who needs to match an existing site's visual system before building a similar page. **The problem:** Re-creating a site's look by hand means guessing colors, fonts and spacing from screenshots, which is slow and often wrong. **The outcome:** A report of the site's design tokens and component styles, with the evidence behind each color pick. ### Steps 1. Open the Dembrandt entry in the Tools section of the Awesome REA README and read its full entry for prerequisites. 2. Choose a website you own or have permission to analyze. 3. Install the Dembrandt Node.js CLI by following the project page at https://github.com/dembrandt/dembrandt. 4. Run Dembrandt against the site URL and let it render the page in Playwright-driven Chromium or Firefox. 5. Review the extracted color roles, typography, spacing and component styles, and check each color against the page. ### Prompt to paste into your agent ```text Use the dembrandt project from the Awesome-REA tools list to extract the design system of , which I own or have permission to analyze. Return the color roles, typography, spacing and button and input styles as a short report. Verify that each color value matches a computed style on the live page. ``` ### Caveat Awesome REA is a list of links, so the Dembrandt setup and commands live in the upstream project and are not verified here. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/reacher-z-awesome-rea/extract-website-design-system/ ## How to make minified JavaScript readable before auditing it with Awesome REA Repo: [reacher-z/Awesome-REA](https://github.com/reacher-z/Awesome-REA) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Unpack bundles and rename minified identifiers so shipped JavaScript can be reviewed. **Who it is for:** A security reviewer or developer who needs to read a site's shipped JavaScript bundle to check what it does. **The problem:** Minified and bundled JavaScript has short, meaningless names and merged modules, which makes manual review slow. **The outcome:** Readable module files and clearer identifiers that make the bundle's logic easier to follow. ### Steps 1. Open the JavaScript tools section in the Awesome REA README and pick a tool that matches your bundle, such as webcrack for webpack or Browserify bundles, or wakaru for recognized minifier and transpiler patterns. 2. Save the bundle you are allowed to review as a local file. 3. Run the chosen tool on the saved file by following its project page, and keep the output in a separate folder. 4. For leftover short names, try humanify, which suggests names with an LLM and applies them with scope-aware AST rewriting. 5. Compare the readable output with the original file to confirm the logic is unchanged before drawing conclusions. ### Prompt to paste into your agent ```text Using the webcrack or wakaru entries from the Awesome-REA README, make the minified bundle at readable and save the output to . Report the modules and any endpoints or API calls you find. Verify that the bundle's exported names still match the original file. ``` ### Caveat The README lists these tools as options with one-line descriptions, so their exact input formats must be checked on each project page. Risk, reverse engineering: Deobfuscating third-party JavaScript may conflict with the site's terms or the code's license, so confirm you have the right to analyze it first. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/reacher-z-awesome-rea/make-minified-javascript-readable/ ## How to turn captured app traffic into an API spec with Awesome REA Repo: [reacher-z/Awesome-REA](https://github.com/reacher-z/Awesome-REA) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Capture HTTP calls from an app, then generate an OpenAPI spec or MCP tools from them. **Who it is for:** An integration developer who needs the API of an app that has no public documentation. **The problem:** Undocumented app APIs have to be mapped by hand from network traffic, which is tedious and error-prone. **The outcome:** A draft OpenAPI 3.1 spec or MCP tool set built from the captured requests, to start an integration. ### Steps 1. Open the mitmproxy entry in the Awesome REA README and set up the proxy on the device or browser you will use. 2. Use the app or site you are allowed to test and record its HTTP traffic. 3. Remove session tokens, cookies and personal data from the captured file before sharing it. 4. Open the Spectral entry and feed the redacted traffic into its LLM-based analysis to generate OpenAPI 3.1, MCP tools or a GraphQL schema. 5. Test a few generated endpoints against the live service and correct any that do not match. ### Prompt to paste into your agent ```text Using mitmproxy and Spectral from the Awesome-REA README, analyze the redacted HTTP capture at from and produce an OpenAPI 3.1 draft in . Note any endpoints that need authentication. Verify two generated endpoints against the live service before reporting success. ``` ### Caveat Spectral and the Browser Reverse Engineering Toolkit are listed as separate projects, and their generated output has not been verified by this list. Risk, credentials: Captured traffic often contains session tokens and cookies, so redact them before any file leaves your machine or goes to an agent. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/reacher-z-awesome-rea/turn-captured-traffic-into-api-spec/ ## How to study the legacy WhatsApp Web protocol from a documented case with Awesome REA Repo: [reacher-z/Awesome-REA](https://github.com/reacher-z/Awesome-REA) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Learn how a browser messaging session was paired, keyed and encrypted from a written case. **Who it is for:** A security researcher or protocol student who wants a worked example of a web messaging protocol's handshake and encryption. **The problem:** Protocol internals are rarely documented, so learners need a worked reference that explains each stage. **The outcome:** A clear understanding of QR pairing, key setup, message framing and media encryption in the documented legacy protocol. ### Steps 1. Open the whatsapp-web-reveng case study in the Awesome REA README and read its full entry for the scope and limits. 2. Read the sections on QR pairing and Curve25519/HKDF key setup in the linked repository. 3. Trace how AES/HMAC-protected binary messages and the token-based node encoding are built and parsed. 4. Read the end-to-end media encryption section and note which parts are described as legacy. 5. Write a short summary of each stage and compare it with the current protocol behavior from official documentation. ### Prompt to paste into your agent ```text Using the whatsapp-web-reveng case in the Awesome-REA README, explain the pairing, key setup and message encryption stages of the legacy WhatsApp Web protocol to a reader. Output a numbered summary with one paragraph per stage. Verify each claim against the linked repository before stating it. ``` ### Caveat The case describes a legacy protocol that WhatsApp Web no longer uses, so its details are historical and not a guide to current behavior. Risk, reverse engineering: The case reimplements a messaging protocol, so use it to study the design and do not point it at accounts or services you do not own. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/reacher-z-awesome-rea/study-legacy-whatsapp-web-protocol/