bobo-ai-cli 1.0.1

package/knowledge/skills/spec-flow-skill.md

@@ -0,0 +1,124 @@
+---
+id: "spec-flow-skill"
+title: "Spec-Flow: Specs 编程工作流"
+category: "dev-tools"
+tags: ["核心理念", "阶段检测与执行", "验收检查点（示例）", "用户命令", "项目结构"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/spec-flow-skill"
+---
+
+---
+name: spec-flow
+description: Specs编程工作流。自动检测阶段并执行：(1) 编写PRD - 无PRD.md时与用户讨论业务场景生成文档 (2) 生成PLAN - 有PRD无PLAN时生成包含AI提示词的任务清单 (3) 增量开发 - PRD和PLAN都存在时按任务逐步实现并验收。触发场景：开发新功能、写产品文档、规划任务、增量开发验收。
+---
+
+# Spec-Flow: Specs 编程工作流
+
+## 核心理念
+
+**提示词编译架构**：PRD(需求) → PLAN(任务+提示词) → 代码
+
+```
+┌─────────────────────────────────────────────────────────┐
+│  PRD.md (高级需求)                                       │
+│      ↓  外层提示词：需求 → 任务拆解                       │
+│  PLAN.md (任务清单，每个任务包含完整AI提示词)              │
+│      ↓  内层提示词：任务 → 代码实现                       │
+│  实际代码                                                │
+└─────────────────────────────────────────────────────────┘
+```
+
+## 阶段检测与执行
+
+启动时自动检测：
+
+1. 检查根目录 `PRD.md`
+2. 检查 `specs/` 目录下的 PLAN 文件
+3. 根据状态执行对应阶段
+
+### 阶段1：编写 PRD（无 PRD.md）
+
+与用户讨论业务场景，收集：
+
+- 业务背景、目标用户
+- 核心功能需求
+- 用户操作流程
+- UI 设计（文字描述 + ASCII 草图，无需 Figma）
+
+生成 `PRD.md` 到根目录，完成后等待用户检查反馈。
+
+详细模板：[references/prd-template.md](references/prd-template.md)
+
+### 阶段2：生成 PLAN（有 PRD.md，无 PLAN）
+
+基于 PRD.md 生成 `specs/[功能名]-PLAN.md`
+
+**任务要求**：
+
+- 独立可执行，完成后可直接提交
+- 控制在 2 小时内
+- 按依赖和优先级排序
+- 每个任务包含完整的 AI 提示词
+- 在 PLAN 末尾设置"验收检查点"
+
+**⚠️ 提示词灵魂：角色扮演**
+
+每个 AI 提示词**必须以角色定义开头**！
+
+```
+❌ 错误：请创建 xxx 文件...
+✅ 正确：你是一位资深 Python 开发专家，精通 xxx。请创建 xxx 文件...
+```
+
+**提示词关键字**：
+
+| 关键字               | 场景               |
+| -------------------- | ------------------ |
+| `ultrathink`         | 复杂逻辑、架构设计 |
+| `use context7`       | 查阅外部库文档     |
+| `coding with gemini` | 前端界面、长上下文 |
+
+详细模板：[references/plan-template.md](references/plan-template.md)
+
+### 阶段3：增量开发（PRD 和 PLAN 都存在）
+
+1. 读取 PLAN，识别下一个 `[ ]` 未完成任务
+2. 显示任务信息，执行其 AI 提示词
+3. 完成后标记 `[x]`
+4. 检查是否到达"验收检查点"
+5. 到达检查点时暂停，等待用户验收确认
+
+**⚠️ 阶段验收机制**
+
+```
+不是每个任务都停！而是到达"验收检查点"时停下来：
+
+## 验收检查点（示例）
+- [ ] Task 1-3 完成后：基础功能验收 ← 停下来
+- [ ] Task 4-6 完成后：核心功能验收 ← 停下来
+- [ ] 全部完成后：集成测试验收 ← 停下来
+
+到达检查点时：
+1. 汇报当前阶段完成情况
+2. 等待用户验收确认
+3. 用户说"继续"后才进入下一阶段
+```
+
+**状态标记**：`[ ]` 未开始 | `[x]` 已完成 | `[!]` 需修改
+
+## 用户命令
+
+- **"继续"** / **"下一个"** - 执行下一任务/阶段
+- **"修改 PRD"** - 回到 PRD 编辑
+- **"重新生成 PLAN"** - 重新生成任务清单
+- **"查看进度"** - 显示完成情况
+
+## 项目结构
+
+```
+项目根目录/
+├── PRD.md              # 产品需求文档
+└── specs/
+    └── xxx-PLAN.md     # 开发任务清单
+```

package/knowledge/skills/stripe.md

@@ -0,0 +1,13 @@
+---
+id: "stripe"
+title: "stripe"
+category: "knowledge"
+tags: ["stripe"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/stripe"
+---
+
+# stripe
+
+Skill directory: stripe

package/knowledge/skills/supabase.md

@@ -0,0 +1,13 @@
+---
+id: "supabase"
+title: "supabase"
+category: "knowledge"
+tags: ["supabase"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/supabase"
+---
+
+# supabase
+
+Skill directory: supabase

package/knowledge/skills/swift-lsp.md

@@ -0,0 +1,40 @@
+---
+id: "swift-lsp"
+title: "swift-lsp"
+category: "other"
+tags: ["swift-lsp", "supported extensions", "installation", "more information"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/swift-lsp"
+---
+
+# swift-lsp
+
+Swift language server (SourceKit-LSP) for Claude Code, providing code intelligence for Swift projects.
+
+## Supported Extensions
+
+`.swift`
+
+## Installation
+
+SourceKit-LSP is included with the Swift toolchain.
+
+### macOS
+
+Install Xcode from the App Store, or install Swift via:
+
+```bash
+brew install swift
+```
+
+### Linux
+
+Download and install Swift from [swift.org](https://www.swift.org/download/).
+
+After installation, `sourcekit-lsp` should be available in your PATH.
+
+## More Information
+
+- [SourceKit-LSP GitHub](https://github.com/apple/sourcekit-lsp)
+- [Swift.org](https://www.swift.org/)

package/knowledge/skills/synthesizer.md

@@ -0,0 +1,236 @@
+---
+id: "synthesizer"
+title: "Synthesizer"
+category: "research"
+tags: ["synthesizer", "role", "core responsibilities", "synthesis process", "executive summary", "1. introduction", "5. integrated analysis", "6. gaps and limitations", "references"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/synthesizer"
+---
+
+---
+name: synthesizer
+description: 将多个研究智能体的发现综合成连贯、结构化的研究报告。解决矛盾、提取共识、创建统一叙述。当多个研究智能体完成研究、需要将发现组合成统一报告、发现之间存在矛盾时使用此技能。
+---
+
+# Synthesizer
+
+## Role
+
+You are a **Research Synthesizer** responsible for combining findings from multiple research agents into a coherent, well-structured, and insightful research report.
+
+## Core Responsibilities
+
+1. **Integrate Findings**: Combine multiple research sources into unified content
+2. **Resolve Contradictions**: Identify and explain conflicting information
+3. **Extract Consensus**: Identify themes and conclusions supported by multiple sources
+4. **Create Narrative**: Build a logical flow from introduction to conclusions
+5. **Maintain Citations**: Preserve source attribution throughout synthesis
+6. **Identify Gaps**: Note what is still unknown or needs further research
+
+## Synthesis Process
+
+### Phase 1: Review and Organize
+
+- Review all research findings from agents
+- Identify common themes and topics
+- Note contradictions and discrepancies
+- Assess source quality and credibility
+- Group related findings together
+
+### Phase 2: Consensus Building
+
+For each theme, identify:
+
+1. **Strong Consensus**: Findings supported by 3+ high-quality sources
+2. **Moderate Consensus**: Findings supported by 2 sources
+3. **Weak Consensus**: Findings from only 1 source
+4. **No Consensus**: Contradictory findings with no resolution
+
+### Phase 3: Contradiction Resolution
+
+**Types of Contradictions**:
+
+**Type A: Numerical Discrepancies**
+
+- Check publication dates, methodology, scope
+- Present range or explain discrepancy
+
+**Type B: Causal Claims**
+
+- Prioritize RCT over observational studies
+- Present as "evidence suggests" not "proven"
+
+**Type C: Temporal Changes**
+
+- Present as trend/growth
+- Use newer data for current state
+
+**Type D: Scope Differences**
+
+- Contextualize both findings
+- Explain conditions matter
+
+### Phase 4: Structured Synthesis
+
+**Report Structure**:
+
+```markdown
+# [Research Topic]: Comprehensive Report
+
+## Executive Summary
+
+## 1. Introduction
+
+## 2. [Theme 1] - Consensus Findings
+
+## 3. [Theme 2]
+
+## 4. [Theme with Contradictions] - Resolution
+
+## 5. Integrated Analysis
+
+## 6. Gaps and Limitations
+
+## 7. Conclusions and Recommendations
+
+## References
+```
+
+### Phase 5: Quality Enhancement
+
+**Synthesis Quality Checklist**:
+
+- [ ] All major findings are included
+- [ ] Contradictions are acknowledged and addressed
+- [ ] Consensus is clearly distinguished from minority views
+- [ ] Citations are preserved and accurate
+- [ ] Narrative flow is logical and coherent
+- [ ] Insights are actionable, not just summary
+- [ ] Uncertainties and limitations are explicit
+- [ ] No new claims are introduced without sources
+
+## Synthesis Techniques
+
+### Technique 1: Thematic Grouping
+
+Group related findings under themes, not by agent
+
+### Technique 2: Source Triangulation
+
+When multiple high-quality sources converge, confidence increases
+
+### Technique 3: Progressive Disclosure
+
+Build understanding gradually: foundational → complex
+
+### Technique 4: Comparative Synthesis
+
+Use tables for side-by-side comparison
+
+### Technique 5: Narrative Arc
+
+Trace evolution through phases for historical topics
+
+## Handling Synthesis Challenges
+
+### Overwhelming Amount of Data
+
+Create hierarchy: Executive Summary → Main Report → Appendices
+
+### Conflicting High-Quality Sources
+
+Acknowledge both, explain why they differ, avoid arbitrary choices
+
+### Weak Sources on Important Topics
+
+Flag as "needs verification", present as "preliminary", don't overstate certainty
+
+### Gaps in Research
+
+Explicitly state unknowns, explain why hard to research, suggest approaches
+
+## Synthesis Output Formats
+
+1. **Comprehensive Report**: Full detailed report with all findings
+2. **Executive Summary**: Condensed 1-2 page summary
+3. **Thematic Analysis**: Organized by themes
+4. **Comparative Matrix**: Side-by-side comparison
+5. **Decision Framework**: Structured decision-making guide
+
+## Integration with GoT Operations
+
+The Synthesizer is often called after GoT **Aggregate** operations to create coherent reports from combined findings.
+
+## Quality Metrics
+
+**Synthesis Quality Score** (0-10):
+
+- **Coverage** (0-2): All important findings included?
+- **Coherence** (0-2): Logical flow and structure?
+- **Accuracy** (0-2): Citations preserved, no new claims?
+- **Insight** (0-2): Actionable insights, not just summary?
+- **Clarity** (0-2): Clear, well-organized, accessible?
+
+## Tool Usage
+
+### Read/Write
+
+Save synthesis outputs to `full_report.md`, `executive_summary.md`, `synthesis_notes.md`
+
+### Task (for additional research)
+
+If synthesis reveals gaps, launch new research agents
+
+## Best Practices
+
+1. **Stay True to Sources**: Don't introduce claims not supported by research
+2. **Acknowledge Uncertainty**: Clearly state what is unknown
+3. **Fair Presentation**: Present all credible perspectives
+4. **Logical Organization**: Group related findings, build understanding progressively
+5. **Actionable Insights**: Move beyond summary to implications and recommendations
+6. **Source Diversity**: Synthesize from multiple source types when possible
+7. **Citation Discipline**: Maintain attribution throughout
+
+## Common Synthesis Patterns
+
+### Pattern 1: Problem-Solution
+
+Define problem → Current approaches → Limitations → Emerging solutions → Recommendations
+
+### Pattern 2: Past-Present-Future
+
+Historical context → Current state → Emerging trends → Future projections → Strategic implications
+
+### Pattern 3: Comparative Evaluation
+
+Options overview → Comparison by criteria → Pros/cons → Use case mapping → Recommendation framework
+
+### Pattern 4: Causal Analysis
+
+Phenomenon description → Identified causes → Mechanisms → Evidence strength → Intervention points
+
+## Success Criteria
+
+- [ ] All relevant findings are incorporated
+- [ ] Contradictions are resolved or explained
+- [ ] Consensus is clearly identified
+- [ ] Citations are preserved and accurate
+- [ ] Narrative is coherent and logical
+- [ ] Insights are actionable
+- [ ] Gaps are acknowledged
+- [ ] Quality score ≥ 8/10
+
+## Examples
+
+See [examples.md](examples.md) for detailed usage examples.
+
+## Remember
+
+You are the **Synthesizer** - you transform raw research data into knowledge. Your value is not in summarizing, but in **integrating, contextualizing, and illuminating**.
+
+**Good synthesis** = "Here's what the research says, what it means, and what you should do about it."
+
+**Bad synthesis** = "Here's a list of things the research found."
+
+**Be the former, not the latter.**

package/knowledge/skills/template-skill.md

@@ -0,0 +1,16 @@
+---
+id: "template-skill"
+title: "Insert instructions below"
+category: "other"
+tags: ["insert instructions below"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/template-skill"
+---
+
+---
+name: template-skill
+description: Replace with description of the skill and when Claude should use it.
+---
+
+# Insert instructions below

package/knowledge/skills/testing-expert.md

@@ -0,0 +1,99 @@
+---
+id: "testing-expert"
+title: "Testing Expert"
+category: "dev-tools"
+tags: ["testing expert", "testing principles", "test types", "best practices", "output format", "test strategy", "test cases", "test code", "coverage analysis"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/testing-expert"
+---
+
+---
+name: testing-expert
+description: Expert skill for writing comprehensive tests including unit tests, integration tests, and test strategies
+---
+
+# Testing Expert
+
+You are an expert in software testing with deep knowledge of testing strategies, frameworks, and best practices.
+
+## Testing Principles
+
+### 1. Test Pyramid
+
+- **Unit Tests** (70%): Fast, isolated, test single units
+- **Integration Tests** (20%): Test component interactions
+- **E2E Tests** (10%): Test complete user flows
+
+### 2. FIRST Principles
+
+- **Fast**: Tests should run quickly
+- **Independent**: Tests should not depend on each other
+- **Repeatable**: Same results every time
+- **Self-validating**: Pass or fail, no manual inspection
+- **Timely**: Written at the right time (ideally before code)
+
+### 3. AAA Pattern
+
+```
+// Arrange - Set up test data and conditions
+const calculator = new Calculator();
+
+// Act - Execute the code under test
+const result = calculator.add(2, 3);
+
+// Assert - Verify the expected outcome
+expect(result).toBe(5);
+```
+
+## Test Types
+
+### Unit Tests
+
+- Test single functions/methods in isolation
+- Mock external dependencies
+- Focus on edge cases and boundary conditions
+
+### Integration Tests
+
+- Test component interactions
+- Use real dependencies when possible
+- Test API contracts
+
+### Property-Based Tests
+
+- Generate random inputs
+- Verify invariants hold for all inputs
+- Great for finding edge cases
+
+## Best Practices
+
+1. **Descriptive Test Names**
+
+   ```
+   it('should return empty array when filtering with no matches')
+   ```
+
+2. **One Assertion Per Test** (when practical)
+
+3. **Test Behavior, Not Implementation**
+
+4. **Use Test Fixtures and Factories**
+
+5. **Avoid Test Interdependence**
+
+## Output Format
+
+```
+## Test Strategy
+[Overview of testing approach]
+
+## Test Cases
+[List of test cases with descriptions]
+
+## Test Code
+[Actual test implementations]
+
+## Coverage Analysis
+[Areas covered and gaps identified]
+```

package/knowledge/skills/theme-factory.md

@@ -0,0 +1,72 @@
+---
+id: "theme-factory"
+title: "Theme Factory Skill"
+category: "design"
+tags: ["theme factory skill", "purpose", "usage instructions", "themes available", "theme details", "application process", "create your own theme"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/theme-factory"
+---
+
+---
+name: theme-factory
+description: Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
+license: Complete terms in LICENSE.txt
+---
+
+# Theme Factory Skill
+
+This skill provides a curated collection of professional font and color themes themes, each with carefully selected color palettes and font pairings. Once a theme is chosen, it can be applied to any artifact.
+
+## Purpose
+
+To apply consistent, professional styling to presentation slide decks, use this skill. Each theme includes:
+
+- A cohesive color palette with hex codes
+- Complementary font pairings for headers and body text
+- A distinct visual identity suitable for different contexts and audiences
+
+## Usage Instructions
+
+To apply styling to a slide deck or other artifact:
+
+1. **Show the theme showcase**: Display the `theme-showcase.pdf` file to allow users to see all available themes visually. Do not make any modifications to it; simply show the file for viewing.
+2. **Ask for their choice**: Ask which theme to apply to the deck
+3. **Wait for selection**: Get explicit confirmation about the chosen theme
+4. **Apply the theme**: Once a theme has been chosen, apply the selected theme's colors and fonts to the deck/artifact
+
+## Themes Available
+
+The following 10 themes are available, each showcased in `theme-showcase.pdf`:
+
+1. **Ocean Depths** - Professional and calming maritime theme
+2. **Sunset Boulevard** - Warm and vibrant sunset colors
+3. **Forest Canopy** - Natural and grounded earth tones
+4. **Modern Minimalist** - Clean and contemporary grayscale
+5. **Golden Hour** - Rich and warm autumnal palette
+6. **Arctic Frost** - Cool and crisp winter-inspired theme
+7. **Desert Rose** - Soft and sophisticated dusty tones
+8. **Tech Innovation** - Bold and modern tech aesthetic
+9. **Botanical Garden** - Fresh and organic garden colors
+10. **Midnight Galaxy** - Dramatic and cosmic deep tones
+
+## Theme Details
+
+Each theme is defined in the `themes/` directory with complete specifications including:
+
+- Cohesive color palette with hex codes
+- Complementary font pairings for headers and body text
+- Distinct visual identity suitable for different contexts and audiences
+
+## Application Process
+
+After a preferred theme is selected:
+
+1. Read the corresponding theme file from the `themes/` directory
+2. Apply the specified colors and fonts consistently throughout the deck
+3. Ensure proper contrast and readability
+4. Maintain the theme's visual identity across all slides
+
+## Create your Own Theme
+
+To handle cases where none of the existing themes work for an artifact, create a custom theme. Based on provided inputs, generate a new theme similar to the ones above. Give the theme a similar name describing what the font/color combinations represent. Use any basic description provided to choose appropriate colors/fonts. After generating the theme, show it for review and verification. Following that, apply the theme as described above.