Reverse Engineering Prompts
Use evidence-first analysis to understand software you own or have permission to inspect.
4 published 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
Start a read-only application investigation
Scope the first investigation of an unfamiliar application to a small question and produce an evidence map before changing code or behavior.
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