AI Code Assistant 使用报告AI Code Assistant Usage Dashboard

1. 执行摘要1. Executive Diagnosis

本报告将当前 claudecode 使用从“花了多少 token”提升为“哪些工作方式最值得优化”。核心信号包括总消耗、估算与账单成本差距、缓存复用、subagent 占比、附件事件，以及项目集中度。This report reframes claudecode usage from raw token spend into work-pattern optimization. Core signals include total usage, estimated versus billed cost, cache reuse, subagent share, attachment events, and project concentration.

2. 效率机会2. Efficiency Opportunities

Vibe coding 效率的关键不是单纯降低 token，而是降低无效上下文构建、重复熟悉、压缩损失和等待中断。重点关注 CB:Output、forget curve、hourly productivity 与 compaction waste。The goal is not simply fewer tokens; it is less wasteful context building, less repeated re-familiarization, lower compaction loss, and fewer interruptions. Focus on CB:Output, forget curve, hourly productivity, and compaction waste.

3. 项目使用策略3. Project Portfolio Strategy

项目层面应优先治理 Pareto 头部项目：这些项目决定大部分成本，也最适合沉淀固定上下文、命令、测试入口和任务拆分规范。生命周期与连续性可以帮助判断项目是持续投入、短期爆发还是反复重启。At project level, prioritize the Pareto head: these projects drive most cost and benefit most from stable context, command lists, test entry points, and task-splitting rules. Lifecycle and continuity show whether projects are sustained, bursty, or repeatedly restarted.

4. 工具与治理4. Tools & Governance

工具治理关注权限模式、分支、native/internal 来源、API 错误与数据质量。目标是减少被权限、错误分支、网络/API 重试和不稳定环境打断的次数。Tool governance covers permission mode, branch, native/internal source, API errors, and data quality. The goal is fewer interruptions from permissions, wrong branches, API retries, and unstable environments.

5. 下一步行动清单5. Action Plan

下一次 session 立即执行Do this in the next session

• 下次开始大型任务前，先让 claudecode 明确目标、验收标准和不做事项，减少重复熟悉上下文。Before the next large task, state the goal, acceptance checks, and non-goals to reduce re-familiarization.
• 把高 token 项目拆成“探索、实现、验证”三个阶段，探索阶段优先用 subagent，主会话保留决策与执行。Split high-token projects into exploration, implementation, and validation; use subagents for exploration and keep decisions in the main session.
• 当 CB:Output 偏高时，先要求产出短计划和文件定位，再允许大范围读取，避免把上下文预算消耗在无效扫描上。When CB:Output is high, ask for a short plan and file targets before broad reads to avoid spending context on low-yield scanning.
• 每周复盘 Top 项目、Top 会话、压缩浪费和审批模式，把高成本但低产出的工作方式改成模板化流程。Review top projects, top sessions, compaction waste, and approval modes weekly, then turn high-cost/low-output patterns into reusable workflows.

每周复盘Weekly review

• 检查 Project Efficiency 表中的高成本项目，判断是否需要项目级 README、任务模板或常用命令清单。Check high-cost projects in Project Efficiency and decide whether they need a project README, task template, or command checklist.
• 关注 Forget Curve：反复重新熟悉的项目应补充稳定上下文文件，而不是每次重新让模型扫描。Watch the Forget Curve: projects with repeated re-familiarization should get stable context files instead of repeated scans.
• 审查 Approval Mode 和 Git Branch 分布，减少在错误分支或过严权限模式下反复中断的工作。Review approval mode and git branch distribution to reduce interruptions from wrong branches or overly strict modes.
• 对 subagent ROI 做抽样复盘：保留高价值探索，避免把可直接完成的小任务委派出去。Sample subagent ROI: keep high-value exploration and avoid delegating small tasks that can be completed directly.