- Tool
- REA
- Provider or project
- JoasASantos community collection
- Source type
- Community-authored
Who should use it
Developers onboarding to an authorized artifact or internal product they did not build.
Practical uses
- Identify the module responsible for converting a local document.
- Prepare a first-pass architecture note for the next engineer.
How to use it
- State which artifact is in scope, what you observed and which actions are permitted.
- Choose a small behavior that has a clear input and output.
- Ask for a map of the evidence and one next question, with unobserved behavior called out.
Original example
Inspect the sample weather desktop app I own. Explain where its local units preference is loaded. Return the modules you inspected and the evidence for each claim.
Limitations
Runtime-only behavior may require separate instrumentation on a test build. A file inventory alone cannot establish execution order.
Sources and versions
The explanation and example were written for this directory. The cited files record the source version.
- Skills/reap-01-getting-started/SKILL.md
REA Investigation Prompts · JoasASantos ·
9756618f25·Source license MIT
Related prompts
Compare two builds to triage a crash
Use a known-good and failing build of your application to isolate what changed around a reproducible crash and hand the evidence to a maintainer.
Reverse Engineering Prompts · REA
Plan a WebAssembly port of your game
Identify the portable simulation code in an authorized game and plan a small browser proof of concept before migrating rendering, audio or platform integrations.
Reverse Engineering Prompts · REA
Trace one feature in an application you own
Follow a single visible action from the user interface to its output. Keep observations, source evidence and hypotheses distinct so the next maintainer can verify the trace.
Reverse Engineering Prompts · REA