Core Framework
Competition is a learning accelerator. Every loss contains the lesson that wins don't.
- 1. Analyze the Loss — Don't just lose, understand WHY
- Study the Winner — What did they do that you didn't?
- Track the Delta — Measure the gap, watch it shrink
- Iterate — Apply lessons, compete again, repeat
The Post-Loss Protocol
After any competitive loss, extract value:
| Question | Purpose |
|---|
| At what moment did the outcome shift? | Find the decision point |
| What did they do that I didn't? |
Identify the winning move |
| What would I do differently? | Formulate the lesson |
| Is this a pattern? | Check history for repeats |
Don't rationalize. Don't blame externals. Extract the actionable insight.
Tracking (What to Measure)
Create a tracking folder in the user's workspace:
CODEBLOCK0
For each domain, track:
- - Win/loss record with dates
- Specific losses analyzed (who, why, lesson)
- Patterns identified (recurring weaknesses)
- Progress metrics (are lessons translating to wins?)
Rival Intelligence
Know your competition:
- - Profile rivals — Their strengths, weaknesses, tendencies
- Monitor changes — When they improve or change strategy
- Find their edge — What specifically makes them beat you?
- Study up — Find examples of them losing, analyze what worked
Quick Reference
| Situation | Action |
|---|
| Just lost | Run post-loss protocol, add to log |
| Pattern emerging |
Document it, create drill/fix |
| Preparing for known rival | Review their profile, past matches |
| Plateau in progress | Analyze recent losses for new patterns |
| Won against usual winner | Document what changed, replicate |
Load Reference
| Need | File |
|---|
| Domain-specific strategies | INLINECODE0 |
| Deep loss analysis framework |
analysis.md |
| Progress tracking templates |
tracking.md |
| Feedback loop mechanics |
feedback.md |
核心框架
竞争是学习的加速器。每一次失败都蕴含着胜利无法给予的教训。
- 1. 分析失败 — 不要仅仅接受失败，要理解失败的原因
- 研究胜者 — 他们做了什么而你没有做到？
- 追踪差距 — 衡量差距，观察其缩小过程
- 迭代改进 — 应用教训，再次竞争，重复循环
失败后处理流程
在任何竞争失利后，提取价值：
| 问题 | 目的 |
|---|
| 结果在哪个时刻发生了转变？ | 找到决策点 |
| 他们做了什么而我没有做到？ |
识别制胜之举 |
| 我会做出哪些不同的选择？ | 总结教训 |
| 这是否是一种模式？ | 检查历史中是否有重复 |
不要合理化。不要归咎于外部因素。提取可执行的洞见。
追踪（衡量指标）
在用户工作区创建追踪文件夹：
~/competing/
├── domains/ # 按领域追踪
├── rivals.md # 对手档案
├── log.md # 胜负记录及教训
└── progress.md # 随时间变化的指标
针对每个领域，追踪：
- - 带日期的胜负记录
- 具体失败案例分析（对手、原因、教训）
- 识别出的模式（反复出现的弱点）
- 进展指标（教训是否转化为胜利？）
对手情报
了解你的竞争对手：
- - 分析对手档案 — 他们的优势、劣势、倾向
- 监测变化 — 当他们改进或改变策略时
- 找到他们的优势 — 具体是什么让他们击败你？
- 研究学习 — 寻找他们失败的案例，分析有效方法
快速参考
| 情况 | 行动 |
|---|
| 刚刚失败 | 执行失败后处理流程，记录到日志 |
| 出现模式 |
记录在案，制定训练/解决方案 |
| 准备应对已知对手 | 查看其档案和过往比赛记录 |
| 进展停滞 | 分析近期失败，寻找新模式 |
| 击败了常胜对手 | 记录变化因素，复制成功经验 |
加载参考
| 需求 | 文件 |
|---|
| 特定领域策略 | domains.md |
| 深度失败分析框架 |
analysis.md |
| 进展追踪模板 | tracking.md |
| 反馈循环机制 | feedback.md |
