BestPromptFinder

Checkpoint a Long Vibe-Coding Chat Before It Starts Breaking Things

Quality, usefulness and confidence are AI evaluations out of 100 — not user ratings. Community results come from visitors' "worked / didn't work" votes below. How scoring works →

The prompt

We've been building [app or game] in this chat for a long time and new changes are starting to break old features or cut code. Before we change anything else, make a checkpoint. 1. Write the full current version of every file, complete, with no '...rest unchanged' gaps. If it's too long for one reply, say how many parts you'll send and send them in order. 2. List every feature that works right now as a short checklist I can test by hand. 3. List known bugs and anything half-finished. 4. Write a handoff summary under 250 words: what the app does, file structure, key decisions and rules (for example 'never rename these functions', 'keep everything in one HTML file'). From now on, for each change: tell me which files you'll touch, change only those, and show the full changed file. If a change would remove or rewrite a working feature, ask first. I'll paste the handoff summary and files into a fresh chat if this one keeps slipping.

Why this prompt

• Hand-picked, editorially reviewed prompt
• Written for Gemini 4 Argon, ChatGPT, Claude

Source

Created by BestPromptFinder — editorial prompt, not user-generated. See our content & source policy.

Related Coding prompts