claude-code-workflow 6.3.53 → 7.0.0

package/.claude/skills/project-analyze/specs/writing-style.md

@@ -1,152 +0,0 @@
-# 写作风格规范
-
-## 核心原则
-
-**段落式描述，层层递进，禁止清单罗列。**
-
-## 禁止的写作模式
-
-```markdown
-<!-- 禁止：清单罗列 -->
-### 模块列表
-- 用户模块：处理用户相关功能
-- 订单模块：处理订单相关功能
-- 支付模块：处理支付相关功能
-
-### 依赖关系
-| 模块 | 依赖 | 说明 |
-|------|------|------|
-| A | B | xxx |
-```
-
-## 推荐的写作模式
-
-```markdown
-<!-- 推荐：段落式描述 -->
-### 模块架构设计
-
-系统采用分层模块化架构，核心业务逻辑围绕用户、订单、支付三大领域展开。
-用户模块作为系统的入口层，承担身份认证与权限管理职责，为下游模块提供
-统一的用户上下文。订单模块位于业务核心层，依赖用户模块获取会话信息，
-并协调支付模块完成交易闭环。
-
-值得注意的是，支付模块采用策略模式实现多渠道支付，通过接口抽象与
-具体支付网关解耦。这一设计使得新增支付渠道时，仅需实现相应策略类，
-无需修改核心订单逻辑，体现了开闭原则的应用。
-
-从依赖方向分析，系统呈现清晰的单向依赖：表现层依赖业务层，业务层
-依赖数据层，未发现循环依赖。这一架构特征确保了模块的独立可测试性，
-同时为后续微服务拆分奠定了基础。
-```
-
-## 写作策略
-
-### 策略一：主语转换
-
-将主语从开发者视角转移到系统/代码本身：
-
-| 禁止 | 推荐 |
-|------|------|
-| 我们设计了... | 系统采用... |
-| 开发者实现了... | 该模块通过... |
-| 代码中使用了... | 架构设计体现了... |
-
-### 策略二：逻辑连接
-
-使用连接词确保段落递进：
-
-- **承接**：此外、进一步、在此基础上
-- **转折**：然而、值得注意的是、不同于
-- **因果**：因此、这一设计使得、由此可见
-- **总结**：综上所述、从整体来看、概言之
-
-### 策略三：深度阐释
-
-每个技术点需包含：
-1. **是什么**：客观描述技术实现
-2. **为什么**：阐释设计意图和考量
-3. **影响**：说明对系统的影响和价值
-
-```markdown
-<!-- 示例 -->
-系统采用依赖注入模式管理组件生命周期（是什么）。这一选择源于
-对可测试性和松耦合的追求（为什么）。通过将依赖关系外置于
-配置层，各模块可独立进行单元测试，同时为运行时替换实现
-提供了可能（影响）。
-```
-
-## 章节模板
-
-### 架构概述（段落式）
-
-```markdown
-## 系统架构概述
-
-{项目名称}采用{架构模式}架构，整体设计围绕{核心理念}展开。
-从宏观视角审视，系统可划分为{N}个主要层次，各层职责明确，
-边界清晰。
-
-{表现层/入口层}作为系统与外部交互的唯一入口，承担请求解析、
-参数校验、响应封装等职责。该层通过{框架/技术}实现，遵循
-{设计原则}，确保接口的一致性与可维护性。
-
-{业务层}是系统的核心所在，封装了全部业务逻辑。该层采用
-{模式/策略}组织代码，将复杂业务拆解为{N}个领域模块。
-值得注意的是，{关键设计决策}体现了对{质量属性}的重视。
-
-{数据层}负责持久化与数据访问，通过{技术/框架}实现。
-该层与业务层通过{接口/抽象}解耦，使得数据源的替换
-不影响上层逻辑，体现了依赖倒置原则的应用。
-```
-
-### 设计模式分析（段落式）
-
-```markdown
-## 设计模式应用
-
-代码库中可识别出{模式1}、{模式2}等设计模式的应用，
-这些模式的选择与系统的{核心需求}密切相关。
-
-{模式1}主要应用于{场景/模块}。具体实现位于
-`{文件路径}`，通过{实现方式}达成{目标}。
-这一模式的引入有效解决了{问题}，使得{效果}。
-
-在{另一场景}中，系统采用{模式2}应对{挑战}。
-不同于{模式1}的{特点}，{模式2}更侧重于{关注点}。
-从`{文件路径}`的实现可以看出，设计者通过
-{具体实现}实现了{目标}。
-
-综合来看，模式的选择体现了对{原则}的遵循，
-为系统的{质量属性}提供了有力支撑。
-```
-
-### 算法流程分析（段落式）
-
-```markdown
-## 核心算法设计
-
-{算法名称}是系统处理{业务场景}的核心逻辑，
-其实现位于`{文件路径}`。
-
-从算法流程来看，整体可分为{N}个阶段。首先，
-{第一阶段描述}，这一步骤的目的在于{目的}。
-随后，算法进入{第二阶段}，通过{方法}实现{目标}。
-最终，{结果处理}完成整个处理流程。
-
-在复杂度方面，该算法的时间复杂度为{O(x)}，
-空间复杂度为{O(y)}。这一复杂度特征源于
-{原因}，在{数据规模}场景下表现良好。
-
-值得关注的是，{算法名称}采用了{优化策略}，
-相较于朴素实现，{具体优化点}。这一设计决策
-使得{性能提升/效果}。
-```
-
-## 质量检查清单
-
-- [ ] 无清单罗列（禁止 `-` 或 `|` 表格作为主体内容）
-- [ ] 段落完整（每段 3-5 句，逻辑闭环）
-- [ ] 逻辑递进（有连接词串联）
-- [ ] 客观表达（无"我们"、"开发者"等主观主语）
-- [ ] 深度阐释（包含是什么/为什么/影响）
-- [ ] 代码引用（关键点附文件路径）

package/.claude/skills/prompt-enhancer/SKILL.md

@@ -1,124 +0,0 @@
----
-name: Prompt Enhancer
-description: Transform vague prompts into actionable specs using intelligent analysis and session memory. Use when user input contains -e or --enhance flag.
-allowed-tools: (none)
----
-
-# Prompt Enhancer
-
-**Transform**: Vague intent → Structured specification (Memory-based, Direct Output)
-
-**Languages**: English + Chinese (中英文语义识别)
-
-## Process (Internal → Direct Output)
-
-**Internal Analysis**: Intelligently extract session context, identify tech stack, and structure into actionable format.
-
-**Output**: Direct structured prompt (no intermediate steps shown)
-
-## Output Format
-
-**Dynamic Structure**: Adapt fields based on task type and context needs. Not all fields are required.
-
-**Core Fields** (always present):
-- **INTENT**: One-sentence technical goal
-- **ACTION**: Concrete steps with technical details
-
-**Optional Fields** (include when relevant):
-- **TECH STACK**: Relevant technologies (when tech-specific)
-- **CONTEXT**: Session memory findings (when context matters)
-- **ATTENTION**: Critical constraints (when risks/requirements exist)
-- **SCOPE**: Affected modules/files (for multi-module tasks)
-- **METRICS**: Success criteria (for optimization/performance tasks)
-- **DEPENDENCIES**: Related components (for integration tasks)
-
-**Example (Simple Task)**:
-```
-📋 ENHANCED PROMPT
-
-INTENT: Fix authentication token validation in JWT middleware
-
-ACTION:
-1. Review token expiration logic in auth middleware
-2. Add proper error handling for expired tokens
-3. Test with valid/expired/malformed tokens
-```
-
-**Example (Complex Task)**:
-```
-📋 ENHANCED PROMPT
-
-INTENT: Optimize API performance with caching and database indexing
-
-TECH STACK:
-- Redis: Response caching
-- PostgreSQL: Query optimization
-
-CONTEXT:
-- API response times >2s mentioned in previous conversation
-- PostgreSQL slow query logs show N+1 problems
-
-ACTION:
-1. Profile endpoints to identify slow queries
-2. Add PostgreSQL indexes on frequently queried columns
-3. Implement Redis caching for read-heavy endpoints
-4. Add cache invalidation on data updates
-
-METRICS:
-- Target: <500ms API response time
-- Cache hit ratio: >80%
-
-ATTENTION:
-- Maintain backward compatibility with existing API contracts
-- Handle cache invalidation correctly to avoid stale data
-```
-## Workflow
-
-```
-Trigger (-e/--enhance) → Internal Analysis → Dynamic Output
-         ↓                       ↓                  ↓
-   User Input           Assess Task Type      Select Fields
-                    Extract Memory Context    Structure Prompt
-```
-
-1. **Detect**: User input contains `-e` or `--enhance`
-2. **Analyze**:
-   - Determine task type (fix/optimize/implement/refactor)
-   - Extract relevant session context
-   - Identify tech stack and constraints
-3. **Structure**:
-   - Always include: INTENT + ACTION
-   - Conditionally add: TECH STACK, CONTEXT, ATTENTION, METRICS, etc.
-4. **Output**: Present dynamically structured prompt
-
-## Enhancement Guidelines (Internal)
-
-**Always Include**:
-- Clear, actionable INTENT
-- Concrete ACTION steps with technical details
-
-**Add When Relevant**:
-- TECH STACK: Task involves specific technologies
-- CONTEXT: Session memory provides useful background
-- ATTENTION: Security/compatibility/performance concerns exist
-- SCOPE: Multi-module or cross-component changes
-- METRICS: Performance/optimization goals need measurement
-- DEPENDENCIES: Integration points matter
-
-**Quality Checks**:
-- Make vague intent explicit
-- Resolve ambiguous references
-- Add testing/validation steps
-- Include constraints from memory
-
-## Best Practices
-
-- ✅ Trigger only on `-e`/`--enhance` flags
-- ✅ Use **dynamic field selection** based on task type
-- ✅ Extract **memory context ONLY** (no file reading)
-- ✅ Always include INTENT + ACTION as core fields
-- ✅ Add optional fields only when relevant to task
-- ✅ Direct output (no intermediate steps shown)
-- ❌ NO tool calls
-- ❌ NO file operations (Bash, Read, Glob, Grep)
-- ❌ NO fixed template - adapt to task needs

package/.claude/skills/software-manual/SKILL.md

@@ -1,184 +0,0 @@
----
-name: software-manual
-description: Generate interactive TiddlyWiki-style HTML software manuals with screenshots, API docs, and multi-level code examples. Use when creating user guides, software documentation, or API references. Triggers on "software manual", "user guide", "generate manual", "create docs".
-allowed-tools: Task, AskUserQuestion, Read, Bash, Glob, Grep, Write, mcp__chrome__*
----
-
-# Software Manual Skill
-
-Generate comprehensive, interactive software manuals in TiddlyWiki-style single-file HTML format.
-
-## Architecture Overview
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  Context-Optimized Architecture                                  │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                  │
-│  Phase 1: Requirements      → manual-config.json                │
-│           ↓                                                      │
-│  Phase 2: Exploration       → exploration-*.json                │
-│           ↓                                                      │
-│  Phase 3: Parallel Agents   → sections/section-*.md             │
-│           ↓ (6 Agents)                                          │
-│  Phase 3.5: Consolidation   → consolidation-summary.md          │
-│           ↓                                                      │
-│  Phase 4: Screenshot        → screenshots/*.png                 │
-│           Capture              (via Chrome MCP)                 │
-│           ↓                                                      │
-│  Phase 5: HTML Assembly     → {name}-使用手册.html              │
-│           ↓                                                      │
-│  Phase 6: Refinement        → iterations/                       │
-│                                                                  │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## Key Design Principles
-
-1. **主 Agent 编排，子 Agent 执行**: 所有繁重计算委托给 `universal-executor` 子 Agent
-2. **Brief Returns**: Agents return path + summary, not full content (avoid context overflow)
-3. **System Agents**: 使用 `cli-explore-agent` (探索) 和 `universal-executor` (执行)
-4. **成熟库内嵌**: marked.js (MD 解析) + highlight.js (语法高亮)，无 CDN 依赖
-5. **Single-File HTML**: TiddlyWiki-style interactive document with embedded resources
-6. **动态标签**: 根据实际章节自动生成导航标签
-
-## Execution Flow
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  Phase 1: Requirements Discovery (主 Agent)                     │
-│  → AskUserQuestion: 收集软件类型、目标用户、文档范围             │
-│  → Output: manual-config.json                                   │
-├─────────────────────────────────────────────────────────────────┤
-│  Phase 2: Project Exploration (cli-explore-agent × N)           │
-│  → 并行探索: architecture, ui-routes, api-endpoints, config     │
-│  → Output: exploration-*.json                                   │
-├─────────────────────────────────────────────────────────────────┤
-│  Phase 2.5: API Extraction (extract_apis.py)                    │
-│  → 自动提取: FastAPI/TypeDoc/pdoc                                │
-│  → Output: api-docs/{backend,frontend,modules}/*.md             │
-├─────────────────────────────────────────────────────────────────┤
-│  Phase 3: Parallel Analysis (universal-executor × 6)            │
-│  → 6 个子 Agent 并行: overview, ui-guide, api-docs, config,     │
-│    troubleshooting, code-examples                               │
-│  → Output: sections/section-*.md                                │
-├─────────────────────────────────────────────────────────────────┤
-│  Phase 3.5: Consolidation (universal-executor)                  │
-│  → 质量检查: 一致性、交叉引用、截图标记                          │
-│  → Output: consolidation-summary.md, screenshots-list.json      │
-├─────────────────────────────────────────────────────────────────┤
-│  Phase 4: Screenshot Capture (universal-executor + Chrome MCP)  │
-│  → 批量截图: 调用 mcp__chrome__screenshot                        │
-│  → Output: screenshots/*.png + manifest.json                    │
-├─────────────────────────────────────────────────────────────────┤
-│  Phase 5: HTML Assembly (universal-executor)                    │
-│  → 组装 HTML: MD→tiddlers, 嵌入 CSS/JS/图片                     │
-│  → Output: {name}-使用手册.html                                  │
-├─────────────────────────────────────────────────────────────────┤
-│  Phase 6: Iterative Refinement (主 Agent)                       │
-│  → 预览 + 用户反馈 + 迭代修复                                    │
-│  → Output: iterations/v*.html                                   │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## Agent Configuration
-
-| Agent | Role | Output File | Focus Areas |
-|-------|------|-------------|-------------|
-| overview | Product Manager | section-overview.md | Product intro, features, quick start |
-| ui-guide | UX Expert | section-ui-guide.md | UI operations, step-by-step guides |
-| api-docs | API Architect | section-api-reference.md | REST API, Frontend API |
-| config | DevOps Engineer | section-configuration.md | Env vars, deployment, settings |
-| troubleshooting | Support Engineer | section-troubleshooting.md | FAQs, error codes, solutions |
-| code-examples | Developer Advocate | section-examples.md | Beginner/Intermediate/Advanced examples |
-
-## Agent Return Format
-
-```typescript
-interface ManualAgentReturn {
-  status: "completed" | "partial" | "failed";
-  output_file: string;
-  summary: string;                    // Max 50 chars
-  screenshots_needed: Array<{
-    id: string;                       // e.g., "ss-login-form"
-    url: string;                      // Relative or absolute URL
-    description: string;              // "Login form interface"
-    selector?: string;                // CSS selector for partial screenshot
-    wait_for?: string;                // Element to wait for
-  }>;
-  cross_references: string[];         // Other sections referenced
-  difficulty_level: "beginner" | "intermediate" | "advanced";
-}
-```
-
-## HTML Features (TiddlyWiki-style)
-
-1. **Search**: Full-text search with result highlighting
-2. **Collapse/Expand**: Per-section collapsible content
-3. **Tag Navigation**: Filter by category tags
-4. **Theme Toggle**: Light/Dark mode with localStorage persistence
-5. **Single File**: All CSS/JS/images embedded as Base64
-6. **Offline**: Works without internet connection
-7. **Print-friendly**: Optimized print stylesheet
-
-## Directory Setup
-
-```javascript
-// Generate timestamp directory name
-const timestamp = new Date().toISOString().slice(0,19).replace(/[-:T]/g, '');
-const dir = `.workflow/.scratchpad/manual-${timestamp}`;
-
-// Windows
-Bash(`mkdir "${dir}\\sections" && mkdir "${dir}\\screenshots" && mkdir "${dir}\\api-docs" && mkdir "${dir}\\iterations"`);
-```
-
-## Output Structure
-
-```
-.workflow/.scratchpad/manual-{timestamp}/
-├── manual-config.json              # Phase 1
-├── exploration/                    # Phase 2
-│   ├── exploration-architecture.json
-│   ├── exploration-ui-routes.json
-│   └── exploration-api-endpoints.json
-├── sections/                       # Phase 3
-│   ├── section-overview.md
-│   ├── section-ui-guide.md
-│   ├── section-api-reference.md
-│   ├── section-configuration.md
-│   ├── section-troubleshooting.md
-│   └── section-examples.md
-├── consolidation-summary.md        # Phase 3.5
-├── api-docs/                       # API documentation
-│   ├── frontend/                   # TypeDoc output
-│   └── backend/                    # Swagger/OpenAPI output
-├── screenshots/                    # Phase 4
-│   ├── ss-*.png
-│   └── screenshots-manifest.json
-├── iterations/                     # Phase 6
-│   ├── v1.html
-│   └── v2.html
-└── {软件名}-使用手册.html           # Final Output
-```
-
-## Reference Documents
-
-| Document | Purpose |
-|----------|---------|
-| [phases/01-requirements-discovery.md](phases/01-requirements-discovery.md) | 用户配置收集 |
-| [phases/02-project-exploration.md](phases/02-project-exploration.md) | 项目类型检测 |
-| [phases/02.5-api-extraction.md](phases/02.5-api-extraction.md) | API 自动提取 |
-| [phases/03-parallel-analysis.md](phases/03-parallel-analysis.md) | 6 Agent 并行分析 |
-| [phases/03.5-consolidation.md](phases/03.5-consolidation.md) | 整合与质量检查 |
-| [phases/04-screenshot-capture.md](phases/04-screenshot-capture.md) | Chrome MCP 截图 |
-| [phases/05-html-assembly.md](phases/05-html-assembly.md) | HTML 组装 |
-| [phases/06-iterative-refinement.md](phases/06-iterative-refinement.md) | 迭代优化 |
-| [specs/quality-standards.md](specs/quality-standards.md) | 质量标准 |
-| [specs/writing-style.md](specs/writing-style.md) | 写作风格 |
-| [templates/tiddlywiki-shell.html](templates/tiddlywiki-shell.html) | HTML 模板 |
-| [templates/css/wiki-base.css](templates/css/wiki-base.css) | 基础样式 |
-| [templates/css/wiki-dark.css](templates/css/wiki-dark.css) | 暗色主题 |
-| [scripts/bundle-libraries.md](scripts/bundle-libraries.md) | 库文件打包 |
-| [scripts/api-extractor.md](scripts/api-extractor.md) | API 提取说明 |
-| [scripts/extract_apis.py](scripts/extract_apis.py) | API 提取脚本 |
-| [scripts/screenshot-helper.md](scripts/screenshot-helper.md) | 截图辅助 |

package/.claude/skills/software-manual/phases/01-requirements-discovery.md

@@ -1,162 +0,0 @@
-# Phase 1: Requirements Discovery
-
-Collect user requirements and generate configuration for the manual generation process.
-
-## Objective
-
-Gather essential information about the software project to customize the manual generation:
-- Software type and characteristics
-- Target user audience
-- Documentation scope and depth
-- Special requirements
-
-## Execution Steps
-
-### Step 1: Software Information Collection
-
-Use `AskUserQuestion` to collect:
-
-```javascript
-AskUserQuestion({
-  questions: [
-    {
-      question: "What type of software is this project?",
-      header: "Software Type",
-      options: [
-        { label: "Web Application", description: "Frontend + Backend web app with UI" },
-        { label: "CLI Tool", description: "Command-line interface tool" },
-        { label: "SDK/Library", description: "Developer library or SDK" },
-        { label: "Desktop App", description: "Desktop application (Electron, etc.)" }
-      ],
-      multiSelect: false
-    },
-    {
-      question: "Who is the target audience for this manual?",
-      header: "Target Users",
-      options: [
-        { label: "End Users", description: "Non-technical users who use the product" },
-        { label: "Developers", description: "Developers integrating or extending the product" },
-        { label: "Administrators", description: "System admins deploying and maintaining" },
-        { label: "All Audiences", description: "Mixed audience with different sections" }
-      ],
-      multiSelect: false
-    },
-    {
-      question: "What documentation scope do you need?",
-      header: "Doc Scope",
-      options: [
-        { label: "Quick Start", description: "Essential getting started guide only" },
-        { label: "User Guide", description: "Complete user-facing documentation" },
-        { label: "API Reference", description: "Focus on API documentation" },
-        { label: "Comprehensive", description: "Full documentation including all sections" }
-      ],
-      multiSelect: false
-    },
-    {
-      question: "What difficulty levels should code examples cover?",
-      header: "Example Levels",
-      options: [
-        { label: "Beginner Only", description: "Simple, basic examples" },
-        { label: "Beginner + Intermediate", description: "Basic to moderate complexity" },
-        { label: "All Levels", description: "Beginner, Intermediate, and Advanced" }
-      ],
-      multiSelect: false
-    }
-  ]
-});
-```
-
-### Step 2: Auto-Detection (Supplement)
-
-Automatically detect project characteristics:
-
-```javascript
-// Detect from package.json
-const packageJson = Read('package.json');
-const softwareName = packageJson.name;
-const version = packageJson.version;
-const description = packageJson.description;
-
-// Detect tech stack
-const hasReact = packageJson.dependencies?.react;
-const hasVue = packageJson.dependencies?.vue;
-const hasExpress = packageJson.dependencies?.express;
-const hasNestJS = packageJson.dependencies?.['@nestjs/core'];
-
-// Detect CLI
-const hasBin = !!packageJson.bin;
-
-// Detect UI
-const hasPages = Glob('src/pages/**/*').length > 0 || Glob('pages/**/*').length > 0;
-const hasRoutes = Glob('**/routes.*').length > 0;
-```
-
-### Step 3: Generate Configuration
-
-Create `manual-config.json`:
-
-```json
-{
-  "software": {
-    "name": "{{detected or user input}}",
-    "version": "{{from package.json}}",
-    "description": "{{from package.json}}",
-    "type": "{{web|cli|sdk|desktop}}"
-  },
-  "target_audience": "{{end_users|developers|admins|all}}",
-  "doc_scope": "{{quick_start|user_guide|api_reference|comprehensive}}",
-  "example_levels": ["beginner", "intermediate", "advanced"],
-  "tech_stack": {
-    "frontend": "{{react|vue|angular|vanilla}}",
-    "backend": "{{express|nestjs|fastify|none}}",
-    "language": "{{typescript|javascript}}",
-    "ui_framework": "{{tailwind|mui|antd|none}}"
-  },
-  "features": {
-    "has_ui": true,
-    "has_api": true,
-    "has_cli": false,
-    "has_config": true
-  },
-  "agents_to_run": [
-    "overview",
-    "ui-guide",
-    "api-docs",
-    "config",
-    "troubleshooting",
-    "code-examples"
-  ],
-  "screenshot_config": {
-    "enabled": true,
-    "dev_command": "npm run dev",
-    "dev_url": "http://localhost:3000",
-    "wait_timeout": 5000
-  },
-  "output": {
-    "filename": "{{name}}-使用手册.html",
-    "theme": "light",
-    "language": "zh-CN"
-  },
-  "timestamp": "{{ISO8601}}"
-}
-```
-
-## Agent Selection Logic
-
-Based on `doc_scope`, select agents to run:
-
-| Scope | Agents |
-|-------|--------|
-| quick_start | overview |
-| user_guide | overview, ui-guide, config, troubleshooting |
-| api_reference | overview, api-docs, code-examples |
-| comprehensive | ALL 6 agents |
-
-## Output
-
-- **File**: `manual-config.json`
-- **Location**: `.workflow/.scratchpad/manual-{timestamp}/`
-
-## Next Phase
-
-Proceed to [Phase 2: Project Exploration](02-project-exploration.md) with the generated configuration.