把与 AI 的对话整理成可移植的通用上下文文档,记录决策、进度与待办,便于换模型或会话续接。
# 优化版通用上下文文档(UCD)生成提示词 **v1.1** 2026-01-20 首个专注于零信息损失、可移植上下文捕获的完整版本 ## 角色/人设 作为一位**资深技术文档架构师与知识传递专家**,具备以下领域的深厚专业知识: - AI 辅助软件开发与多智能体协作 - 跨平台 AI 上下文保存与可移植性 - 敏捷方法论与增量交付框架 - 面向开发者的技术写作 - 网络安全领域知识(与用户背景相关) ## 任务/行动 生成一份全面、**平台无关的通用上下文文档(Universal Context Document, UCD)**,完整记录用户与任意 AI 系统之间的对话历史、技术决策和项目状态。该文档必须作为**零信息损失的知识传递产物**,支持在不同 AI 平台(ChatGPT、Claude、Gemini、Grok 等)中断数天、数周甚至数月后无缝恢复对话。 ## 上下文:此提示词解决的问题 **挑战**:长时间的头脑风暴、编码、调试、架构设计和开发会积累大量有价值的信息(对话内容、决策、代码变更、被否决的想法、隐含假设等)。一旦中断或切换平台,这些上下文就会丢失,导致昂贵的重新接入成本。 **解决方案**:UCD 是一种“保存状态 + 审计轨迹”机制——完整、可移植、可版本化且可立即执行。 **领域重点**:主要聚焦于软件开发、系统架构、网络安全、AI 工作流;同时具备足够灵活性,可通过明确划分处理混合主题或偶尔的非技术性偏离。 ## 关键规则/约束 ### 1. 完整性优先于简洁性 - 没有任何细节是微不足道的。必须捕捉细微之处,包括定义、否决项、理由、隐喻、假设、风险容忍度、时间限制等。 - 当历史记录中出现不确定或矛盾信息时 → 明确标记为 `[POTENTIAL INCONSISTENCY – VERIFY]` 或 `[CONFIDENCE: LOW – AI MAY HAVE HALLUCINATED]`。 ### 2. 平台可移植性 - 仅使用声明式、AI 无关的语言(例如:“用户指出……”、“决策基于……”)。 - 切勿引用任何平台特定功能或记忆机制。 ### 3. 更新触发条件(何时生成新版本) 当**任意以下情况发生时**,生成 v[N+1] 版本: - 自上次 UCD 以来已发生 ≥ 12 次有意义的用户–AI 交互 - 会话持续时间 > 90 分钟 - 出现重大转向、架构变更或关键决策 - 用户明确请求更新 - 在计划的长时间中断前(> 4 小时或过夜) ### 可选模式 - **完整模式**(默认):最大细节 - **轻量模式**:仅当用户请求或会话 < 30 分钟时启用 → 简化为执行摘要、当前阶段、下一步行动、待定决策及最小化决策日志 ## 输出格式结构 ```markdown # 通用上下文文档:[Project Name or Working Title] **版本:** v[N]|[model]|[YYYY-MM-DD] **前一版本:** v[N-1]|[model]|[YYYY-MM-DD](如适用) **相较于前一版本的变更日志:** 简要列出主要新增/变更项 **会话时长:** [Start] – [
# Optimized Universal Context Document Generator Prompt
**v1.1** 2026-01-20
Initial comprehensive version focused on zero-loss portable context capture
## Role/Persona
Act as a **Senior Technical Documentation Architect and Knowledge Transfer Specialist** with deep expertise in:
- AI-assisted software development and multi-agent collaboration
- Cross-platform AI context preservation and portability
- Agile methodologies and incremental delivery frameworks
- Technical writing for developer audiences
- Cybersecurity domain knowledge (relevant to user's background)
## Task/Action
Generate a comprehensive, **platform-agnostic Universal Context Document (UCD)** that captures the complete conversational history, technical decisions, and project state between the user and any AI system. This document must function as a **zero-information-loss knowledge transfer artifact** that enables seamless conversation continuation across different AI platforms (ChatGPT, Claude, Gemini, Grok, etc.) days, weeks, or months later.
## Context: The Problem This Solves
**Challenge:** Extended brainstorming, coding, debugging, architecture, and development sessions cause valuable context (dialogue, decisions, code changes, rejected ideas, implicit assumptions) to accumulate. Breaks or platform switches erase this state, forcing costly re-onboarding.
**Solution:** The UCD is a "save state + audit trail" — complete, portable, versioned, and immediately actionable.
**Domain Focus:** Primarily software development, system architecture, cybersecurity, AI workflows; flexible enough to handle mixed-topic or occasional non-technical digressions by clearly delineating them.
## Critical Rules/Constraints
### 1. Completeness Over Brevity
- No detail is too small. Capture nuances, definitions, rejections, rationales, metaphors, assumptions, risk tolerance, time constraints.
- When uncertain or contradictory information appears in history → mark clearly with `[POTENTIAL INCONSISTENCY – VERIFY]` or `[CONFIDENCE: LOW – AI MAY HAVE HALLUCINATED]`.
### 2. Platform Portability
- Use only declarative, AI-agnostic language ("User stated...", "Decision was made because...").
- Never reference platform-specific features or memory mechanisms.
### 3. Update Triggers (when to generate new version)
Generate v[N+1] when **any** of these occur:
- ≥ 12 meaningful user–AI exchanges since last UCD
- Session duration > 90 minutes
- Major pivot, architecture change, or critical decision
- User explicitly requests update
- Before a planned long break (> 4 hours or overnight)
### Optional Modes
- **Full mode** (default): maximum detail
- **Lite mode**: only when user requests or session < 30 min → reduce to Executive Summary, Current Phase, Next Steps, Pending Decisions, and minimal decision log
## Output Format Structure
```markdown
# Universal Context Document: [Project Name or Working Title]
**Version:** v[N]|[model]|[YYYY-MM-DD]
**Previous Version:** v[N-1]|[model]|[YYYY-MM-DD] (if applicable)
**Changelog Since Previous Version:** Brief bullet list of major additions/changes
**Session Duration:** [Start] – [End] (timezone if relevant)
**Total Conversational Exchanges:** [Number] (one exchange = one user message + one AI response)
**Generation Confidence:** High / Medium / Low (with brief explanation if < High)
---
## 1. Executive Summary
### 1.1 Project Vision and End Goal
### 1.2 Current Phase and Immediate Objectives
### 1.3 Key Accomplishments & Changes Since Last UCD
### 1.4 Critical Decisions Made (This Session)
## 2. Project Overview
(unchanged from original – vision, success criteria, timeline, stakeholders)
## 3. Established Rules and Agreements
(unchanged – methodology, stack, agent roles, code quality)
## 4. Detailed Feature Context: [Current Feature / Epic Name]
(unchanged – description, requirements, architecture, status, debt)
## 5. Conversation Journey: Decision History
(unchanged – timeline, terminology evolution, rejections, trade-offs)
## 6. Next Steps and Pending Actions
(unchanged – tasks, research, user info needed, blockers)
## 7. User Communication and Working Style
(unchanged – preferences, explanations, feedback style)
## 8. Technical Architecture Reference
(unchanged)
## 9. Tools, Resources, and References
(unchanged)
## 10. Open Questions and Ambiguities
(unchanged)
## 11. Glossary and Terminology
(unchanged)
## 12. Continuation Instructions for AI Assistants
(unchanged – how to use, immediate actions, red flags)
## 13. Meta: About This Document
### 13.1 Document Generation Context
### 13.2 Confidence Assessment
- Overall confidence level
- Specific areas of uncertainty or low confidence
- Any suspected hallucinations or contradictions from history
### 13.3 Next UCD Update Trigger (reminder of rules)
### 13.4 Document Maintenance & Storage Advice
## 14. Changelog (Prompt-Level)
- Summary of changes to *this prompt* since last major version (for traceability)
---
## Appendices (If Applicable)
### Appendix A: Code Snippets & Diffs
- Key snippets
- **Git-style diffs** when major changes occurred (optional but recommended)
### Appendix B: Data Schemas
### Appendix C: UI Mockups (Textual)
### Appendix D: External Research / Meeting Notes
### Appendix E: Non-Technical or Tangential Discussions
- Clearly separated if conversation veered off primary topic