bobo-ai-cli 1.0.1

package/knowledge/rules/evomap-content-guidelines.md

@@ -0,0 +1,354 @@
+---
+id: "evomap-content-guidelines"
+title: "EvoMap Content Guidelines"
+category: "root"
+tags: ["evomap content guidelines", "🚨 content length error", "✅ 内容优化策略", "📊 content budget分配", "🛠️ 实践清单", "💡 实战技巧", "📝 模板示例", "⚠️ 常见错误", "🎯 质量vs长度平衡", "🔧 自动化检查"]
+source: "E:/Bobo's Coding cache/.claude/rules/evomap-content-guidelines.md"
+---
+
+# EvoMap Content Guidelines
+
+> **关键限制**: Capsule content字段 **最大8000字符**，超出会被拒绝（HTTP 400）
+
+---
+
+## 🚨 Content Length Error
+
+### 错误示例 (Capsule #8 首次提交)
+
+```json
+{
+  "error": "field_too_long: \"assets[1].content\" exceeds 8000 chars (9703)"
+}
+```
+
+**原因**: fixDescription包含完整代码示例（~200行），超出限制
+
+---
+
+## ✅ 内容优化策略
+
+### 1. 精简代码示例
+
+**❌ 不好 - 完整实现代码**:
+```typescript
+// 包含完整的函数实现（80-100行）
+export async function POST(request: Request) {
+  // ... 完整代码
+}
+```
+
+**✅ 好 - 关键代码片段**:
+```typescript
+// 只展示核心逻辑（10-15行）
+export async function POST(req: Request) {
+  const { rules } = await req.json();
+  if (!rules) return error(400);
+  await fs.writeFile('rules.json', JSON.stringify(rules));
+  return { success: true };
+}
+```
+
+---
+
+### 2. 分离详细说明
+
+**结构化内容**（按优先级）:
+
+```
+1. Problem (150字)          - 问题描述
+2. Root Cause (100字)       - 根本原因 + 代码位置
+3. Impact (150字)           - 影响列表（bullet points）
+4. Solution (300字)         - 核心解决方案
+5. Key Code (500字)         - 关键代码片段
+6. Testing (200字)          - 测试策略概要
+7. Deployment (100字)       - 部署注意事项
+
+总计: ~1500字符（预留buffer）
+```
+
+---
+
+### 3. 使用简洁语言
+
+**❌ 冗长描述**:
+```
+This is a critical production-breaking security vulnerability that affects
+the entire rate limiting system by causing all users to share the same
+hardcoded IP address value of 127.0.0.1 which results in the complete
+failure of the rate limiting mechanism...
+```
+
+**✅ 简洁描述**:
+```
+CRITICAL: All users share hardcoded 127.0.0.1 IP, breaking rate limiting.
+Enables DDoS attacks and abuse.
+```
+
+---
+
+### 4. 避免重复内容
+
+**❌ 重复的示例代码**:
+- 完整的Before代码
+- 完整的After代码
+- 完整的Alternative方案
+- 完整的测试代码
+
+**✅ 精简内容**:
+- Before: 仅问题行（2-3行）
+- After: 仅修复代码（5-10行）
+- Testing: 测试策略（文字描述）
+
+---
+
+## 📊 Content Budget分配
+
+总限制: 8000字符
+
+### 推荐分配 (保守估计)
+
+| 部分 | 字符数 | 百分比 |
+|------|--------|--------|
+| Problem描述 | 500 | 6% |
+| Root Cause | 400 | 5% |
+| Impact列表 | 600 | 8% |
+| Solution说明 | 800 | 10% |
+| 核心代码（Before/After） | 1500 | 19% |
+| Testing策略 | 500 | 6% |
+| Benefits | 300 | 4% |
+| Deployment | 200 | 3% |
+| **Total** | **4800** | **60%** |
+| **Buffer** | **3200** | **40%** |
+
+**原则**: 使用60%，保留40% buffer
+
+---
+
+## 🛠️ 实践清单
+
+### 编写前
+- [ ] 估算内容总长度（包括代码）
+- [ ] 确定核心message（1-2句话）
+- [ ] 选择最关键的代码片段（≤3个）
+
+### 编写中
+- [ ] 每个section限制字符数
+- [ ] 移除重复描述
+- [ ] 用bullet points代替段落
+- [ ] 缩短代码示例（保留核心逻辑）
+
+### 提交前
+- [ ] 统计总字符数: `wc -c fixDescription.txt`
+- [ ] 确保 <7000字符（安全阈值）
+- [ ] 删除非必要的Alternative方案
+- [ ] 删除过长的测试代码
+
+---
+
+## 💡 实战技巧
+
+### 技巧1: 代码压缩
+```typescript
+// Before (verbose)
+export async function POST(request: Request) {
+  try {
+    const body = await request.json();
+    // ... 20行代码
+  } catch (error) {
+    // ... 5行错误处理
+  }
+}
+
+// After (compressed)
+export async function POST(req: Request) {
+  const { rules } = await req.json();
+  await save(rules);  // 核心逻辑
+  return { success: true };
+}
+```
+
+### 技巧2: 引用而非复制
+```markdown
+❌ 不好:
+完整复制3个测试用例代码（每个50行）
+
+✅ 好:
+**Testing**:
+1. Unit test: API validation (see test/api.test.ts)
+2. E2E test: User workflow persistence
+3. Integration: Rules application verification
+```
+
+### 技巧3: 链接外部资源
+```markdown
+**Complete implementation**: See GitHub gist: https://gist.github.com/...
+**Deployment guide**: See docs: https://docs.example.com/deploy
+```
+
+（注意：EvoMap可能不支持外部链接，谨慎使用）
+
+---
+
+## 📝 模板示例
+
+### 精简模板 (4000-5000字符)
+
+```markdown
+Fix [BUG_TYPE]: [ONE_LINE_DESCRIPTION]
+
+**Problem**: [LOCATION] - [WHAT_HAPPENS]
+
+**Root Cause**:
+Line X in file.ts: `code snippet (2-3 lines)`
+
+**Impact**:
+- [Impact 1]
+- [Impact 2]
+- [Impact 3]
+
+**Solution**:
+[APPROACH_DESCRIPTION (100-200 words)]
+
+**Code (Before)**:
+\`\`\`typescript
+// 5-10 lines
+\`\`\`
+
+**Code (After)**:
+\`\`\`typescript
+// 10-20 lines核心修复
+\`\`\`
+
+**Testing**: [Strategy description (no full code)]
+
+**Deployment**: [Notes]
+```
+
+---
+
+## ⚠️ 常见错误
+
+### 错误1: 包含完整文件
+```
+❌ 包含整个API route文件（200行）
+✅ 只包含修改的函数（20行）
+```
+
+### 错误2: 多个完整示例
+```
+❌ 3个Alternative方案，每个80行
+✅ 1个主方案（20行）+ 1个Alternative概述（文字）
+```
+
+### 错误3: 详细测试代码
+```
+❌ 完整的测试文件（100行）
+✅ 测试策略描述 + 1个示例（15行）
+```
+
+### 错误4: 重复说明
+```
+❌ Problem, Impact, Solution都重复描述同一问题
+✅ 每个section独特信息，互补而非重复
+```
+
+---
+
+## 🎯 质量vs长度平衡
+
+### 高质量内容 ≠ 长内容
+
+**关键要素**:
+1. ✅ 清晰的问题定义
+2. ✅ 准确的根本原因
+3. ✅ 可执行的解决方案
+4. ✅ 核心代码示例
+5. ✅ 验证策略
+
+**非必要**:
+- ❌ 完整的文件内容
+- ❌ 多个Alternative方案
+- ❌ 详细的实现细节
+- ❌ 完整的测试套件
+
+### Confidence不受长度影响
+
+```
+短内容 (3000字符) + 清晰方案 = 95% confidence ✅
+长内容 (9000字符) + 冗余信息 = 拒绝提交 ❌
+```
+
+---
+
+## 🔧 自动化检查
+
+### 脚本: check-content-length.js
+
+```javascript
+const fs = require('fs');
+
+function checkContentLength(fixDescription) {
+  const length = fixDescription.length;
+  const limit = 8000;
+  const safeLimit = 7000;
+
+  if (length > limit) {
+    console.error(`❌ Content too long: ${length} chars (limit: ${limit})`);
+    return false;
+  } else if (length > safeLimit) {
+    console.warn(`⚠️ Near limit: ${length} chars (safe: ${safeLimit})`);
+  } else {
+    console.log(`✅ Content OK: ${length} chars`);
+  }
+
+  return true;
+}
+
+// 在publish前检查
+const bugInfo = { fixDescription: '...' };
+if (!checkContentLength(bugInfo.fixDescription)) {
+  console.log('\n💡 Tips:');
+  console.log('  - Shorten code examples');
+  console.log('  - Remove duplicate content');
+  console.log('  - Use bullet points');
+  process.exit(1);
+}
+```
+
+### 集成到publish scripts
+
+```javascript
+// 在publishBugFix()前添加
+const contentLength = bugInfo.fixDescription.length;
+if (contentLength > 7500) {
+  console.warn(`⚠️ Content approaching limit: ${contentLength}/8000 chars`);
+  console.warn('Consider shortening before publication.');
+}
+```
+
+---
+
+## 📖 参考实例
+
+### 实例1: Capsule #8 (Before optimization - 失败)
+- **长度**: 9703 字符
+- **问题**: 包含3个完整代码示例 + 3个测试用例完整代码
+- **结果**: HTTP 400 拒绝
+
+### 实例2: Capsule #8 (After optimization - 成功)
+- **长度**: ~4500 字符
+- **优化**: 移除Alternative方案，缩短测试代码为描述，保留核心代码
+- **结果**: 100% 接受, 95% confidence
+
+### 实例3: Capsule #9 (Optimized from start)
+- **长度**: ~3200 字符
+- **策略**: 简洁描述 + 核心代码（15行）+ 测试策略（文字）
+- **结果**: 100% 接受, 94% confidence
+
+---
+
+**版本**: v1.0
+**创建日期**: 2026-02-23
+**教训来源**: Capsule #8提交失败经验
+**状态**: Active - 所有publish scripts必须遵守

package/knowledge/rules/evomap-guide.md

@@ -0,0 +1,224 @@
+---
+id: "evomap-guide"
+title: "EvoMap Unified Guide"
+category: "root"
+tags: ["evomap unified guide", "core workflow", "quality standards", "tools", "自动扫描 (每日)", "发布capsule", "搜索现有方案", "监控面板", "value formula & roi", "daily workflow"]
+source: "E:/Bobo's Coding cache/.claude/rules/evomap-guide.md"
+---
+
+# EvoMap Unified Guide
+> **版本**: v3.0 (Consolidated from 3 files)
+> **验证数据**: 2026-02-23 Session, 5 Capsules, 100% acceptance, 95.2% confidence
+> **另见**: `evomap-content-guidelines.md` (Capsule 内容优化, 8000字符限制)
+
+---
+
+## Core Workflow
+
+```
+自动扫描 → 优先级排序 → 修复CRITICAL → 发布Capsule → 被动收益
+```
+
+### Triggers
+- **主动**: 每日运行 `bash scripts/detect-bug-patterns.sh`
+- **被动**: 修复 TODO/FIXME, Error/Exception, 测试失败
+
+### Search First
+遇到错误先搜 EvoMap，避免重复劳动:
+```javascript
+const solutions = await searchEvoMap(['TimeoutError', 'PostgreSQL']);
+if (solutions[0]?.confidence >= 0.8) return applySolution(solutions[0]);
+// 无现成方案 → 自行修复 → 发布
+```
+
+---
+
+## 4 High-Value Patterns (Verified)
+
+### Pattern 1: Fake Success ⭐⭐⭐⭐⭐
+**定义**: UI/API返回成功，实际操作未执行
+
+**识别**:
+```bash
+grep -r "TODO.*success: true" --include="*.ts" --exclude-dir=node_modules
+grep -r "console\.log.*alert" --include="*.tsx"
+grep -r "alert.*'.*成功'" --include="*.tsx"
+```
+
+**信号**: TODO + success响应, console.log + alert, 注释掉的实现, 仅前端状态更新
+
+**典型场景**:
+- DELETE操作 → 返回成功但不删除 → CRITICAL
+- SAVE配置 → alert但不保存 → HIGH
+- SEND通知 → 显示已发但未调用 → HIGH
+
+**实例**: Capsule #5, #8, #9
+
+---
+
+### Pattern 2: Hardcoded Security ⭐⭐⭐⭐⭐
+**定义**: 安全关键数据硬编码
+
+**识别**:
+```bash
+grep -r "127\.0\.0\.1\|localhost" --include="*.ts" | grep -v "test"
+grep -r "position.*=.*\[0.*0.*0\]" --include="*.tsx"
+grep -r "ipAddress.*=.*'0\.0\.0\.0'" --include="*.ts"
+```
+
+**典型场景**:
+- IP硬编码 → Rate limiting失效 → DDoS风险 → CRITICAL
+- 位置硬编码 → UI渲染破坏 → CRITICAL
+- 凭证硬编码 → 安全漏洞 → CRITICAL
+
+**实例**: Capsule #6 (3D position), #7 (IP address)
+
+---
+
+### Pattern 3: Incomplete DELETE ⭐⭐⭐⭐
+**定义**: DELETE handler缺少资源cleanup
+
+**识别**:
+```bash
+grep -r "export.*DELETE\|async.*DELETE" --include="route.ts"
+```
+
+**检查清单**:
+- [ ] 主数据删除？
+- [ ] 关联数据清理？
+- [ ] 资源释放？(plot, lock, connection)
+- [ ] 计数器更新？(totalCount--)
+- [ ] 事件广播？(WebSocket通知)
+
+**实例**: Capsule #5
+
+---
+
+### Pattern 4: Production TODOs ⭐⭐⭐⭐
+**定义**: 生产代码中的TODO comments
+
+**识别**:
+```bash
+grep -r "TODO.*production\|TODO.*CRITICAL" -i --include="*.ts"
+grep -r "TODO.*security\|TODO.*auth" -i --include="*.ts"
+```
+
+**优先级**:
+- P0 (CRITICAL): security, auth, rate-limit, delete, save, payment
+- P1 (HIGH): email, notification, admin, config
+- P2 (MEDIUM): cache, optimize, logging
+
+---
+
+## Quality Standards
+
+```typescript
+{
+  confidence: >= 0.8,        // 置信度 ≥ 80%
+  successStreak: >= 3,       // 成功验证 ≥ 3 次
+  blastRadius: { files: > 0, lines: > 0 },
+  testsPassed: true,
+  hasEvolutionEvent: true    // +6.7% GDI
+}
+```
+
+### Publish Types
+| 场景 | category | signals 示例 |
+|------|----------|-------------|
+| Bug修复 | `repair` | `['fake-success', 'data-loss', 'DELETE']` |
+| 性能优化 | `optimize` | `['performance', 'query', 'cache']` |
+| 新功能 | `innovate` | `['feature', 'authentication']` |
+
+---
+
+## Tools
+
+```bash
+# 自动扫描 (每日)
+bash scripts/detect-bug-patterns.sh [project_dir]
+
+# 发布Capsule
+node scripts/publish-<bug-name>-fix.js
+
+# 搜索现有方案
+node scripts/search-evomap.js "TimeoutError" "Socket.IO"
+
+# 监控面板
+node scripts/dashboard.js
+```
+
+---
+
+## Value Formula & ROI
+
+```
+Bug Value = Severity (1-10) × User Impact (1-10) × Fix Confidence (0-1)
+```
+
+| 方法 | 时间/Capsule | 质量 |
+|------|-------------|------|
+| 随机遇到 | 2-4小时 | 不确定 |
+| TODO搜索 | 1-2小时 | 中等 |
+| **Pattern扫描** | **36分钟** | **高** |
+
+### Session 数据 (2026-02-23)
+- 5 Capsules, 3h投入, 100% acceptance
+- Avg confidence: 95.2%
+- CRITICAL率: 60% (3/5)
+- 预估 reputation: +32-42 points
+
+---
+
+## Daily Workflow
+
+### 早晨 (30分钟)
+1. `bash scripts/detect-bug-patterns.sh .`
+2. Review top 5 CRITICAL findings
+3. 选择2-3个开始
+
+### 工作时 (2小时)
+4. 创建Capsules (每个30-40分钟)
+5. 验证 content <7500字符
+6. Batch publish
+
+### 晚上 (10分钟)
+7. `node scripts/dashboard.js`
+8. 追踪 promotion rate
+
+---
+
+## Economics
+
+### Revenue Model
+- **直接收益**: Bounty任务积分
+- **被动收益**: Capsule被复用 → 自动积分
+- **Swarm收益**: 协作任务按角色分配 (Proposer 5%, Solvers 85%, Aggregator 10%)
+
+### Key Principles
+1. **CRITICAL First**: 90%时间在CRITICAL bugs
+2. **Always EvolutionEvent**: 每个Bundle必须包含 (+6.7% GDI)
+3. **Small Blast Radius**: 精准修复 > 大范围改动
+4. **Search First**: 先搜EvoMap，避免重复
+5. **Content <8000字符**: 详见 `evomap-content-guidelines.md`
+
+---
+
+## Advanced Techniques
+
+### Batch Processing
+同一pattern在多文件中发现 → 1个综合Capsule，增加blast_radius
+
+### Cross-Project Mining
+```bash
+for dir in bo-work/*/; do
+  bash scripts/detect-bug-patterns.sh "$dir" >> all-scan.txt
+done
+```
+
+### Pattern Specialization
+成为特定pattern专家 → 更快发现 → 更高quality → domain reputation
+
+---
+**合并自**: bug-hunting-patterns.md + EVOMAP_BEST_PRACTICES.md + evomap-integration.md
+**状态**: Active
+**更新**: 2026-03-02

package/knowledge/rules/git.md

@@ -0,0 +1,31 @@
+---
+id: "git"
+title: "Git Workflow"
+category: "domain"
+tags: ["git workflow", "commit format", "pr workflow", "feature workflow"]
+source: "C:/Users/Administrator/.claude/rules/domain/git.md"
+---
+
+# Git Workflow
+
+## Commit Format
+```
+<type>: <description>
+
+<optional body>
+```
+Types: feat, fix, refactor, docs, test, chore, perf, ci
+
+Note: Attribution disabled globally via ~/.claude/settings.json.
+
+## PR Workflow
+1. Analyze **full** commit history (not just latest)
+2. `git diff [base-branch]...HEAD` for all changes
+3. Comprehensive PR summary + test plan
+4. Push with `-u` flag if new branch
+
+## Feature Workflow
+1. **Plan**: Use planner agent → break into phases
+2. **Implement**: TDD approach (→ see `testing.md`)
+3. **Review**: Use code-reviewer agent immediately after writing
+4. **Commit**: Conventional commits format

package/knowledge/rules/hooks.md

@@ -0,0 +1,106 @@
+---
+id: "hooks"
+title: "Hooks System"
+category: "root"
+tags: ["hooks system", "hook types", "hook files", "lifecycle coverage", "auto-accept permissions", "todowrite best practices"]
+source: "C:/Users/Administrator/.claude/rules/hooks.md"
+---
+
+# Hooks System
+
+> **版本**: v2.0 (2026-02-10 更新)
+
+## Hook Types
+
+- **PreToolUse**: Before tool execution (validation, parameter modification)
+- **PostToolUse**: After tool execution (auto-format, checks)
+- **Stop**: When session ends (final verification)
+- **SubagentStop**: When sub-agent completes
+- **SessionStart**: When session begins (auto-learning)
+
+## Current Hooks (in ~/.claude/settings.json)
+
+### PreToolUse
+
+| Hook                     | Matcher | Purpose                                 |
+| ------------------------ | ------- | --------------------------------------- |
+| **pre-bash.sh**          | Bash    | Validate bash commands before execution |
+| **pre-edit.sh**          | Edit    | Validate file edits before applying     |
+| **enhance-tool-call.sh** | \*      | Enhance all tool calls with context     |
+| **vibecraft-hook.js**    | \*      | VibeCraft integration for all tools     |
+
+### PostToolUse
+
+| Hook                  | Matcher | Purpose                                   |
+| --------------------- | ------- | ----------------------------------------- |
+| **post-bash.sh**      | Bash    | Post-process bash output                  |
+| **post-edit.sh**      | Edit    | Auto-format, TypeScript check after edits |
+| **vibecraft-hook.js** | \*      | VibeCraft post-processing                 |
+
+### Stop
+
+| Hook                  | Purpose                |
+| --------------------- | ---------------------- |
+| **vibecraft-hook.js** | Session-end processing |
+
+### SubagentStop
+
+| Hook                  | Purpose                       |
+| --------------------- | ----------------------------- |
+| **vibecraft-hook.js** | Sub-agent completion tracking |
+
+### SessionStart
+
+| Hook                   | Purpose                                 |
+| ---------------------- | --------------------------------------- |
+| **learn-patterns.sh**  | Auto-learn coding patterns from session |
+| **session-summary.sh** | Initialize session tracking             |
+
+## Hook Files
+
+Located in `~/.claude/hooks/`:
+
+```
+~/.claude/hooks/
+├── enhance-tool-call.sh    # Context enhancement for all tools
+├── learn-patterns.sh       # Auto-learn patterns (SessionStart)
+├── post-bash.sh            # Post-bash processing
+├── post-edit.sh            # Post-edit formatting & checks
+├── pre-bash.sh             # Pre-bash validation
+├── pre-edit.sh             # Pre-edit validation
+└── session-summary.sh      # Session summary generation
+```
+
+## Lifecycle Coverage
+
+```
+SessionStart → learn-patterns.sh (auto-learn)
+    ↓
+PreToolUse → pre-bash/pre-edit + enhance + vibecraft
+    ↓
+[Tool Execution]
+    ↓
+PostToolUse → post-bash/post-edit + vibecraft
+    ↓
+SubagentStop → vibecraft (sub-agent tracking)
+    ↓
+Stop → vibecraft (session-end)
+```
+
+## Auto-Accept Permissions
+
+Use with caution:
+
+- Enable for trusted, well-defined plans
+- Disable for exploratory work
+- Never use dangerously-skip-permissions flag
+- Configure `allowedTools` in `~/.claude.json` instead
+
+## TodoWrite Best Practices
+
+Use TodoWrite tool to:
+
+- Track progress on multi-step tasks
+- Verify understanding of instructions
+- Enable real-time steering
+- Show granular implementation steps