mobile-compaction
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseMobile Compaction Skill
移动端上下文压缩Skill
Strategic context compaction for large Android projects to optimize token usage while preserving critical information.
针对大型Android项目的战略性上下文压缩,在保留关键信息的同时优化Token使用。
When to Compact
何时进行压缩
Compact context when:
- Token usage exceeds 100,000
- Working on large refactors spanning many files
- Switching between unrelated features
- Session becomes unfocused
- Context contains resolved discussions
在以下场景进行上下文压缩:
- Token使用量超过100,000
- 处理跨多个文件的大型重构工作
- 在不相关功能之间切换时
- 会话失去焦点时
- 上下文包含已解决的讨论内容时
Compaction Strategies
压缩策略
1. Module-Level Compaction
1. 模块级压缩
Focus on a single Android module:
bash
/compact --module=feature:authWhat happens:
- Retain: All files in feature:auth module
- Summarize: Other modules to high-level description
- Drop: Resolved discussions about other modules
Use when: Deep work on a specific feature
聚焦单个Android模块:
bash
/compact --module=feature:auth执行效果:
- 保留:feature:auth模块中的所有文件
- 总结:将其他模块提炼为高层级描述
- 丢弃:关于其他模块的已解决讨论
适用场景:针对特定功能的深度开发工作
2. Layer-Based Compaction
2. 基于分层的压缩
Focus on architecture layer:
bash
/compact --layer=ui
/compact --layer=data
/compact --layer=domainWhat happens:
| Layer | Retain | Summarize |
|---|---|---|
| UI | Composables, ViewModels, navigation | Repository details, data models |
| Data | Repositories, data sources, models | Compose code, UI state |
| Domain | Use cases, domain models | Implementation details |
Use when: Working on cross-cutting concerns in a layer
聚焦架构分层:
bash
/compact --layer=ui
/compact --layer=data
/compact --layer=domain执行效果:
| Layer | 保留内容 | 总结内容 |
|---|---|---|
| UI | Composables、ViewModels、导航逻辑 | 仓库细节、数据模型 |
| Data | 仓库、数据源、模型 | Compose代码、UI状态 |
| Domain | 用例、领域模型 | 实现细节 |
适用场景:处理某一分层的横向关注点
3. Build Variant Focus
3. 构建变体聚焦
Narrow to specific build variant:
bash
/compact --variant=debugWhat happens:
- Retain: Debug-specific configurations, test code
- Summarize: Release configurations, ProGuard rules
Use when: Debugging or test development
缩小到特定构建变体:
bash
/compact --variant=debug执行效果:
- 保留:Debug专属配置、测试代码
- 总结:Release配置、ProGuard规则
适用场景:调试或测试开发
4. Test Isolation
4. 测试隔离
Compact around failing tests:
bash
/compact --test=AuthViewModelTest
/compact --test-failingWhat happens:
- Retain: Test file, related source files
- Summarize: Unrelated test discussions
- Drop: Resolved test fix discussions
Use when: Fixing specific test failures
围绕失败的测试进行压缩:
bash
/compact --test=AuthViewModelTest
/compact --test-failing执行效果:
- 保留:测试文件、相关源文件
- 总结:不相关的测试讨论
- 丢弃:已解决的测试修复讨论
适用场景:修复特定测试失败问题
5. Pattern-Based Compaction
5. 基于模式的压缩
Compact based on architectural patterns:
bash
/compact --pattern=compose
/compact --pattern=mvi
/compact --pattern=koinWhat happens:
- Retain: Files matching the pattern
- Summarize: Non-matching files to pattern names only
Use when: Pattern-specific work (e.g., Compose optimization)
基于架构模式进行压缩:
bash
/compact --pattern=compose
/compact --pattern=mvi
/compact --pattern=koin执行效果:
- 保留:匹配该模式的文件
- 总结:将非匹配文件仅提炼为模式名称
适用场景:针对特定模式的工作(如Compose性能优化)
Compaction Levels
压缩级别
| Level | Retention | Token Savings | Use Case |
|---|---|---|---|
| Lite | Current task only | 70-80% | Deep focus work |
| Medium | Current + related | 50-60% | Feature development |
| Standard | Project summary | 30-40% | Default compaction |
| Minimal | Essential only | 80-90% | Context at limit |
| 级别 | 保留内容 | Token节省率 | 适用场景 |
|---|---|---|---|
| 轻量(Lite) | 仅当前任务 | 70-80% | 深度聚焦工作 |
| 中等(Medium) | 当前任务+相关内容 | 50-60% | 功能开发 |
| 标准(Standard) | 项目摘要 | 30-40% | 默认压缩级别 |
| 最小(Minimal) | 仅核心内容 | 80-90% | 上下文达到上限时 |
What Gets Preserved
保留规则
Always Preserve (Critical)
始终保留(核心内容)
- Active task context (what we're doing now)
- Recent code changes (last 5-10 files)
- Current errors/failures
- Mobile memory context
- High-confidence instincts (>0.7)
- Unresolved questions
- 活跃任务上下文(当前正在进行的工作)
- 近期代码变更(最近5-10个文件)
- 当前错误/失败信息
- 移动端内存上下文
- 高置信度直觉(>0.7)
- 未解决的问题
Usually Preserve (Important)
通常保留(重要内容)
- Architecture decisions
- Recent discussions (last 50 messages)
- Related file contents
- Test states
- 架构决策
- 近期讨论(最近50条消息)
- 相关文件内容
- 测试状态
Summarize (Compressible)
总结压缩(可压缩内容)
- Completed features
- Resolved bugs
- Working code explanations
- Background discussions
- 已完成功能
- 已修复Bug
- 工作代码说明
- 背景讨论
Drop (Disposable)
丢弃(可舍弃内容)
- Successful build outputs
- Trivial operations
- Duplicated information
- Off-topic discussions
- 成功的构建输出
- 琐碎操作
- 重复信息
- 无关讨论
Compaction Commands
压缩命令
Basic Compaction
基础压缩
bash
/compact # Auto-select strategy
/compact --level=medium # Specify level
/compact --focus=compose # Focus on specific areabash
/compact # 自动选择策略
/compact --level=medium # 指定压缩级别
/compact --focus=compose # 聚焦特定领域Smart Compaction
智能压缩
bash
/compact --smart # AI chooses strategy
/compact --adaptive # Adjusts based on usagebash
/compact --smart # AI选择策略
/compact --adaptive # 根据使用情况自动调整Manual Compaction
手动压缩
bash
/compact --keep=file1.kt,file2.kt # Keep specific files
/compact --drop=discussion-1 # Drop specific discussion
/compact --summarize=feature-x # Summarize specific topicbash
/compact --keep=file1.kt,file2.kt # 保留特定文件
/compact --drop=discussion-1 # 丢弃特定讨论
/compact --summarize=feature-x # 总结特定主题Compaction Workflow
压缩工作流
Before Compaction
压缩前
bash
1. /memory-save all # Save current state to memory
2. /mobile-checkpoint save pre-compact # Optional checkpoint
3. /compact --strategy=module --focus=feature:authbash
1. /memory-save all # 将当前状态保存到内存
2. /mobile-checkpoint save pre-compact # 可选:创建检查点
3. /compact --strategy=module --focus=feature:authAfter Compaction
压缩后
bash
1. /memory-summary # Verify memory preserved
2. /instinct-status # Verify instincts preserved
3. Continue work...bash
1. /memory-summary # 验证内存内容是否保留
2. /instinct-status # 验证直觉信息是否保留
3. 继续工作...Integration
集成
With Checkpoints
与检查点集成
bash
undefinedbash
undefinedPre-compact hook automatically saves checkpoint
压缩前钩子会自动保存检查点
Restore to recover if compaction removes needed context
如果压缩移除了所需上下文,可通过恢复检查点找回
undefinedundefinedWith Memory
与内存集成
bash
undefinedbash
undefinedMemory survives compaction
内存内容在压缩后仍保留
Query memory to recover details:
通过查询内存恢复细节:
/memory-query "What was the auth flow architecture?"
undefined/memory-query "What was the auth flow architecture?"
undefinedWith Instincts
与直觉集成
bash
undefinedbash
undefinedInstincts survive compaction
直觉信息在压缩后仍保留
High-confidence instincts always retained
高置信度直觉始终会被保留
Low-confidence may be summarized
低置信度直觉可能会被总结
undefinedundefinedAnti-Patterns
反模式
Don't Compact When:
避免压缩的场景:
- In the middle of debugging
- Unresolved errors exist
- Active discussion ongoing
- Task almost complete
- 正在调试过程中
- 存在未解决的错误
- 正在进行活跃讨论
- 任务即将完成时
Do Compact When:
建议压缩的场景:
- Starting new task
- Switching context
- Token limit approaching
- Task completed, keeping summary
- 开始新任务时
- 切换上下文时
- 接近Token上限时
- 任务完成后,保留摘要时
Recovery
恢复方法
If compaction removed needed context:
bash
1. /memory-query <topic> # Query memory
2. /mobile-checkpoint list # Check for checkpoints
3. /mobile-checkpoint restore <name> # Restore if needed
4. Git history for file diffs如果压缩移除了所需上下文:
bash
1. /memory-query <topic> # 查询内存
2. /mobile-checkpoint list # 查看检查点列表
3. /mobile-checkpoint restore <name> # 如有需要,恢复检查点
4. 通过Git历史查看文件差异Examples
示例
Example 1: Feature Development
示例1:功能开发
Context: Working on auth feature, context contains old home feature discussions
Action: /compact --module=feature:auth
Result: Retains auth files, summarizes home feature上下文:正在开发认证功能,上下文包含旧版首页功能的讨论
操作:/compact --module=feature:auth
结果:保留认证模块文件,总结首页功能相关内容Example 2: Test Fixing
示例2:测试修复
Context: Many files, focus on fixing LoginTest
Action: /compact --test=LoginTest
Result: Retains LoginTest, related auth files, summarizes rest上下文:包含大量文件,聚焦修复LoginTest
操作:/compact --test=LoginTest
结果:保留LoginTest及相关认证文件,总结其他内容Example 3: Compose Optimization
示例3:Compose优化
Context: Large project, optimizing Compose performance
Action: /compact --pattern=compose --level=medium
Result: Retains Compose files, summaries of data/network layersRemember: Compaction is reversible via checkpoints and memory. When in doubt, checkpoint first.
上下文:大型项目,优化Compose性能
操作:/compact --pattern=compose --level=medium
结果:保留Compose文件,总结数据/网络层内容注意:可通过检查点和内存撤销压缩操作。如有疑问,先创建检查点。