Archive / Get a map of a codebase before you change it

Get a map of a codebase before you change it

Follow one user action to the code and data it touches, then decide what to inspect next.

For: Solo founders, Small business owners

Topics: Learning, Agent management

Start with one action you can point to, such as Save preferences. A diagram of the entire app can wait.

1. Trace one action

Prompt

Read only. In [repo or supplied files], trace [specific action] from the UI through validation, requests and storage as far as evidence goes. Give path, symbol and data at each hop. Separate inference from confirmed references. Do not edit, run the app or inspect secrets.

2. Make a true map

Prompt

Turn the trace into a table of reads, writes, failure paths and unknowns. Separate what the UI shows from what the code attempts to persist. Name one more file or existing test that could resolve the most important unknown.

3. Plan one check

Prompt

For [proposed change], identify the smallest plausible edit and behavior that should stay unchanged. Suggest a success test and a failure test. Do not implement or claim runtime results from source alone.

Try it on one example

A green success toast does not prove preferences survive a restart. If you haven't found the storage adapter or run the app, say where the trace stops.

Inspired by Graphify: https://github.com/Graphify-Labs/graphify. These prompts work on plain source; no installation required.

Use it for: Follow one user action to the code and data it touches, then decide what to inspect next.

Back to the archive