Latest / AI Fire Daily / #678 Neil: Reverse Engineering Notion With REA and Claude Code Easily
Transcript
- 0:00Think about the app you use the most right now.
- 0:04Software usually just feels like this impenetrable
- 0:07black box. Oh, totally. Just a locked vault you
- 0:10can't see inside. Right. But what if you could
- 0:14peer inside your favorite app, understand its
- 0:16exact mechanics, and clone its best features?
- 0:19Yeah, and do all of that without knowing how
- 0:21to write a single line of code. Exactly. Welcome
- 0:23to the deep dive. We've got a fascinating mission
- 0:26for you today. We really do. We are exploring
- 0:28a detailed guide on using something called REA,
- 0:31which stands for Reverse Engineer Anything, and
- 0:34we are pairing it with Claude Code Desktop. Basically
- 0:37to safely analyze local applications and figure
- 0:40out how they tick. We have a very clear roadmap
- 0:42for how we're going to do this. First, we're
- 0:44covering how to set up the environment. Which
- 0:46is usually the hardest part, honestly. It really
- 0:48is. Then we will safely analyze the Notion desktop
- 0:51app. build a custom clone from scratch called
- 0:54TableKeep, and finally, polish it into a professional
- 0:58workspace. It's going to be a fun one. So to
- 1:00deconstruct software, we obviously first need
- 1:03to equip our AI with the right tools. Right.
- 1:05Which brings us to step one. We need to install
- 1:08REA inside Cloud Code Desktop. And there are
- 1:11a few prerequisites here, right? Yeah, you need
- 1:13Node .js installed, NPM, and you need to grab
- 1:17the REA GitHub repository. OK, standard stuff.
- 1:20But... I'll make a vulnerable admission here.
- 1:22I still wrestle with setting up coding environments
- 1:25myself. You know, it always feels like something
- 1:27breaks. Oh, dependency hell is a very real place.
- 1:31I've spent days stuck in it. Glad it's not just
- 1:33me. But the methodology here is actually brilliant
- 1:35because you don't do it manually. Exactly. You
- 1:39don't just blindly copy paste terminal commands.
- 1:42Instead, you prompt Claude code to read the official
- 1:45readme file. Right. So Claude checks your specific
- 1:48operating system, verifies your dependencies,
- 1:51and installs it for you. Wait, so why rely on
- 1:53Claude to read the README instead of just installing
- 1:56it manually? Well, official documentation changes
- 1:59all the time, right? So this ensures Claude matches
- 2:02the installation exactly to your specific operating
- 2:05system and totally avoids that blind copy -pasting
- 2:08trap. So the AI acts as a personalized IT assistant
- 2:12for the setup. Yeah, that's exactly what it's
- 2:14doing. And it makes sure you have a solid foundation.
- 2:17Now, a big part of this setup involves the REAMCP
- 2:21server. Right. The model context protocol. Let
- 2:24me quickly define that. It is a bridge letting
- 2:27AI use outside tools securely on your computer.
- 2:30Perfectly said. It's sandboxed, so it's safe.
- 2:34Claude also checks for analysis providers like
- 2:36Hopper or Ghidra. Yeah, those are essentially
- 2:39decompilers to help read the structure of the
- 2:41software. And once it's all configured, Claude
- 2:44runs a diagnostic command. I think it's npx -y
- 2:49rea -agents -at -latest -doctor. Yep, that verifies
- 2:53the whole setup. You might need to restart Claude
- 2:56Code Desktop afterward just to refresh everything.
- 2:58Okay, so the AI is equipped. The environment
- 3:01is ready. We can finally point it at a target.
- 3:04But we have to be careful here to not overwhelm
- 3:06the system. Right. We have to narrow our focus.
- 3:09We can't just say clone all of Notion. Oh no.
- 3:11That would be a complete disaster. The AI would
- 3:14lose context immediately. So the target for today
- 3:16is very specific. We are looking at a feature
- 3:19within the local Notion desktop app. Specifically,
- 3:22the Notion database feature. Right. We want the
- 3:25table, board, and list views plus properties
- 3:28like dates and check boxes. The core of what
- 3:30makes Notion, well, Notion. And the process here
- 3:33is fascinating. We are using REA to inspect the
- 3:38local installation folder. Yeah, we aren't setting
- 3:40up some complex API to talk to Notion servers.
- 3:43It's all local. It's kind of like sending an
- 3:46AI architect with a hard hat into a building
- 3:48to sketch the floor plan. Well, just imagine
- 3:50the AI opening up your local files and mapping
- 3:53out how a billion dollar app ticks. It's incredible.
- 3:56It really is a wild concept. But I do want to
- 3:59make a crucial ethical note here based on the
- 4:01source. Very important, yes. You should only
- 4:04reverse engineer apps you own or have permission
- 4:06to inspect. you have to strictly follow terms
- 4:09of service. Absolutely. This is for educational,
- 4:13local cloning, not corporate espionage. Right.
- 4:17So REA is inspecting the files. But what happens
- 4:20if REA hits a wall and can't see all the original
- 4:23code? Well, code is often obfuscated, right?
- 4:26So REA maps out the observable actions and database
- 4:31views, reporting what it can confirm. and leaves
- 4:34the unreadable gaps for Claude to creatively
- 4:36solve later. It grabs the visible blueprints
- 4:39and gets creative with the missing pieces. Exactly.
- 4:41Okay. That uses its own logic to fill in the
- 4:43blanks. We're going to take a quick break, but
- 4:45when we come back, we're taking those blueprints
- 4:47and building our own app from scratch. Explicit
- 4:50placeholder for sponsor read. All right, so we
- 4:53are armed with our Notion blueprints. Now we
- 4:55transition from analyzing someone else's app
- 4:58to building our own. The fun part. We are building
- 5:00a web app we're calling TableKeep. And we are
- 5:03doing this in a local working folder. Yep, keeping
- 5:06it all contained. But the prompt instructions
- 5:09we give Claude here are super critical. We feed
- 5:11it the confirmed REA findings, but we have to
- 5:14explicitly tell it to invent original code for
- 5:17the missing parts. Yes. And you must tell it
- 5:20strictly, do not copy Notion's source code, their
- 5:23design, their branding, or any private data.
- 5:26We want the mechanics, not a stolen copy. Exactly.
- 5:30It has to be a clean room design, essentially.
- 5:33So we list our core features. We need a table
- 5:36view, right? Yeah, and that needs standard add,
- 5:39edit, and delete functions, plus resizing columns.
- 5:42And we need a board view, where you can drag
- 5:43items between status groups. Like dragging a
- 5:46task from to do to done. And a basic list view.
- 5:49Plus it has to handle filters and sorting. Don't
- 5:52forget data persistence. The data has to stay
- 5:54saved when you refresh the page. Oh, right. Very
- 5:57important. Clod usually uses local storage in
- 6:00the browser for that. Yeah. It's the easiest
- 6:02way to keep it local and snappy. But here's the
- 6:04really tricky part. All these views have to sync
- 6:07changes simultaneously. Right. If you edit a
- 6:10title in the table view, it has to update in
- 6:11the board view instantly. So how does the AI
- 6:14ensure the views stay synced if it couldn't see
- 6:17notions underlying sync code? Well, Clod understands
- 6:19the goal from the re -analysis. So it writes
- 6:22its own original logic to route all three views
- 6:24to a single shared database. The AI clones the
- 6:27core function, not the actual underlying code.
- 6:30Exactly. You build the central source of truth,
- 6:34and the views just look at that source. That's
- 6:37incredibly smart. We also demand that Claude
- 6:39uses a simple tech stack for this. Yeah, keep
- 6:42it a basic React or vanilla .js. And it has to
- 6:45add sample data immediately so we can actually
- 6:47see it working. Crucial step. But the most important
- 6:50prompt instruction is about testing, right? Oh,
- 6:52for sure. You have to tell Claude to test the
- 6:55features and fix its own bugs before declaring
- 6:57it done. We want a working local URL for the
- 7:00browser, not a list of errors. Right. You make
- 7:03the AI do its own quality assurance. OK. So TableKeep
- 7:06works functionally. The data saves, the views
- 7:08sync. It's functional, yeah. But user experience
- 7:11matters. We need to transition this from a basic
- 7:14clunky database into a professional daily workspace.
- 7:17We need to iterate and polish it. But we need
- 7:19to iterate and polish it. But before we ask Claude
- 7:22to make massive changes, there is a crucial piece
- 7:24of advice here. Always, always make a backup
- 7:27of the original TableKeep project folder. Yes.
- 7:30Because if you ask for huge updates, an AI can
- 7:33sometimes just completely break the working logic.
- 7:35And there is nothing worse than losing a perfectly
- 7:37working app because you wanted a new font color.
- 7:39So true. Once the backup is safe, we start feeding
- 7:43Claude specific prompt upgrades. What are we
- 7:46asking for? Well, we want a clean left sidebar
- 7:48for moving between multiple databases. OK, nice.
- 7:51A modern design with soft colors. We obviously
- 7:54need light and dark modes. Dark mode is mandatory.
- 7:57And it has to be mobile responsive. Of course.
- 8:00We also want to upgrade the actual features.
- 8:02Smooth drag and drop animations, a global search
- 8:05bar. Oh, and record detail side panels. Like
- 8:08when you click a record, a panel slides out to
- 8:11edit it. Yes, that makes it feel so much more
- 8:14professional. We also ask for keyboard shortcuts,
- 8:18multi -condition filtering. and confirmation
- 8:20messages before deleting data. Safety reels.
- 8:23I love it. Now to test all this, the source gives
- 8:26a great specific example. We have Claude create
- 8:29a reading list database. Oh, that's a good test.
- 8:32Yeah, it has book titles, authors, ratings, and
- 8:35a reading status. So it's testing how the app
- 8:38handles different data types all at once. Texts,
- 8:41numbers, dropdowns. Exactly. But I have to ask,
- 8:46does asking for all these complex UI changes
- 8:48risk breaking the database logic we just built?
- 8:51Yes, absolutely. Which is exactly why the prompt
- 8:54demands that Claude check existing code, keep
- 8:57all working features and save data, and test
- 9:00the updated app locally to fix broken buttons
- 9:03before delivering the final URL. You must demand
- 9:06that AI tests its new paint job against the engine.
- 9:09Yeah. That's a great way to put it. Function
- 9:12has to survive the form upgrade. So stepping
- 9:17back and looking at this whole process, it's
- 9:19a massive paradigm shift. It really is. By combining
- 9:23REA and Cloud Code Desktop, you aren't just an
- 9:26end user trapped in someone else's software ecosystem
- 9:28anymore. No, you're not waiting on developers
- 9:30to fix the things that annoy you. Exactly. You
- 9:33have the tools to ethically deconstruct how your
- 9:36favorite features work, and then you can rebuild
- 9:38them to serve your exact needs. Even if you are
- 9:41a total beginner, the barrier to entry is just
- 9:44gone. It's incredibly empowering. So think about
- 9:47your daily workflow. What is that one specific
- 9:51feature from an app you use every day that you
- 9:53wish worked just a little bit differently? We
- 9:56all have at least one. Right. With these tools,
- 9:59you no longer have to wait for a developer to
- 10:01update it. You can build it yourself. What will
- 10:04you reverse engineer first? Yeah, get building.
- 10:07See you next time.