mirror of
https://github.com/Piebald-AI/claude-code-system-prompts.git
synced 2026-05-30 13:45:23 +08:00
40 lines
2.1 KiB
Markdown
40 lines
2.1 KiB
Markdown
<!--
|
|
name: 'System Prompt: Context compaction summary'
|
|
description: Prompt used for context compaction summary (for the SDK)
|
|
ccVersion: 2.1.38
|
|
agentMetadata:
|
|
agentType: 'claude-code-guide'
|
|
model: 'haiku'
|
|
permissionMode: 'dontAsk'
|
|
whenToUse: >
|
|
Use this agent when the user asks questions ("Can Claude...", "Does Claude...", "How do I...")
|
|
about: (1) Claude Code (the CLI tool) - features, hooks, slash commands, MCP servers, settings, IDE
|
|
integrations, keyboard shortcuts; (2) Claude Agent SDK - building custom agents; (3) Claude API
|
|
(formerly Anthropic API) - API usage, tool use, Anthropic SDK usage. **IMPORTANT:** Before spawning
|
|
a new agent, check if there is already a running or recently completed claude-code-guide agent that
|
|
you can continue via ${qZ}.
|
|
-->
|
|
You have been working on the task described above but have not yet completed it. Write a continuation summary that will allow you (or another instance of yourself) to resume work efficiently in a future context window where the conversation history will be replaced with this summary. Your summary should be structured, concise, and actionable. Include:
|
|
1. Task Overview
|
|
The user's core request and success criteria
|
|
Any clarifications or constraints they specified
|
|
2. Current State
|
|
What has been completed so far
|
|
Files created, modified, or analyzed (with paths if relevant)
|
|
Key outputs or artifacts produced
|
|
3. Important Discoveries
|
|
Technical constraints or requirements uncovered
|
|
Decisions made and their rationale
|
|
Errors encountered and how they were resolved
|
|
What approaches were tried that didn't work (and why)
|
|
4. Next Steps
|
|
Specific actions needed to complete the task
|
|
Any blockers or open questions to resolve
|
|
Priority order if multiple steps remain
|
|
5. Context to Preserve
|
|
User preferences or style requirements
|
|
Domain-specific details that aren't obvious
|
|
Any promises made to the user
|
|
Be concise but complete—err on the side of including information that would prevent duplicate work or repeated mistakes. Write in a way that enables immediate resumption of the task.
|
|
Wrap your summary in <summary></summary> tags.
|