Conversation Continuity Checkpoint

Use this when the chat context is full or at the end of the day. It helps you create a dense summary so you can start again in a new chat.

How to use

Use this when you reach a natural stopping point.

Prompt

Create a high-density checkpoint summary to allow seamless continuation in a new chat.

Analysis

Review entire conversation and extract:

  • What is the user trying to achieve? What's next?
  • What decisions were made? What's final?
  • What problems remain unsolved?
  • Which files are being modified?

Generate Checkpoint

Output a single code block exactly:

# 🚀 CONVERSATION CONTINUATION CHECKPOINT

## 🎯 Current Objective

[One sentence of active task, e.g., "Fixing the hydration error in Gallery component"]

## 📝 Context & Decisions

- **Architecture:** [Key decisions, e.g., "Using SvelteKit Loaders not onMount"]
- **State:** [Current status, e.g., "API endpoint ready, frontend fetch failing"]
- **Constraints:** [Restrictions, e.g., "Use Shadcn UI, no custom CSS"]

## 📂 Active Files

- `src/routes/+page.svelte` (Main UI)
- `src/lib/components/Gallery.svelte` (Component with bug)

## 🚧 Outstanding Tasks

1. [ ] Debug the fetch call in Gallery.svelte
2. [ ] Verify data types match Zod schema
3. [ ] Run pnpm test:e2e to verify fix

## 🤖 Next Prompt (Copy & Paste)

"I am continuing a previous session. We are working on [Objective]. The current state is [State]. Please load the Active Files and proceed with Task #1: [Task Name]."

Instruction

Tell user: "Copy the code block above and paste it into a new chat to resume exactly where we left off."

Quality Checklist

  • Objective is 1-2 sentences max
  • File paths are correct and relative
  • Tasks have clear descriptions
  • No unnecessary repetition
  • Next prompt is self-contained