Orientation / Code Dev Home

Move into the project as it is.

An existing repository carries decisions that may not be obvious from its folder names. Begin by observing how a real behavior works. Give the coding assistant time to discover the project's conventions before asking it to improve or extend them.

Take one path through the code

Choose a small feature with a visible entry point. Follow its route or command through the application layer, storage boundary, and relevant test. Read project instructions before proposing edits. Ask the assistant to explain which nearby implementation is the best precedent and which details remain uncertain.

Account for the work already there

Inspect the current working state and distinguish existing edits from the change you intend to make. Do not treat unfamiliar files as disposable or assume that all uncommitted work belongs to the current task. If a new request overlaps ongoing work, understand the overlap before deciding how to implement it.

A first visit to a repository

Adapt to your project

Read the repository instructions without editing.
Trace one existing feature from entry point to result.
List the patterns and commands this project uses.
Describe the current local changes without replacing them.
Recommend one bounded next task with source references.

When should I introduce a new abstraction?

When a concrete requirement or repeated complexity justifies it. First establish why existing patterns do not meet the task, and keep the proposed scope reviewable.