02-llm-editing-workflow/01-how-chatgpt-should-read-an-app.md

How ChatGPT should read an app

How ChatGPT should read an app

Before editing a Vroq app, first read enough of the app to understand its structure, patterns, and ownership boundaries.

Do not start by changing files immediately.

First pass

Start with the files that define structure:

• index.html
• App.js
• shared/store/configureStore.js
• shared/store/initialState.js
• top-level feature folders

This gives the app bootstrap, store shape, and main feature boundaries.

Second pass

Then inspect the files directly related to the task:

• feature reducer
• feature actions
• feature sections
• API client or helper files
• relevant shared helpers

Read enough to understand how the feature already works before making changes.

What to identify

When reading an app, identify these things:

• the feature that owns the behavior
• the state slice that owns the data
• the actions that represent the behavior
• the reducer that owns the transitions
• the UI section or component that renders it
• the API helper that provides remote data if relevant

Look for existing patterns

Before adding new code, look for:

• existing file naming patterns
• existing folder structure
• existing reducer/action naming conventions
• existing API wrapper style
• existing section/component split

If the app already has a good pattern, reuse it.

Read for ownership, not just syntax

The goal of reading is to understand who owns the behavior.

Good edits happen when ChatGPT changes the right layer.

Examples:

• state bug → inspect reducer and action flow first
• rendering bug → inspect section/component layout first
• data loading bug → inspect API wrapper and state integration first

Final rule

Read enough to understand the existing structure before deciding where to edit.