Back to Details

session-management

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Session Management Skill

会话管理Skill

Load with: base.md
For maintaining context across long development sessions and enabling seamless resume after breaks.
加载方式：base.md
用于在长时间开发会话中维护上下文，并支持中断后无缝恢复工作。

Core Principle

核心原则

Checkpoint at natural breakpoints, resume instantly.
Long development sessions risk context loss. Proactively document state, decisions, and progress so any session can resume exactly where it left off - whether returning after a break or hitting context limits.
在自然断点处创建检查点，可立即恢复工作。
长时间开发会话存在上下文丢失的风险。主动记录状态、决策和进度，以便任何会话都能从中断的地方精确恢复——无论是休息后返回还是达到上下文限制时。

Tiered Summarization Rules

分层总结规则

Tier 1: Quick Update (current-state.md only)

第一层：快速更新（仅current-state.md）

Trigger: After completing any small task or todo item Action: Update "Active Task", "Progress", and "Next Steps" sections Time: ~30 seconds
触发条件：完成任何小型任务或待办事项后 操作：更新“当前任务”、“进度”和“下一步计划”部分 耗时：约30秒

Tier 2: Full Checkpoint (current-state.md + decisions.md)

第二层：完整检查点（current-state.md + decisions.md）

Trigger:
  • After completing a feature or significant change
  • After any architectural/library decision
  • After ~20 tool calls during active work
  • When switching to a different area of the codebase
Action:
  1. Update full current-state.md
  2. Log any decisions to decisions.md
  3. Update files being modified table
触发条件：
  • 完成某个功能或重大变更后
  • 做出任何架构/库选择决策后
  • 活跃工作期间完成约20次工具调用后
  • 切换到代码库的不同区域时
操作：
  1. 完整更新current-state.md
  2. 将所有决策记录到decisions.md
  3. 更新正在修改的文件表格

Tier 3: Session Archive (archive/ + full checkpoint)

第三层：会话归档（archive/ + 完整检查点）

Trigger:
  • End of work session
  • Completing a major feature/milestone
  • Before a significant context shift
  • When context feels heavy (~50+ tool calls)
Action:
  1. Create archive entry: 
    archive/YYYY-MM-DD[-topic].md
  2. Full checkpoint
  3. Clear verbose notes from current-state.md
  4. Update code-landmarks.md if new patterns introduced
触发条件：
  • 工作会话结束时
  • 完成某个主要功能/里程碑时
  • 重大上下文切换前
  • 上下文负担过重时（约50+次工具调用）
操作：
  1. 创建归档条目：
    archive/YYYY-MM-DD[-topic].md
  2. 执行完整检查点操作
  3. 清除current-state.md中的冗余笔记
  4. 如果引入了新模式，更新code-landmarks.md

Decision Heuristic

决策启发式规则

┌─────────────────────────────────────────────────────┐
│ After completing work, ask:                         │
├─────────────────────────────────────────────────────┤
│ Was a decision made?        → Log to decisions.md   │
│ Task took >10 tool calls?   → Full Checkpoint       │
│ Major feature complete?     → Archive               │
│ Ending session?             → Archive + Handoff     │
│ Otherwise                   → Quick Update          │
└─────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────┐
│ 完成工作后，请自问：                                 │
├─────────────────────────────────────────────────────┤
│ 是否做出了决策？        → 记录到decisions.md       │
│ 任务耗时超过10次工具调用？ → 执行完整检查点         │
│ 主要功能已完成？         → 进行归档                 │
│ 是否要结束会话？         → 归档并完成工作交接       │
│ 其他情况                 → 执行快速更新            │
└─────────────────────────────────────────────────────┘

Session State Structure

会话状态结构

Create 
_project_specs/session/
directory:
_project_specs/
└── session/
    ├── current-state.md      # Live session state (update frequently)
    ├── decisions.md          # Key decisions log (append-only)
    ├── code-landmarks.md     # Important code locations
    └── archive/              # Past session summaries
        └── 2025-01-15.md
创建
_project_specs/session/
目录：
_project_specs/
└── session/
    ├── current-state.md      # 实时会话状态（频繁更新）
    ├── decisions.md          # 关键决策日志（仅追加）
    ├── code-landmarks.md     # 重要代码位置
    └── archive/              # 过往会话总结
        └── 2025-01-15.md

Current State File

当前状态文件

_project_specs/session/current-state.md
 - Update every 15-20 minutes or after significant progress.
markdown
undefined
_project_specs/session/current-state.md
 - 每15-20分钟或取得重大进展时更新一次。
markdown
undefined

Current Session State

当前会话状态

Last updated: 2025-01-15 14:32
最后更新时间：2025-01-15 14:32

Active Task

当前任务

[One sentence: what are we working on right now]
Example: Implementing user authentication flow with JWT tokens
[一句话描述：当前正在处理的工作]
示例：使用JWT令牌实现用户认证流程

Current Status

当前状态

  • Phase: [exploring | planning | implementing | testing | debugging | refactoring]
  • Progress: [X of Y steps complete, or percentage]
  • Blocking Issues: [None, or describe blockers]
  • 阶段：[探索中 | 规划中 | 实现中 | 测试中 | 调试中 | 重构中]
  • 进度：[已完成Y步中的X步，或百分比]
  • 阻塞问题：[无，或描述阻塞问题]

Context Summary

上下文总结

[2-3 sentences summarizing the current state of work]
Example: Created auth middleware and login endpoint. JWT signing works. Currently implementing token refresh logic. Need to add refresh token rotation for security.
[2-3句话总结当前工作状态]
示例：已创建认证中间件和登录端点。JWT签名功能正常。 当前正在实现令牌刷新逻辑。需要添加刷新令牌轮换以提升安全性。

Files Being Modified

正在修改的文件

FileStatusNotes
src/auth/middleware.tsDoneJWT verification
src/auth/refresh.tsIn ProgressToken rotation
src/auth/types.tsDoneToken interfaces
文件状态备注
src/auth/middleware.ts已完成JWT验证
src/auth/refresh.ts进行中令牌轮换
src/auth/types.ts已完成令牌接口

Next Steps

下一步计划

  1. Complete refresh token rotation in refresh.ts
  2. Add token blacklist for logout
  3. Write integration tests for auth flow
  1. 完成refresh.ts中的刷新令牌轮换逻辑
  2. 为登出功能添加令牌黑名单
  3. 为认证流程编写集成测试

Key Context to Preserve

需要保留的关键上下文

  • Using RS256 algorithm (not HS256) per security requirements
  • Refresh tokens stored in HttpOnly cookies
  • Access tokens: 15 min, Refresh tokens: 7 days
  • 根据安全要求使用RS256算法（而非HS256）
  • 刷新令牌存储在HttpOnly Cookie中
  • 访问令牌：15分钟，刷新令牌：7天

Resume Instructions

恢复说明

To continue this work:
  1. Read src/auth/refresh.ts - currently at line 45
  2. The rotateRefreshToken() function needs error handling
  3. Check decisions.md for why we chose RS256 over HS256

---
要继续此项工作：
  1. 阅读src/auth/refresh.ts - 当前进度到第45行
  2. rotateRefreshToken()函数需要添加错误处理
  3. 查看decisions.md了解我们选择RS256而非HS256的原因

---

Decision Log

决策日志

_project_specs/session/decisions.md
 - Append-only log of architectural and implementation decisions.
markdown
undefined
_project_specs/session/decisions.md
 - 仅追加的架构和实现决策日志。
markdown
undefined

Decision Log

决策日志

Track key decisions for future reference. Never delete entries.
记录关键决策以供未来参考。请勿删除任何条目。

[2025-01-15] JWT Algorithm Choice

[2025-01-15] JWT算法选择

Decision: Use RS256 instead of HS256 for JWT signing
Context: Implementing authentication system
Options Considered:
  1. HS256 (symmetric) - Simpler, single secret
  2. RS256 (asymmetric) - Public/private key pair
Choice: RS256
Reasoning:
  • Allows token verification without exposing signing key
  • Better for microservices (services only need public key)
  • Industry standard for production systems
Trade-offs:
  • Slightly more complex key management
  • Larger token size
References:
  • src/auth/keys/ - Key storage
  • docs/security.md - Security architecture
决策：使用RS256而非HS256进行JWT签名
背景：实现认证系统
考虑的选项：
  1. HS256（对称加密） - 更简单，单密钥
  2. RS256（非对称加密） - 公钥/私钥对
选择：RS256
理由：
  • 无需暴露签名密钥即可验证令牌
  • 更适合微服务架构（服务仅需公钥）
  • 生产系统的行业标准
权衡：
  • 密钥管理略复杂
  • 令牌尺寸更大
参考资料：
  • src/auth/keys/ - 密钥存储位置
  • docs/security.md - 安全架构文档

[2025-01-14] Database Schema Approach

[2025-01-14] 数据库架构方案

Decision: Use Drizzle ORM with PostgreSQL
Context: Setting up data layer
Options Considered:
  1. Prisma - Popular, good DX
  2. Drizzle - Type-safe, SQL-like
  3. Raw SQL - Maximum control
Choice: Drizzle
Reasoning:
  • Better TypeScript inference than Prisma
  • More transparent SQL generation
  • Lighter weight, faster cold starts
References:
  • src/db/schema.ts - Schema definitions
  • src/db/migrations/ - Migration files

---
决策：使用Drizzle ORM搭配PostgreSQL
背景：搭建数据层
考虑的选项：
  1. Prisma - 流行，开发体验好
  2. Drizzle - 类型安全类SQL语法
  3. 原生SQL - 控制度最高
选择：Drizzle
理由：
  • TypeScript推断能力优于Prisma
  • SQL生成更透明
  • 更轻量，冷启动速度更快
参考资料：
  • src/db/schema.ts - 架构定义
  • src/db/migrations/ - 迁移文件

---

Code Landmarks

代码地标

_project_specs/session/code-landmarks.md
 - Important code locations for quick reference.
markdown
undefined
_project_specs/session/code-landmarks.md
 - 用于快速参考的重要代码位置。
markdown
undefined

Code Landmarks

代码地标

Quick reference to important parts of the codebase.
快速参考代码库的重要部分。

Entry Points

入口点

LocationPurpose
src/index.tsMain application entry
src/api/routes.tsAPI route definitions
src/workers/index.tsBackground job entry
位置用途
src/index.ts应用主入口
src/api/routes.tsAPI路由定义
src/workers/index.ts后台任务入口

Core Business Logic

核心业务逻辑

LocationPurpose
src/core/auth/Authentication system
src/core/billing/Payment processing
src/core/workflows/Main workflow engine
位置用途
src/core/auth/认证系统
src/core/billing/支付处理
src/core/workflows/主工作流引擎

Configuration

配置文件

LocationPurpose
src/config/index.tsEnvironment config
src/config/features.tsFeature flags
drizzle.config.tsDatabase config
位置用途
src/config/index.ts环境配置
src/config/features.ts功能开关
drizzle.config.ts数据库配置

Key Patterns

关键模式

PatternExample LocationNotes
Service Layersrc/services/user.tsBusiness logic encapsulation
Repositorysrc/repos/user.tsData access abstraction
Middlewaresrc/middleware/auth.tsRequest processing
模式示例位置备注
服务层src/services/user.ts业务逻辑封装
仓储层src/repos/user.ts数据访问抽象
中间件src/middleware/auth.ts请求处理

Testing

测试

LocationPurpose
tests/unit/Unit tests
tests/integration/API tests
tests/e2e/End-to-end tests
tests/fixtures/Test data
位置用途
tests/unit/单元测试
tests/integration/API测试
tests/e2e/端到端测试
tests/fixtures/测试数据

Gotchas & Non-Obvious Behavior

注意事项与非直观行为

LocationIssueNotes
src/utils/date.tsTimezone handlingAlways use UTC internally
src/api/middleware.ts:45Auth bypassSkip auth for health checks
src/db/pool.tsConnection limitMax 10 connections in dev

---
位置问题备注
src/utils/date.ts时区处理内部始终使用UTC
src/api/middleware.ts:45认证绕过健康检查跳过认证
src/db/pool.ts连接限制开发环境最大10个连接

---

CLAUDE.md Session Rules

CLAUDE.md会话规则

Add this section to CLAUDE.md:
markdown
undefined
将此部分添加到CLAUDE.md中：
markdown
undefined

Session Management

会话管理

IMPORTANT: Follow session-management.md skill. Update session state at natural breakpoints.
重要提示：遵循session-management.md skill的规则。在自然断点处更新会话状态。

After Every Task Completion

完成每项任务后

Ask yourself:
  1. Was a decision made? → Log to 
    decisions.md
  2. Did this take >10 tool calls? → Full checkpoint to 
    current-state.md
  3. Is a major feature complete? → Create archive entry
  4. Otherwise → Quick update to 
    current-state.md
自问：
  1. 是否做出了决策？ → 记录到
    decisions.md
  2. 任务耗时是否超过10次工具调用？ → 执行完整检查点操作到
    current-state.md
  3. 主要功能是否已完成？ → 创建归档条目
  4. 其他情况 → 快速更新
    current-state.md

Checkpoint Triggers

检查点触发条件

Quick Update (current-state.md):
  • After any todo completion
  • After small changes
Full Checkpoint (current-state.md + decisions.md):
  • After significant changes
  • After ~20 tool calls
  • After any decision
  • When switching focus areas
Archive (archive/ + full checkpoint):
  • End of session
  • Major feature complete
  • Context feels heavy
快速更新（current-state.md）：
  • 完成任何待办事项后
  • 完成小型变更后
完整检查点（current-state.md + decisions.md）：
  • 完成重大变更后
  • 约20次工具调用后
  • 做出任何决策后
  • 切换关注领域时
归档（archive/ + 完整检查点）：
  • 会话结束时
  • 主要功能完成时
  • 上下文负担过重时

Session Start Protocol

会话启动流程

When beginning work:
  1. Read 
    _project_specs/session/current-state.md
  2. Check 
    _project_specs/todos/active.md
  3. Review recent 
    decisions.md
    entries if needed
  4. Continue from "Next Steps"
开始工作时：
  1. 阅读
    _project_specs/session/current-state.md
  2. 查看
    _project_specs/todos/active.md
  3. 如有需要，查看最近的
    decisions.md
    条目
  4. 从“下一步计划”继续工作

Session End Protocol

会话结束流程

Before ending or when context limit approaches:
  1. Create archive: 
    _project_specs/session/archive/YYYY-MM-DD.md
  2. Update current-state.md with handoff format
  3. Ensure next steps are specific and actionable

---
结束会话或接近上下文限制时：
  1. 创建归档：
    _project_specs/session/archive/YYYY-MM-DD.md
  2. 用交接格式更新current-state.md
  3. 确保下一步计划具体且可执行

---

Compression Strategies

压缩策略

When to Compress (Tier 3 Archive)

何时压缩（第三层归档）

TriggerAction
~50+ tool callsSummarize progress, archive verbose notes
Major feature completeArchive feature details, update landmarks
Context shiftSummarize previous context, archive, start fresh
End of sessionFull session handoff with archive
触发条件操作
约50+次工具调用总结进度，归档冗余笔记
主要功能完成归档功能细节，更新地标
上下文切换总结之前的上下文，归档，重新开始
会话结束完整会话交接并归档

What to Keep vs Archive

保留与归档内容区分

Keep in active context:
  • Current task and immediate next steps
  • Active file list with status
  • Blocking issues
  • Key decisions affecting current work
Archive/summarize:
  • Exploration paths that didn't work out
  • Detailed debugging traces (keep conclusion only)
  • Verbose error messages (keep root cause only)
  • Research notes (keep recommendations only)
保留在活跃上下文中的内容：
  • 当前任务和即时下一步计划
  • 活跃文件列表及状态
  • 阻塞问题
  • 影响当前工作的关键决策
归档/总结的内容：
  • 未成功的探索路径
  • 详细调试轨迹（仅保留结论）
  • 冗长的错误信息（仅保留根本原因）
  • 研究笔记（仅保留建议）

Compression Template

压缩模板

When compressing, use this format:
markdown
undefined
压缩时使用以下格式：
markdown
undefined

Compressed Context - [Topic]

压缩上下文 - [主题]

Summary: [1-2 sentences]
Key Findings:
  • [Bullet points of important discoveries]
Decisions Made:
  • [Reference to decisions.md entries]
Relevant Code:
  • [File:line references]
Archived Details: [Link to archive file if created]

---
总结：[1-2句话]
关键发现：
  • [重要发现的要点]
已做出的决策：
  • [引用decisions.md中的条目]
相关代码：
  • [文件:行号引用]
归档详情：[如果创建了归档文件，添加链接]

---

Session Archive

会话归档

After significant work or at session end, create archive:
_project_specs/session/archive/YYYY-MM-DD[-topic].md
markdown
undefined
完成重要工作或会话结束后，创建归档：
_project_specs/session/archive/YYYY-MM-DD[-topic].md
markdown
undefined

Session Archive: [Date] - [Topic]

会话归档：[日期] - [主题]

Summary

总结

[Paragraph summarizing what was accomplished]
[段落总结已完成的工作]

Tasks Completed

已完成任务

  • [TODO-XXX] Description - Done
  • [TODO-YYY] Description - Done
  • [TODO-XXX] 描述 - 已完成
  • [TODO-YYY] 描述 - 已完成

Key Decisions

关键决策

  • [Reference decisions.md entries made this session]
  • [引用本次会话中decisions.md的条目]

Code Changes

代码变更

FileChange TypeDescription
src/auth/login.tsCreatedLogin endpoint
src/auth/types.tsModifiedAdded RefreshToken type
文件变更类型描述
src/auth/login.ts创建登录端点
src/auth/types.ts修改添加RefreshToken类型

Tests Added

新增测试

  • tests/auth/login.test.ts - Login flow tests
  • tests/auth/refresh.test.ts - Token refresh tests
  • tests/auth/login.test.ts - 登录流测试
  • tests/auth/refresh.test.ts - 令牌刷新测试

Open Items Carried Forward

未完成事项移交

  • [Anything not finished, now in active.md]
  • [未完成的工作，现在移至active.md]

Session Stats

会话统计

  • Duration: ~3 hours
  • Tool calls: ~120
  • Files modified: 8
  • Tests added: 12

---
  • 时长：约3小时
  • 工具调用次数：约120次
  • 修改文件数：8个
  • 新增测试数：12个

---

Integration with Todo System

与待办事项系统集成

Link Todos to Sessions

将会话与待办事项关联

In active todos, reference session context:
markdown
undefined
在活跃待办事项中引用会话上下文：
markdown
undefined

[TODO-042] Implement token refresh

[TODO-042] 实现令牌刷新

Status: in-progress Session Context: See current-state.md
状态：进行中 会话上下文：查看current-state.md

Progress Notes

进度笔记

  • 2025-01-15: Started implementation, base structure done
  • 2025-01-15: Added rotation logic, need error handling
undefined
  • 2025-01-15：开始实现，基础结构已完成
  • 2025-01-15：添加了轮换逻辑，需要错误处理
undefined

Auto-Update on Todo Completion

完成待办事项时自动更新

When completing a todo:
  1. Mark todo complete in active.md
  2. Update current-state.md progress
  3. Log any decisions made
  4. Update code-landmarks.md if new patterns introduced
完成待办事项时：
  1. 在active.md中标记待办事项为已完成
  2. 更新current-state.md中的进度
  3. 记录任何已做出的决策
  4. 如果引入了新模式，更新code-landmarks.md

Quick Commands

快速命令

Add to project scripts or aliases:
bash
undefined
添加到项目脚本或别名中：
bash
undefined

Show current session state

查看当前会话状态

alias session-status="cat _project_specs/session/current-state.md"
alias session-status="cat _project_specs/session/current-state.md"

Quick edit session state

快速编辑会话状态

alias session-edit="$EDITOR _project_specs/session/current-state.md"
alias session-edit="$EDITOR _project_specs/session/current-state.md"

View recent decisions

查看近期决策

alias decisions="tail -100 _project_specs/session/decisions.md"
alias decisions="tail -100 _project_specs/session/decisions.md"

Create session archive

创建会话归档

session-archive() { cp _project_specs/session/current-state.md
"_project_specs/session/archive/$(date +%Y-%m-%d).md" echo "Archived to _project_specs/session/archive/$(date +%Y-%m-%d).md" }

---
session-archive() { cp _project_specs/session/current-state.md
"_project_specs/session/archive/$(date +%Y-%m-%d).md" echo "已归档至 _project_specs/session/archive/$(date +%Y-%m-%d).md" }

---

Enforcement Mechanisms

执行机制

1. CLAUDE.md as Entry Point

1. 以CLAUDE.md为入口点

CLAUDE.md must reference session-management.md in the Skills section. Claude reads CLAUDE.md first, which directs it to follow session rules.
CLAUDE.md必须在Skills部分引用session-management.md。Claude会首先读取CLAUDE.md，其中会指示它遵循会话规则。

2. Session File Headers with Reminders

2. 会话文件头部的提醒

Include enforcement reminders in session file headers:
current-state.md header:
markdown
<!--
CHECKPOINT RULES (from session-management.md):
- Quick update: After any todo completion
- Full checkpoint: After ~20 tool calls or decisions
- Archive: End of session or major feature complete
-->
在会话文件头部包含执行提醒：
current-state.md头部：
markdown
<!--
检查点规则（来自session-management.md）：
- 快速更新：完成任何待办事项后
- 完整检查点：约20次工具调用或做出决策后
- 归档：会话结束或主要功能完成时
-->

3. Self-Check Questions

3. 自我检查问题

After completing any task, Claude should ask:
□ Did I make a decision? → Log it
□ Did this take >10 tool calls? → Full checkpoint
□ Is a feature complete? → Archive
□ Am I ending/switching context? → Archive + handoff
完成任何任务后，Claude应自问：
□ 是否做出了决策？ → 记录下来
□ 任务耗时是否超过10次工具调用？ → 执行完整检查点
□ 功能是否已完成？ → 进行归档
□ 是否要结束/切换上下文？ → 归档并完成交接

4. Session Start Verification

4. 会话启动验证

When starting a session, Claude must:
  1. Check if 
    current-state.md
    exists and read it
  2. Announce what it found: "Resuming from: [last state]"
  3. Confirm next steps before proceeding
启动会话时，Claude必须：
  1. 检查
    current-state.md
    是否存在并读取它
  2. 告知所发现的内容："从以下状态恢复：[上次状态]"
  3. 继续前确认下一步计划

5. Periodic Self-Audit

5. 定期自我审核

Every ~20 tool calls, Claude should check:
  • Is current-state.md up to date?
  • Are there unlogged decisions?
  • Is context getting heavy?
每约20次工具调用，Claude应检查：
  • current-state.md是否为最新版本？
  • 是否有未记录的决策？
  • 上下文是否变得过重？

6. User Prompts

6. 用户提示

Users can enforce by asking:
  • "Update session state" → Triggers checkpoint
  • "What's the current state?" → Claude reads and reports
  • "End session" → Triggers archive + handoff
  • "Resume from last session" → Claude reads state files first
用户可通过以下请求强制执行：
  • "更新会话状态" → 触发检查点
  • "当前状态是什么？" → Claude读取并报告
  • "结束会话" → 触发归档与交接
  • "从上次会话恢复" → Claude先读取状态文件

Anti-Patterns

反模式

  • No state tracking - Flying blind, can't resume
  • Overly verbose state - Keep it scannable, not a novel
  • Stale state files - Update regularly or they become useless
  • Missing decisions - Future you won't remember why
  • No code landmarks - Wastes time re-discovering the codebase
  • Never archiving - Session files become cluttered
  • Ignoring compression signals - Context overload degrades performance
  • Skipping checkpoint after decisions - Key context lost
  • No handoff at session end - Next session starts blind
  • 无状态跟踪 - 盲目工作，无法恢复
  • 状态过于冗长 - 保持内容易扫描，不要写成小说
  • 状态文件过时 - 定期更新，否则毫无用处
  • 缺失决策记录 - 未来的你会忘记原因
  • 无代码地标 - 浪费时间重新探索代码库
  • 从不归档 - 会话文件变得杂乱无章
  • 忽略压缩信号 - 上下文过载会降低性能
  • 做出决策后跳过检查点 - 关键上下文丢失
  • 会话结束时未完成交接 - 下次会话盲目启动

Quick Reference

快速参考

Checkpoint Decision Tree

检查点决策树

Task completed?
    │
    ├── Decision made? ──────────────────→ Log to decisions.md
    │
    ├── >10 tool calls OR significant? ──→ Full Checkpoint
    │
    ├── Major feature done? ─────────────→ Archive
    │
    └── Otherwise ───────────────────────→ Quick Update
任务已完成？
    │
    ├── 是否做出决策？ ──────────────────→ 记录到decisions.md
    │
    ├── 超过10次工具调用或重大任务？ ──→ 执行完整检查点
    │
    ├── 主要功能已完成？ ─────────────→ 进行归档
    │
    └── 其他情况 ───────────────────────→ 执行快速更新

Files at a Glance

文件概览

FileUpdate FrequencyPurpose
current-state.mdEvery taskLive state, next steps
decisions.mdWhen decidingArchitectural choices
code-landmarks.mdWhen patterns changeCode navigation
archive/*.mdEnd of session/featureHistorical record
文件更新频率用途
current-state.md每项任务后实时状态、下一步计划
decisions.md做出决策时架构选择
code-landmarks.md模式变更时代码导航
archive/*.md会话/功能结束时历史记录