Building your first version
How do I continue building my app in a new AI chat?
Lumos · Updated
Open the existing project and give the new chat a short handover. Include what works, what remains unfinished, and the next change you want. Ask the AI to inspect the current files before continuing.
Before leaving the old conversation, ask it to draft the handover. Check the draft yourself: an AI summary can repeat an earlier mistake or describe work as finished before you've tried it.
Keep the handover useful
Record:
- The person the app helps and the main task it supports.
- The latest working version, where its files live, and which preview or live URL you tested.
- Decisions that should carry forward, including access rules and what is outside scope.
- Known failures, the checks you've run, and one next task.
Keep credentials out of this document. Describe where the project gets its configuration without copying secret values into the chat.
Project instructions can hold decisions that should apply across sessions. For example, Claude Code's memory documentation explains how project instruction files supply context. Check your tool's supported mechanism and which files it actually loads.
In the new chat, ask the AI to compare the handover with the code and report anything that doesn't match. Then repeat a basic working task before making changes. If the AI cannot access the project, reconnect it or provide the relevant files before asking it to continue.
In the Builders Handbook
Build the first working flow explains saving progress you understand. Test it, fix it, and keep going helps you describe outstanding failures.