ecc_infisense 0.0.1 → 0.1.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "ecc_infisense",
-  "version": "0.0.1",
+  "version": "0.1.0",
   "description": "Claude Code plugin for C/C++ development — component management, release workflow, and coding conventions",
   "author": "ECC InfiSense Contributors",
   "languages": [

package/README.md

@@ -13,9 +13,9 @@ C++ 编码规范。
 | 能力 | 原生 Claude Code | 搭配 ECC InfiSense |
 |------|-------------------|------------------------|
 | 构建系统感知 | 通用文件编辑 | 自动检测 CMake/Make/Meson/Bazel，了解构建命令 |
-| 规则 | 通用建议 | 4 条规则覆盖智能体委派、开发工作流、Git 规范、钩子开发 |
+| 规则 | 通用建议 | 13 条规则覆盖智能体委派、开发工作流、Git 规范、钩子开发、组件编写、文档同步、C/C++ 编码风格/内存安全/错误处理/现代特性 |
 | 会话连续性 | 无持久化 | 会话钩子在压缩 (Compaction) 和重启时自动保存/恢复上下文 |
-| 组件管理 | 无 | `/component-creator` 创建、分析、重命名插件组件 |
+| 组件管理 | 无 | `/component` 创建、分析、重命名插件组件 |
 | 版本发布 | 手动操作 | `/release` 自动检测变更、提交、发布到 npm |
 
 ## 功能概览
@@ -23,10 +23,10 @@ C++ 编码规范。
 | 组件 | 数量 | 说明 |
 |------|------|------|
 | 智能体 (Agent) | 3 | 组件设计、插件索引和发布管理的专用子智能体 |
-| 技能 (Skill) | 2 | 组件模板和发布工作流的知识库 |
-| 命令 (Command) | 3 | 组件创建、帮助索引和版本发布的斜杠命令 |
-| 钩子匹配器 (Hook Matcher) | 4 | 覆盖 PreToolUse、PreCompact、SessionStart 和 SessionEnd 事件 |
-| 规则 (Rule) | 4 | 位于 `common/` 目录下的常驻准则 |
+| 技能 (Skill) | 4 | 组件模板、发布工作流、C 规范、C++ 规范的知识库 |
+| 命令 (Command) | 4 | 组件管理、插件概览、版本发布和质量评分的斜杠命令 |
+| 钩子匹配器 (Hook Matcher) | 6 | 覆盖 PreToolUse、PostToolUse(x2)、PreCompact、SessionStart 和 SessionEnd 事件 |
+| 规则 (Rule) | 13 | 位于 `common/`(6)、`c/`(3)、`cpp/`(4) 目录下的常驻准则 |
 | 指南 (Guide) | 1 | ECC InfiSense 使用指南 |
 
 ## 安装
@@ -56,8 +56,8 @@ cd ecc-infisense
 
 | 组件 | 安装路径 | 数量 |
 |------|---------|------|
-| 规则 (Rules) | `~/.claude/rules/common/` | 4 |
-| 命令 (Commands) | `~/.claude/commands/` | 3 |
+| 规则 (Rules) | `~/.claude/rules/common/` | 6 |
+| 命令 (Commands) | `~/.claude/commands/` | 4 |
 | 智能体 (Agents) | `~/.claude/agents/` | 3 |
 | 技能 (Skills) | `~/.claude/skills/` | 2 |
 | 钩子 (Hooks) | `~/.claude/settings.json` (合并) | 4 |
@@ -67,7 +67,7 @@ cd ecc-infisense
 安装完成后，在 Claude Code 会话中运行：
 
 ```
-> /infi-ecc-helper
+> /infi-overview
 ```
 
 如果插件已激活，将显示所有已安装组件的分类索引。
@@ -92,10 +92,10 @@ cd /path/to/your/cpp/project
 claude
 
 # 查看所有可用命令
-> /infi-ecc-helper
+> /infi-overview
 
 # 创建新组件
-> /infi-component-creator create
+> /infi-component create
 
 # 提交变更
 > /infi-release git-update
@@ -103,10 +103,10 @@ claude
 
 ## 使用示例
 
-### /infi-ecc-helper -- 查看插件概览
+### /infi-overview -- 查看插件概览
 
 ```
-> /infi-ecc-helper
+> /infi-overview
 
 动态扫描插件目录，生成分类索引:
   - 按 category (plugin/cpp) 分组
@@ -114,10 +114,10 @@ claude
   - 包含快速上手工作流
 ```
 
-### /infi-component-creator -- 组件管理
+### /infi-component -- 组件管理
 
 ```
-> /infi-component-creator
+> /infi-component
 
 三种模式:
   1. create  — 从功能描述生成命令/智能体/技能
@@ -136,22 +136,36 @@ claude
   3. status     — 查看当前版本和未发布变更
 ```
 
+### /infi-quality -- 质量评分
+
+```
+> /infi-quality
+
+四种模式:
+  1. score    — 评分单个组件或全部组件（0-100 多维度）
+  2. compare  — 对比两个组件的重叠度
+  3. report   — 全量评分报告（含汇总和改进建议）
+  4. optimize — 评分后自动修改文件，修复弱项维度
+```
+
 ## 架构
 
 ```
 ecc-infisense/
   agents/                    # 3 个专用插件子智能体
-  commands/                  # 3 个斜杠命令
+  commands/                  # 4 个斜杠命令
   docs/                      # 指南文档
     GUIDE.md                 # ECC InfiSense 使用指南
   hooks/                     # 事件驱动的自动化
   rules/                     # 常驻准则
-    common/                  # 通用规则（4 个文件）
+    common/                  # 通用规则（6 个文件）
+    c/                       # C 语言规则
+    cpp/                     # C++ 语言规则
   scripts/                   # Node.js 工具脚本
     ci/                      # CI 验证脚本
     hooks/                   # 钩子运行器实现
     lib/                     # 共享库代码
-  skills/                    # 2 个工作流技能
+  skills/                    # 4 个工作流技能
   tests/                     # 测试套件
   .claude-plugin/            # 插件元数据
     plugin.json
@@ -189,14 +203,17 @@ category: plugin
 |------|------|
 | `component-templates` | ECC InfiSense 组件创建模板与规范（agent、skill、command、rule） |
 | `release-workflow` | 发布管理约定：提交规范、变更日志格式、版本管理和安全检查 |
+| `c-conventions` | C 语言编码规范知识库：命名模式、格式示例、内存安全惯用法、错误处理模式 |
+| `cpp-conventions` | C++ 编码规范知识库：命名模式、RAII 惯用法、错误处理模式、现代 C++ 用法 |
 
 ## 命令 (Command)
 
 | 命令 | 说明 |
 |------|------|
-| `/component-creator` | 创建新组件，分析已有组件的重叠、缺口，或重命名组件 |
-| `/ecc-helper` | 查看 ECC InfiSense 插件概览：所有命令、智能体和技能分类索引 |
+| `/component` | 创建新组件，分析已有组件的重叠、缺口，或重命名组件 |
+| `/overview` | 查看 ECC InfiSense 插件概览：所有命令、智能体和技能分类索引 |
 | `/release` | Git 提交 + npm 发布 + 版本管理 |
+| `/quality` | 组件质量评分、对比、报告和自动优化 |
 
 ## 钩子系统
 
@@ -205,6 +222,8 @@ category: plugin
 | 事件 | 匹配器 | 钩子脚本 | 用途 |
 |------|--------|----------|------|
 | `PreToolUse` | `Edit\|Write` | `suggest-compact.js` | 上下文过大时建议压缩 |
+| `PostToolUse` | `Edit\|Write` | `doc-sync-reminder.js` | 组件文件修改后提醒同步文档 |
+| `PostToolUse` | `Edit\|Write` | `component-check.js` | 组件文件创建或修改后提醒运行 spec 分析 |
 | `PreCompact` | `*` | `pre-compact.js` | 压缩前保存上下文 |
 | `SessionStart` | `*` | `session-start.js` | 恢复上一次会话上下文 |
 | `SessionEnd` | `*` | `session-end.js` | 保存会话状态 |
@@ -242,14 +261,23 @@ category: plugin
 
 规则是 Claude Code 在每次交互中始终遵循的准则。
 
-### 规则（4 条）
+### 规则（13 条）
 
 | 规则 | 说明 |
 |------|------|
-| `agents` | 智能体委派和职责边界 |
+| `agent-delegation` | 智能体委派和职责边界 |
 | `development-workflow` | 工作流规则 |
 | `git-workflow` | 分支策略和提交规范 |
-| `hooks` | 钩子执行和安全防护 |
+| `hook-authoring` | 钩子执行和安全防护 |
+| `component-authoring` | 组件编写约束和模板引用规范 |
+| `doc-sync` | 组件变更时强制同步文档的准则 |
+| `c/coding-style` | C 语言编码风格（Google C Style） |
+| `c/memory-safety` | C 语言内存安全约束 |
+| `c/error-handling` | C 语言错误处理约束 |
+| `cpp/coding-style` | C++ 编码风格（Google C++ Style） |
+| `cpp/memory-safety` | C++ 内存安全与 RAII 约束 |
+| `cpp/error-handling` | C++ 错误处理约束（禁止异常） |
+| `cpp/modern-cpp` | C++17/20 现代特性使用约束 |
 
 ## 文档
 
@@ -265,11 +293,11 @@ category: plugin
 
 ### 问：如何添加自定义规则？
 
-在 `rules/common/` 中创建一个 Markdown 文件。参照现有规则的格式。
+在 `rules/{common,c,cpp}/` 中创建一个 Markdown 文件。参照现有规则的格式。
 
 ### 问：如何创建新的插件组件？
 
-使用 `/infi-component-creator create` 命令，提供功能描述，插件会自动决定需要
+使用 `/infi-component create` 命令，提供功能描述，插件会自动决定需要
 哪些组件类型（命令/智能体/技能/规则）并生成文件。
 
 ## 开发
@@ -289,6 +317,28 @@ npm test
 5. `scripts/ci/validate-hooks.js` -- 验证钩子配置
 6. `tests/run-all.js` -- 运行功能测试
 
+### 组件质量评分
+
+除结构合规性验证外，还可对组件内容质量进行多维度评分（0-100）：
+
+```bash
+# 评分全部组件
+node scripts/ci/score-components.js --all
+
+# 评分单个文件
+node scripts/ci/score-components.js rules/c/coding-style.md
+
+# 对比两个组件的重叠度
+node scripts/ci/score-components.js --overlap rules/c/coding-style.md rules/cpp/coding-style.md
+
+# 输出 JSON 用于前后对比
+node scripts/ci/score-components.js rules/c/coding-style.md --json > before.json
+```
+
+**Rule 评分维度：** sizing (行数)、density (约束密度)、uniqueness (唯一性)、tone (命令式语气)、structure (结构完整性)
+
+**Skill 评分维度：** sizing (行数)、coverage (规则覆盖率)、examples (正反例)、compilable (代码可编译)、sections (必要章节)
+
 ## 贡献
 
 详细指南请参阅 [CONTRIBUTING.md](CONTRIBUTING.md)。

package/agents/plugin-inspector.md

@@ -81,8 +81,8 @@ For skills, group by domain (quality pipeline, testing, build, design, security,
 ### Quick Start Section
 
 Always include a quick-start section with the most common workflows:
-- 查看概览: `/infi-ecc-helper`
-- 创建组件: `/infi-component-creator create`
+- 查看概览: `/infi-overview`
+- 创建组件: `/infi-component create`
 - 提交变更: `/infi-release git-update`
 - 发布版本: `/infi-release publish minor`
 
@@ -142,8 +142,8 @@ ECC InfiSense — Claude Code C/C++ 开发工具套件
 
 ━━━ 快速上手 ━━━
 
-  查看概览:    /infi-ecc-helper
-  创建组件:    /infi-component-creator create
+  查看概览:    /infi-overview
+  创建组件:    /infi-component create
   提交变更:    /infi-release git-update
   发布版本:    /infi-release publish minor
 

package/commands/{infi-component-creator.md → infi-component.md}

@@ -3,14 +3,14 @@ description: Create new components or analyze existing ones for overlap, gaps, a
 category: plugin
 ---
 
-# Component Creator
+# Component Management
 
 Create new ECC InfiSense components from a feature description, analyze existing components
 for orphans, overlaps, and spec violations, or rename components for clarity.
 
 ## Usage
 
-`/infi-component-creator [create|analyze|rename] [description]`
+`/infi-component [create|analyze|rename] [description]`
 
 If mode is omitted, present an interactive menu using AskUserQuestion:
 

package/commands/{infi-ecc-helper.md → infi-overview.md}

@@ -3,14 +3,14 @@ description: Show ECC InfiSense plugin overview — available commands, agents,
 category: plugin
 ---
 
-# ECC InfiSense Helper
+# Plugin Overview
 
 Display a categorized index of all available ECC InfiSense components by dynamically
 scanning plugin directories. The index is always up-to-date with the actual filesystem.
 
 ## Usage
 
-`/infi-ecc-helper`
+`/infi-overview`
 
 No arguments. Produces a formatted overview of all installed components.
 
@@ -40,5 +40,5 @@ Output the generated index directly to the user. The index includes:
 
 - Agent: `plugin-inspector` — dynamic directory scanning and index generation
 - Skill: `component-templates` — component type definitions and conventions
-- Related: `/infi-component-creator` — create new components
+- Related: `/infi-component` — create new components
 - Related: `/infi-release` — version management and publishing

package/commands/infi-quality.md

@@ -0,0 +1,166 @@
+---
+description: Score, compare, report, and optimize component quality.
+category: plugin
+---
+
+# Quality Scoring & Optimization
+
+Evaluate and improve ECC InfiSense component quality through multi-dimensional
+scoring. Runs `scripts/ci/score-components.js` for scoring, then optionally
+edits files to fix weak dimensions.
+
+## Usage
+
+`/infi-quality [score|compare|report|optimize] [args]`
+
+If mode is omitted, present an interactive menu using AskUserQuestion:
+
+```
+Which quality workflow do you want to run?
+
+1. score    — Score a single component or all components
+2. compare  — Compare overlap between two components
+3. report   — Full scoring report with summary and improvement suggestions
+4. optimize — Score then auto-fix weak dimensions in component files
+```
+
+---
+
+## 1. score
+
+Score one or all components on a 0-100 scale across multiple dimensions.
+
+**Single file:**
+
+```
+/infi-quality score rules/c/coding-style.md
+```
+
+Run: `node scripts/ci/score-components.js <file>`
+
+**All components:**
+
+```
+/infi-quality score --all
+```
+
+Run: `node scripts/ci/score-components.js --all`
+
+Display the per-dimension breakdown and overall score. Highlight any dimension
+below 60% of its max as needing improvement.
+
+---
+
+## 2. compare
+
+Compare overlap between two components to decide whether to merge or keep both.
+
+```
+/infi-quality compare rules/c/coding-style.md rules/cpp/coding-style.md
+```
+
+Run: `node scripts/ci/score-components.js --overlap <fileA> <fileB>`
+
+Display the overlap percentage, shared content areas, and a recommendation
+(merge / keep separate / refactor shared content into a skill).
+
+---
+
+## 3. report
+
+Full scoring report across all components with actionable improvement suggestions.
+
+```
+/infi-quality report
+```
+
+Run: `node scripts/ci/score-components.js --all --json`
+
+Parse the JSON output and generate:
+
+1. **Summary table** — component name, overall score, lowest dimension
+2. **Top improvements** — list the 5 lowest-scoring dimensions across all
+   components with specific suggestions
+3. **Comparison with previous run** — if user provides a previous JSON file,
+   show score deltas
+
+---
+
+## 4. optimize
+
+Score a component, then automatically edit it to improve weak dimensions.
+
+**Single file:**
+
+```
+/infi-quality optimize rules/c/coding-style.md
+```
+
+**All components below threshold:**
+
+```
+/infi-quality optimize --all
+/infi-quality optimize --all --threshold 80
+```
+
+Default threshold is 70. Only components scoring below the threshold are optimized.
+
+### Workflow
+
+1. **Score** — run `node scripts/ci/score-components.js <file>` (or `--all --json`)
+2. **Identify weak dimensions** — any dimension below 60% of its max weight
+3. **Plan fixes** — show the user which dimensions will be improved and what
+   changes are planned. Wait for confirmation before editing.
+4. **Edit** — apply targeted fixes to the file using the Edit tool
+5. **Re-score** — run scoring again to verify improvement
+6. **Report delta** — show before/after comparison for each dimension
+
+### Optimization Actions by Dimension
+
+#### Rule dimensions
+
+| Dimension | Trigger | Action |
+|-----------|---------|--------|
+| sizing | < 30 or > 50 lines | Trim redundant lines or split overly terse points into clearer items |
+| density | constraint ratio < 0.3 | Convert explanatory prose into constraint bullet points or table rows; remove filler sentences |
+| uniqueness | duplicate constraints found | Remove constraints that are identical to another rule; rephrase near-duplicates to differentiate |
+| tone | < 50% imperative | Rewrite soft phrasing to imperative: "should" → "必须", "avoid" → "禁止", "prefer" → "优先" |
+| structure | missing elements | Add frontmatter if absent; add cross-reference to corresponding skill; convert lists to tables where appropriate |
+
+#### Skill dimensions
+
+| Dimension | Trigger | Action |
+|-----------|---------|--------|
+| sizing | < 100 or > 600 lines | Expand thin sections with more examples, or extract verbose sections into sub-files |
+| coverage | rule keywords missing | Add code examples or explanation paragraphs covering the missing rule keywords |
+| examples | Good without Bad | Add a `// Bad` counterpart next to every `// Good` example that lacks one |
+| compilable | syntax errors in code blocks | Fix compilation errors in code blocks (missing includes, typos, invalid syntax) |
+| sections | missing required sections | Add `## Quick Reference`, `## When to Use`, or `## When NOT to Use` sections with appropriate content |
+| token-efficiency | tokens > 3000 | Compress code blocks (merge duplicate includes, combine Good/Bad pairs), trim redundant explanatory text |
+
+### Safety
+
+- Never remove content without showing the user what will be deleted
+- Always show a before/after diff summary before confirming
+- If the user declines a specific optimization, skip it and proceed to the next
+- Run `npm test` after all edits to ensure nothing is broken
+
+---
+
+## Scoring Dimensions
+
+**Rule components:** sizing (line count), density (constraint density),
+uniqueness, tone (imperative voice), structure (completeness)
+
+**Skill components:** sizing (line count), coverage (rule coverage),
+examples (positive/negative), compilable (code compiles), sections (required
+sections), token-efficiency (token cost within limit)
+
+---
+
+## Cross-References
+
+- Script: `scripts/ci/score-components.js` — CLI entry point
+- Library: `scripts/lib/quality-scorer.js` — scoring engine
+- Related: `/infi-component analyze` — structural health check (quality does content scoring)
+- Related: `/infi-overview` — view current plugin overview

package/commands/infi-release.md

@@ -79,5 +79,5 @@ Delegate to `release-executor` agent to display:
 
 - Agent: `release-executor` — executes all three release workflows
 - Skill: `release-workflow` — commit conventions, path-scope mapping, changelog format
-- Related: `/infi-component-creator` — create components before releasing
-- Related: `/infi-ecc-helper` — view current plugin overview
+- Related: `/infi-component` — create components before releasing
+- Related: `/infi-overview` — view current plugin overview

package/hooks/hooks.json

@@ -13,6 +13,28 @@
         "description": "Suggest manual compaction at logical intervals"
       }
     ],
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/hooks/doc-sync-reminder.js\""
+          }
+        ],
+        "description": "Remind to sync CLAUDE.md, README.md, docs/GUIDE.md when component files are modified"
+      },
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/hooks/component-check.js\""
+          }
+        ],
+        "description": "Remind to run /infi-component analyze when component files are created or modified"
+      }
+    ],
     "PreCompact": [
       {
         "matcher": "*",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ecc_infisense",
-  "version": "0.0.1",
+  "version": "0.1.0",
   "description": "Claude Code plugin for C/C++ development — agents, skills, hooks, commands, and rules for component management, release workflow, and C++ coding conventions",
   "keywords": [
     "claude-code",

package/rules/c/coding-style.md

@@ -0,0 +1,48 @@
+---
+paths: "*.c,*.h"
+---
+
+# C Coding Style
+
+For detailed patterns and examples, consult `c-conventions` skill.
+
+基于 Google C Style，适用于所有 C 源文件。
+
+## Naming
+
+| 元素 | 风格 |
+|------|------|
+| 函数 | snake_case |
+| 变量（局部） | snake_case |
+| 全局变量 | g_ 前缀 + snake_case |
+| 静态变量 | s_ 前缀 + snake_case |
+| 宏 / 常量 | UPPER_SNAKE_CASE |
+| 类型（struct/enum/typedef） | snake_case_t 后缀 |
+| 结构体成员 | snake_case，无前缀 |
+
+## Formatting
+
+| 项目 | 规则 |
+|------|------|
+| 缩进 | 2 空格，禁止 Tab |
+| 大括号 | K&R 风格，左大括号同行 |
+| 行宽 | 最大 80 列 |
+| 指针星号 | 靠变量，禁止靠类型 |
+| 函数之间 | 1 个空行 |
+| 运算符两侧 | 必须加空格 |
+
+## Headers
+
+| 项目 | 规则 |
+|------|------|
+| include guard | ifndef 宏（PROJECT_PATH_FILE_H_ 格式），禁止 pragma once |
+| 后缀 | .h |
+| include 顺序 | 自身头文件 → 项目头文件 → 第三方 → 系统头文件 |
+| 每组之间 | 空 1 行 |
+
+## General
+
+- 每个函数不超过 40 行（不含空行和注释），超过必须拆分
+- 函数参数不超过 5 个，超过用结构体封装
+- 禁止 goto
+- 输出参数必须用指针

package/rules/c/error-handling.md

@@ -0,0 +1,33 @@
+---
+paths: "*.c,*.h"
+---
+
+# C Error Handling
+
+For detailed patterns and examples, consult `c-conventions` skill.
+
+C 语言错误处理约束，基于 Google C Style。
+
+## Return Codes
+
+| 约束 | 规则 |
+|------|------|
+| 错误类型 | 优先使用 enum 定义错误码，禁止裸整数 |
+| 成功值 | 成功返回 0 或正值，错误返回负值或特定错误枚举 |
+| 调用方检查 | 调用返回错误码的函数后必须检查返回值 |
+| errno | 仅在调用标准库函数后检查 errno，禁止自定义函数使用 errno |
+
+## Error Propagation
+
+| 约束 | 规则 |
+|------|------|
+| 向上传递 | 内部函数错误必须向上传递，禁止静默吞掉 |
+| 清理路径 | 函数内多个资源获取时，错误后必须按逆序清理已获取资源 |
+| 日志记录 | 错误最终处理点必须记录日志，中间传递层不重复记录 |
+
+## Prohibited
+
+- 禁止忽略函数返回值（除显式标注为无需检查的函数）
+- 禁止使用 setjmp/longjmp 做错误处理
+- 禁止用 assert 处理运行时可能发生的错误，assert 仅用于不变量
+- 禁止在错误路径上泄漏资源

package/rules/c/memory-safety.md

@@ -0,0 +1,34 @@
+---
+paths: "*.c,*.h"
+---
+
+# C Memory Safety
+
+For detailed patterns and examples, consult `c-conventions` skill.
+
+C 语言内存安全约束，基于 Google C Style 和 CERT C。
+
+## Allocation
+
+| 约束 | 规则 |
+|------|------|
+| 返回值检查 | malloc/calloc/realloc 返回值必须检查 NULL |
+| 配对释放 | 每个 malloc 必须有且仅有一个对应的 free |
+| 释放后置空 | free 后必须将指针置为 NULL |
+| realloc 安全 | 必须用临时变量接收 realloc 返回值，失败时保留原指针 |
+
+## Ownership
+
+| 约束 | 规则 |
+|------|------|
+| 单一所有者 | 每块动态内存有且仅有一个所有者负责释放 |
+| 文档化 | 函数返回动态内存时必须在注释中说明调用方需释放 |
+| 数组边界 | 数组访问前必须检查索引范围 |
+| 缓冲区长度 | 字符串操作必须使用带长度参数的版本（strncpy 而非 strcpy） |
+
+## Prohibited
+
+- 禁止使用已释放的指针（use-after-free）
+- 禁止返回局部变量的指针
+- 禁止对栈上对象调用 free
+- 禁止在头文件中定义全局可变状态

package/rules/common/agent-delegation.md

@@ -0,0 +1,35 @@
+# Agent Delegation Guide
+
+For component templates and naming conventions, consult `component-templates` skill.
+
+## When to Delegate
+
+| 场景 | 规则 |
+|------|------|
+| 多文件操作、组件设计、插件分析、发布管理 | 必须委派给对应智能体 |
+| 单文件编辑、上下文充分的简单任务 | 禁止委派，直接执行 |
+
+## Agent Selection
+
+| Agent | 职责 | 使用条件 |
+|-------|------|----------|
+| `@component-designer` | 设计、分析、重命名组件 | 必须用于 create/analyze/rename 操作 |
+| `@plugin-inspector` | 扫描目录，生成分类索引 | 必须用于 `/infi-overview` |
+| `@release-executor` | Git 提交、npm 发布、版本状态 | 必须用于 `/infi-release` |
+
+## Coordination Patterns
+
+| 命令 | 必须委派给 |
+|------|-----------|
+| `/infi-component` | `component-designer` |
+| `/infi-overview` | `plugin-inspector` |
+| `/infi-release` | `release-executor` |
+
+- 顺序工作流：设计组件 → 创建 → 发布，禁止跳过中间步骤
+
+## Best Practices
+
+- 必须在委派时包含文件路径、错误信息或设计约束
+- 必须使用具体描述："分析 agents/ 目录中的孤儿组件"，禁止模糊描述
+- 多智能体工作流中，必须在智能体之间共享结果
+- 智能体输出仅作为起点，必须根据上下文进行验证和调整