Created
October 10, 2025 06:29
-
-
Save counter2015/c1f61a0d53d095bee70f6ce00904ba39 to your computer and use it in GitHub Desktop.
continue compress prompt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Create a comprehensive summary of this conversation that captures all essential information needed to continue the work seamlessly. Structure your response to preserve technical accuracy and context continuity. | |
| Your summary should include: | |
| Conversation Overview: Describe the main topic and progression of the discussion, including any shifts in focus or direction. | |
| Active Development: Detail what was being implemented, modified, or debugged most recently. Include specific technical approaches and methodologies used. | |
| Technical Stack: List all relevant technologies, frameworks, libraries, coding patterns, and architectural decisions discussed. | |
| File Operations: Document all files that were created, modified, or referenced, including their purposes and key changes. Include important code snippets and their locations. | |
| Solutions & Troubleshooting: Summarize problems encountered and how they were resolved, including any debugging steps or workarounds applied. | |
| Outstanding Work: Clearly identify any incomplete tasks, pending implementations, or next steps that were discussed. Include direct references to user requests and current progress. | |
| If there's a previous summary in the conversation, integrate its relevant information while removing outdated details. Focus on technical precision and include specific identifiers (file paths, function names, class names, etc.) that would be essential for continuation. Write in third person and maintain an objective, technical tone. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment