From 676ee34cbe228de5962aa0433b8ac2cc3faf5b5f Mon Sep 17 00:00:00 2001 From: Akuma <2374973868@qq.com> Date: Thu, 3 Sep 2026 12:15:57 +0800 Subject: [PATCH 1/3] fix(v2): consolidate bundled Skill assets --- .../fix-issue-534-bundled-skills.md | 7 + .../bundled-skills/brainstorming/SKILL.md | 2 +- .../bundled-skills/brainstorming/SKILL.zh.md | 0 .../brainstorming/metadata.json | 0 .../code-review-and-quality/SKILL.md | 0 .../code-review-and-quality/SKILL.zh.md | 0 .../code-review-and-quality/metadata.json | 0 .../bundled-skills/frontend-design/SKILL.md | 0 .../frontend-design/SKILL.zh.md | 0 .../frontend-design/metadata.json | 0 .../bundled-skills/handoff/SKILL.md | 0 .../bundled-skills/handoff/SKILL.zh.md | 0 .../bundled-skills/handoff/metadata.json | 0 .../bundled-skills/paper-writing/SKILL.md | 0 .../bundled-skills/paper-writing/SKILL.zh.md | 0 .../paper-writing/metadata.json | 0 .../personal-finance-planning/SKILL.md | 0 .../personal-finance-planning/SKILL.zh.md | 0 .../personal-finance-planning/metadata.json | 0 .../refactor-review-knowledge/SKILL.md | 0 .../refactor-review-knowledge/SKILL.zh.md | 0 .../refactor-review-knowledge/metadata.json | 0 .../bundled-skills/skill-creator/SKILL.md | 0 .../bundled-skills/skill-creator/SKILL.zh.md | 0 .../skill-creator/metadata.json | 0 .../systematic-debugging/SKILL.zh.md | 0 .../systematic-debugging/metadata.json | 0 apps/main-2.0/electron.vite.config.ts | 2 + .../scripts/check-source-entrypoints.mjs | 1 - apps/main-2.0/scripts/package-smoke.mjs | 43 + .../engine/main/bridges/mcp-bridge.test.ts | 2 +- .../engine/main/skills/skill-installer.ts | 30 +- .../shared/bundled-skill-library.test.ts | 26 + .../engine/shared/bundled-skill-library.ts | 40 +- .../bundled-skills/brainstorming/SKILL.md | 159 - .../references/visual-companion.md | 5 - .../feishu-tech-diagram/SKILL.md | 79 - .../feishu-tech-diagram/agents/openai.yaml | 4 - .../assets/sample-manifest.json | 402 --- .../assets/samples/01-react-loop.svg | 63 - .../assets/samples/02-plan-and-execute.svg | 79 - .../assets/samples/03-context-assembly.svg | 155 - .../assets/samples/04-memory-architecture.svg | 160 - .../assets/samples/05-rag-agent.svg | 141 - .../assets/samples/06-supervisor-worker.svg | 165 - .../assets/samples/07-router-specialist.svg | 93 - .../assets/samples/08-parallel-fan-in.svg | 99 - .../assets/samples/09-generator-reviewer.svg | 82 - .../assets/samples/10-handoff-human.svg | 113 - .../11-agent-development-lifecycle.svg | 107 - .../assets/samples/12-prompt-development.svg | 92 - .../samples/13-tool-mcp-integration.svg | 184 - .../samples/14-agent-evaluation-loop.svg | 118 - .../samples/15-agent-trace-debugging.svg | 136 - .../16-software-development-lifecycle.svg | 121 - .../samples/17-requirement-to-design.svg | 119 - .../assets/samples/18-tdd-cycle.svg | 67 - .../assets/samples/19-git-pr-review.svg | 125 - .../assets/samples/20-cicd-release.svg | 144 - .../samples/21-layered-architecture.svg | 176 - .../samples/22-monolith-to-microservices.svg | 241 -- .../samples/23-microservice-gateway.svg | 120 - .../assets/samples/24-plugin-architecture.svg | 132 - .../assets/samples/25-agent-platform.svg | 191 - .../samples/26-synchronous-sequence.svg | 99 - .../samples/27-asynchronous-sequence.svg | 133 - .../samples/28-human-agent-swimlane.svg | 132 - .../assets/samples/29-task-state-machine.svg | 101 - .../assets/samples/30-retry-compensation.svg | 141 - .../assets/samples/31-data-pipeline.svg | 163 - .../assets/samples/32-data-lineage.svg | 180 - .../assets/samples/33-er-model.svg | 253 -- .../assets/samples/34-domain-model.svg | 93 - .../assets/samples/35-cache-consistency.svg | 152 - .../assets/samples/36-observability-loop.svg | 145 - .../assets/samples/37-incident-response.svg | 191 - .../assets/samples/38-resilience-control.svg | 112 - .../39-authentication-authorization.svg | 118 - .../40-sensitive-operation-approval.svg | 141 - .../assets/samples/41-learning-roadmap.svg | 128 - .../assets/samples/42-knowledge-mindmap.svg | 160 - .../assets/samples/43-concept-dependency.svg | 100 - .../assets/samples/44-mechanism-breakdown.svg | 114 - .../samples/45-one-picture-overview.svg | 140 - .../samples/46-architecture-evolution.svg | 210 -- .../assets/samples/47-project-milestones.svg | 212 -- .../samples/48-technology-selection.svg | 164 - .../assets/samples/49-capability-map.svg | 202 -- .../samples/50-troubleshooting-tree.svg | 287 -- .../assets/samples/51-c4-context.svg | 81 - .../assets/samples/52-c4-container.svg | 91 - .../assets/samples/53-c4-component.svg | 84 - .../54-deployment-runtime-topology.svg | 158 - .../55-quality-attribute-utility-tree.svg | 98 - .../samples/56-architecture-tradeoff.svg | 147 - .../assets/samples/57-adr-decision.svg | 106 - .../assets/samples/58-capacity-bottleneck.svg | 188 - .../assets/samples/59-fault-propagation.svg | 138 - .../assets/samples/60-slo-error-budget.svg | 78 - .../samples/61-data-consistency-strategy.svg | 84 - .../62-trust-boundary-threat-model.svg | 176 - .../samples/63-multi-tenant-isolation.svg | 145 - .../samples/64-team-topology-ownership.svg | 135 - .../65-shared-context-architecture.svg | 120 - .../samples/66-ai-workflow-governance.svg | 111 - .../feishu-tech-diagram/metadata.json | 10 - .../references/diagram-prompts.json | 530 --- .../references/template-catalog.md | 151 - .../references/template-specs.json | 3142 ----------------- .../references/visual-examples.md | 295 -- .../scripts/render_lark_skill_doc.py | 75 - .../tests/validate_assets.py | 111 - .../resume-optimization/SKILL.md | 188 - .../resume-optimization/SKILL.zh.md | 100 - .../resume-optimization/metadata.json | 10 - .../rewrite-technical-tutorial/SKILL.md | 441 --- .../agents/openai.yaml | 4 - .../rewrite-technical-tutorial/metadata.json | 10 - .../systematic-debugging/CREATION-LOG.md | 119 - .../systematic-debugging/SKILL.md | 296 -- .../condition-based-waiting-example.ts | 158 - .../condition-based-waiting.md | 115 - .../systematic-debugging/defense-in-depth.md | 122 - .../systematic-debugging/find-polluter.sh | 63 - .../root-cause-tracing.md | 169 - .../systematic-debugging/test-academic.md | 14 - .../systematic-debugging/test-pressure-1.md | 58 - .../systematic-debugging/test-pressure-2.md | 68 - .../systematic-debugging/test-pressure-3.md | 69 - .../src/core/managed-skill-library.test.ts | 10 + apps/main-2.0/src/main/index.ts | 6 +- apps/main-2.0/tsconfig.json | 3 +- 132 files changed, 118 insertions(+), 16055 deletions(-) create mode 100644 .release-notes/fix-issue-534-bundled-skills.md rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/brainstorming/SKILL.zh.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/brainstorming/metadata.json (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/code-review-and-quality/SKILL.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/code-review-and-quality/SKILL.zh.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/code-review-and-quality/metadata.json (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/frontend-design/SKILL.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/frontend-design/SKILL.zh.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/frontend-design/metadata.json (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/handoff/SKILL.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/handoff/SKILL.zh.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/handoff/metadata.json (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/paper-writing/SKILL.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/paper-writing/SKILL.zh.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/paper-writing/metadata.json (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/personal-finance-planning/SKILL.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/personal-finance-planning/SKILL.zh.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/personal-finance-planning/metadata.json (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/refactor-review-knowledge/SKILL.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/refactor-review-knowledge/SKILL.zh.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/refactor-review-knowledge/metadata.json (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/skill-creator/SKILL.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/skill-creator/SKILL.zh.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/skill-creator/metadata.json (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/systematic-debugging/SKILL.zh.md (100%) rename apps/main-2.0/{src/automation/engine/shared => assets}/bundled-skills/systematic-debugging/metadata.json (100%) delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/SKILL.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/references/visual-companion.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/SKILL.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/agents/openai.yaml delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/sample-manifest.json delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/01-react-loop.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/02-plan-and-execute.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/03-context-assembly.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/04-memory-architecture.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/05-rag-agent.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/06-supervisor-worker.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/07-router-specialist.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/08-parallel-fan-in.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/09-generator-reviewer.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/10-handoff-human.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/11-agent-development-lifecycle.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/12-prompt-development.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/13-tool-mcp-integration.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/14-agent-evaluation-loop.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/15-agent-trace-debugging.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/16-software-development-lifecycle.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/17-requirement-to-design.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/18-tdd-cycle.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/19-git-pr-review.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/20-cicd-release.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/21-layered-architecture.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/22-monolith-to-microservices.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/23-microservice-gateway.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/24-plugin-architecture.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/25-agent-platform.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/26-synchronous-sequence.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/27-asynchronous-sequence.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/28-human-agent-swimlane.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/29-task-state-machine.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/30-retry-compensation.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/31-data-pipeline.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/32-data-lineage.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/33-er-model.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/34-domain-model.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/35-cache-consistency.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/36-observability-loop.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/37-incident-response.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/38-resilience-control.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/39-authentication-authorization.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/40-sensitive-operation-approval.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/41-learning-roadmap.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/42-knowledge-mindmap.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/43-concept-dependency.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/44-mechanism-breakdown.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/45-one-picture-overview.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/46-architecture-evolution.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/47-project-milestones.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/48-technology-selection.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/49-capability-map.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/50-troubleshooting-tree.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/51-c4-context.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/52-c4-container.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/53-c4-component.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/54-deployment-runtime-topology.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/55-quality-attribute-utility-tree.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/56-architecture-tradeoff.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/57-adr-decision.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/58-capacity-bottleneck.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/59-fault-propagation.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/60-slo-error-budget.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/61-data-consistency-strategy.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/62-trust-boundary-threat-model.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/63-multi-tenant-isolation.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/64-team-topology-ownership.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/65-shared-context-architecture.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/66-ai-workflow-governance.svg delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/metadata.json delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/diagram-prompts.json delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/template-catalog.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/template-specs.json delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/visual-examples.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/scripts/render_lark_skill_doc.py delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/tests/validate_assets.py delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/SKILL.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/SKILL.zh.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/metadata.json delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/SKILL.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/agents/openai.yaml delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/metadata.json delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/CREATION-LOG.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/SKILL.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/condition-based-waiting-example.ts delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/condition-based-waiting.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/defense-in-depth.md delete mode 100755 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/find-polluter.sh delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/root-cause-tracing.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-academic.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-1.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-2.md delete mode 100644 apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-3.md diff --git a/.release-notes/fix-issue-534-bundled-skills.md b/.release-notes/fix-issue-534-bundled-skills.md new file mode 100644 index 000000000..51369db45 --- /dev/null +++ b/.release-notes/fix-issue-534-bundled-skills.md @@ -0,0 +1,7 @@ +# 修复 V2 内置 Skill 资源一致性 + + + +## Bug 修复 + +- 修复 V2 内置 Skill 在自动化模板、主 Skill 库与安装包之间可能内容不一致的问题，嵌套资源现在会随 Skill 完整交付。 diff --git a/apps/main-2.0/assets/bundled-skills/brainstorming/SKILL.md b/apps/main-2.0/assets/bundled-skills/brainstorming/SKILL.md index 780606560..9c515acdb 100644 --- a/apps/main-2.0/assets/bundled-skills/brainstorming/SKILL.md +++ b/apps/main-2.0/assets/bundled-skills/brainstorming/SKILL.md @@ -156,4 +156,4 @@ A browser-based companion for showing mockups, diagrams, and visual options duri A question about a UI topic is not automatically a visual question. "What does personality mean in this context?" is a conceptual question — use the terminal. "Which wizard layout works better?" is a visual question — use the browser. If they agree to the companion, read the detailed guide before proceeding: -`skills/brainstorming/visual-companion.md` +`references/visual-companion.md` diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/SKILL.zh.md b/apps/main-2.0/assets/bundled-skills/brainstorming/SKILL.zh.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/SKILL.zh.md rename to apps/main-2.0/assets/bundled-skills/brainstorming/SKILL.zh.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/metadata.json b/apps/main-2.0/assets/bundled-skills/brainstorming/metadata.json similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/metadata.json rename to apps/main-2.0/assets/bundled-skills/brainstorming/metadata.json diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/code-review-and-quality/SKILL.md b/apps/main-2.0/assets/bundled-skills/code-review-and-quality/SKILL.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/code-review-and-quality/SKILL.md rename to apps/main-2.0/assets/bundled-skills/code-review-and-quality/SKILL.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/code-review-and-quality/SKILL.zh.md b/apps/main-2.0/assets/bundled-skills/code-review-and-quality/SKILL.zh.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/code-review-and-quality/SKILL.zh.md rename to apps/main-2.0/assets/bundled-skills/code-review-and-quality/SKILL.zh.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/code-review-and-quality/metadata.json b/apps/main-2.0/assets/bundled-skills/code-review-and-quality/metadata.json similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/code-review-and-quality/metadata.json rename to apps/main-2.0/assets/bundled-skills/code-review-and-quality/metadata.json diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/frontend-design/SKILL.md b/apps/main-2.0/assets/bundled-skills/frontend-design/SKILL.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/frontend-design/SKILL.md rename to apps/main-2.0/assets/bundled-skills/frontend-design/SKILL.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/frontend-design/SKILL.zh.md b/apps/main-2.0/assets/bundled-skills/frontend-design/SKILL.zh.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/frontend-design/SKILL.zh.md rename to apps/main-2.0/assets/bundled-skills/frontend-design/SKILL.zh.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/frontend-design/metadata.json b/apps/main-2.0/assets/bundled-skills/frontend-design/metadata.json similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/frontend-design/metadata.json rename to apps/main-2.0/assets/bundled-skills/frontend-design/metadata.json diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/handoff/SKILL.md b/apps/main-2.0/assets/bundled-skills/handoff/SKILL.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/handoff/SKILL.md rename to apps/main-2.0/assets/bundled-skills/handoff/SKILL.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/handoff/SKILL.zh.md b/apps/main-2.0/assets/bundled-skills/handoff/SKILL.zh.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/handoff/SKILL.zh.md rename to apps/main-2.0/assets/bundled-skills/handoff/SKILL.zh.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/handoff/metadata.json b/apps/main-2.0/assets/bundled-skills/handoff/metadata.json similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/handoff/metadata.json rename to apps/main-2.0/assets/bundled-skills/handoff/metadata.json diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/paper-writing/SKILL.md b/apps/main-2.0/assets/bundled-skills/paper-writing/SKILL.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/paper-writing/SKILL.md rename to apps/main-2.0/assets/bundled-skills/paper-writing/SKILL.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/paper-writing/SKILL.zh.md b/apps/main-2.0/assets/bundled-skills/paper-writing/SKILL.zh.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/paper-writing/SKILL.zh.md rename to apps/main-2.0/assets/bundled-skills/paper-writing/SKILL.zh.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/paper-writing/metadata.json b/apps/main-2.0/assets/bundled-skills/paper-writing/metadata.json similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/paper-writing/metadata.json rename to apps/main-2.0/assets/bundled-skills/paper-writing/metadata.json diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/personal-finance-planning/SKILL.md b/apps/main-2.0/assets/bundled-skills/personal-finance-planning/SKILL.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/personal-finance-planning/SKILL.md rename to apps/main-2.0/assets/bundled-skills/personal-finance-planning/SKILL.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/personal-finance-planning/SKILL.zh.md b/apps/main-2.0/assets/bundled-skills/personal-finance-planning/SKILL.zh.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/personal-finance-planning/SKILL.zh.md rename to apps/main-2.0/assets/bundled-skills/personal-finance-planning/SKILL.zh.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/personal-finance-planning/metadata.json b/apps/main-2.0/assets/bundled-skills/personal-finance-planning/metadata.json similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/personal-finance-planning/metadata.json rename to apps/main-2.0/assets/bundled-skills/personal-finance-planning/metadata.json diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/refactor-review-knowledge/SKILL.md b/apps/main-2.0/assets/bundled-skills/refactor-review-knowledge/SKILL.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/refactor-review-knowledge/SKILL.md rename to apps/main-2.0/assets/bundled-skills/refactor-review-knowledge/SKILL.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/refactor-review-knowledge/SKILL.zh.md b/apps/main-2.0/assets/bundled-skills/refactor-review-knowledge/SKILL.zh.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/refactor-review-knowledge/SKILL.zh.md rename to apps/main-2.0/assets/bundled-skills/refactor-review-knowledge/SKILL.zh.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/refactor-review-knowledge/metadata.json b/apps/main-2.0/assets/bundled-skills/refactor-review-knowledge/metadata.json similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/refactor-review-knowledge/metadata.json rename to apps/main-2.0/assets/bundled-skills/refactor-review-knowledge/metadata.json diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/skill-creator/SKILL.md b/apps/main-2.0/assets/bundled-skills/skill-creator/SKILL.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/skill-creator/SKILL.md rename to apps/main-2.0/assets/bundled-skills/skill-creator/SKILL.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/skill-creator/SKILL.zh.md b/apps/main-2.0/assets/bundled-skills/skill-creator/SKILL.zh.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/skill-creator/SKILL.zh.md rename to apps/main-2.0/assets/bundled-skills/skill-creator/SKILL.zh.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/skill-creator/metadata.json b/apps/main-2.0/assets/bundled-skills/skill-creator/metadata.json similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/skill-creator/metadata.json rename to apps/main-2.0/assets/bundled-skills/skill-creator/metadata.json diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/SKILL.zh.md b/apps/main-2.0/assets/bundled-skills/systematic-debugging/SKILL.zh.md similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/SKILL.zh.md rename to apps/main-2.0/assets/bundled-skills/systematic-debugging/SKILL.zh.md diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/metadata.json b/apps/main-2.0/assets/bundled-skills/systematic-debugging/metadata.json similarity index 100% rename from apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/metadata.json rename to apps/main-2.0/assets/bundled-skills/systematic-debugging/metadata.json diff --git a/apps/main-2.0/electron.vite.config.ts b/apps/main-2.0/electron.vite.config.ts index 4f40f8a6c..fe46865ed 100644 --- a/apps/main-2.0/electron.vite.config.ts +++ b/apps/main-2.0/electron.vite.config.ts @@ -10,6 +10,8 @@ export default defineConfig({ input: { index: resolve("src/main/index.ts"), "live-session-worker": resolve("src/main/live-session-worker.ts"), + "bundled-skill-library": resolve("src/automation/engine/shared/bundled-skill-library.ts"), + "managed-skill-library": resolve("src/core/managed-skill-library.ts"), }, }, }, diff --git a/apps/main-2.0/scripts/check-source-entrypoints.mjs b/apps/main-2.0/scripts/check-source-entrypoints.mjs index f4b7fa5a5..de620409e 100644 --- a/apps/main-2.0/scripts/check-source-entrypoints.mjs +++ b/apps/main-2.0/scripts/check-source-entrypoints.mjs @@ -49,7 +49,6 @@ function collectSourceFiles(directory) { for (const entry of fs.readdirSync(directory, { withFileTypes: true })) { const entryPath = path.join(directory, entry.name); if (entry.isDirectory()) { - if (entryPath === path.join(sourceRoot, "automation", "engine", "shared", "bundled-skills")) continue; files.push(...collectSourceFiles(entryPath)); continue; } diff --git a/apps/main-2.0/scripts/package-smoke.mjs b/apps/main-2.0/scripts/package-smoke.mjs index 0e5bd3aee..0de01cac1 100644 --- a/apps/main-2.0/scripts/package-smoke.mjs +++ b/apps/main-2.0/scripts/package-smoke.mjs @@ -125,6 +125,8 @@ try { await Promise.all([ access(path.join(installedRoot, "out", "main", "index.js")), access(path.join(installedRoot, "out", "main", "live-session-worker.js")), + access(path.join(installedRoot, "out", "main", "bundled-skill-library.js")), + access(path.join(installedRoot, "out", "main", "managed-skill-library.js")), ]); await access(path.join(installedRoot, "out", "mcp", "workflow-entry.js")); await access(path.join(installedRoot, "dist", "main", "index.js")); @@ -145,6 +147,47 @@ try { if (diagramSamples.filter((entry) => entry.endsWith(".svg")).length !== 66) { throw new Error("Packaged diagram Skill must include all 66 SVG samples."); } + + const bundledSkillLibrary = await import(pathToFileURL(path.join(installedRoot, "out", "main", "bundled-skill-library.js")).href); + const loadBundledSkillTemplates = bundledSkillLibrary.loadBundledSkillTemplates ?? bundledSkillLibrary.default?.loadBundledSkillTemplates; + const bundledSkillAssetsFor = bundledSkillLibrary.bundledSkillAssetsFor ?? bundledSkillLibrary.default?.bundledSkillAssetsFor; + if (typeof loadBundledSkillTemplates !== "function" || typeof bundledSkillAssetsFor !== "function") { + throw new Error("Packaged bundled Skill loader did not expose its template and asset APIs."); + } + const bundledTemplates = loadBundledSkillTemplates(); + for (const templateId of ["rewrite-technical-tutorial", "feishu-tech-diagram"]) { + if (!bundledTemplates.some((template) => template.id === templateId && template.sourceType === "official")) { + throw new Error(`Packaged Automation templates did not discover ${templateId}.`); + } + } + const packagedDiagramAssets = bundledSkillAssetsFor("feishu-tech-diagram"); + if (packagedDiagramAssets.filter((asset) => asset.relativePath.startsWith("assets/samples/") && asset.relativePath.endsWith(".svg")).length !== 66) { + throw new Error("Packaged Automation loader must embed all 66 diagram SVG samples."); + } + + const managedSkillLibraryModule = await import(pathToFileURL(path.join(installedRoot, "out", "main", "managed-skill-library.js")).href); + const ManagedSkillLibrary = managedSkillLibraryModule.ManagedSkillLibrary ?? managedSkillLibraryModule.default?.ManagedSkillLibrary; + if (typeof ManagedSkillLibrary !== "function") throw new Error("Packaged managed Skill library was not exported."); + const managedLibrary = new ManagedSkillLibrary({ + libraryRoot: path.join(tempRoot, "managed-skills"), + homeDir: path.join(tempRoot, "managed-home"), + }); + managedLibrary.ensureBuiltinSkills(path.join(installedRoot, "assets", "bundled-skills")); + for (const skillId of ["rewrite-technical-tutorial", "feishu-tech-diagram"]) { + if (!managedLibrary.list().skills.some((skill) => skill.managedId === skillId)) { + throw new Error(`Packaged managed Skill library did not import ${skillId}.`); + } + } + const managedDiagram = managedLibrary.list().skills.find((skill) => skill.managedId === "feishu-tech-diagram"); + if (!managedDiagram) throw new Error("Packaged managed Skill library did not import feishu-tech-diagram."); + const managedDiagramSpecs = JSON.parse(await readFile(path.join(managedDiagram.directoryPath, "references", "template-specs.json"))); + if (!Array.isArray(managedDiagramSpecs) || managedDiagramSpecs.length !== 66) { + throw new Error("Managed Skill import did not retain all 66 diagram template specifications."); + } + const managedDiagramSamples = await readdir(path.join(managedDiagram.directoryPath, "assets", "samples")); + if (managedDiagramSamples.filter((entry) => entry.endsWith(".svg")).length !== 66) { + throw new Error("Managed Skill import did not retain all 66 diagram SVG samples."); + } const installedRequire = createRequire(path.join(installedRoot, "package.json")); const { restoreEmbeddedPostgresNativeLinks, diff --git a/apps/main-2.0/src/automation/engine/main/bridges/mcp-bridge.test.ts b/apps/main-2.0/src/automation/engine/main/bridges/mcp-bridge.test.ts index cc63cf808..9a2f4b9ef 100644 --- a/apps/main-2.0/src/automation/engine/main/bridges/mcp-bridge.test.ts +++ b/apps/main-2.0/src/automation/engine/main/bridges/mcp-bridge.test.ts @@ -519,7 +519,7 @@ describe("MCP bridge", () => { const skillTemplates = (await (await bridgeRequest("/mcp/skill-templates/list", bridge.token, {})).json()) as any; expect(skillTemplates).toMatchObject({ ok: true, - templates: expect.arrayContaining([expect.objectContaining({ id: "brainstorming", sourcePath: "src/shared/bundled-skills/brainstorming/SKILL.md" })]), + templates: expect.arrayContaining([expect.objectContaining({ id: "brainstorming", sourcePath: "assets/bundled-skills/brainstorming/SKILL.md" })]), }); const skillSearch = (await (await bridgeRequest("/mcp/skills/search-online", bridge.token, { query: "frontend design anthropic" })).json()) as any; diff --git a/apps/main-2.0/src/automation/engine/main/skills/skill-installer.ts b/apps/main-2.0/src/automation/engine/main/skills/skill-installer.ts index 06585270d..254d5481d 100644 --- a/apps/main-2.0/src/automation/engine/main/skills/skill-installer.ts +++ b/apps/main-2.0/src/automation/engine/main/skills/skill-installer.ts @@ -1,7 +1,5 @@ -import { existsSync } from "node:fs"; -import { cp, lstat, mkdir, readdir, readFile, readlink, rm, symlink, unlink, writeFile } from "node:fs/promises"; +import { lstat, mkdir, readdir, readFile, readlink, rm, symlink, unlink, writeFile } from "node:fs/promises"; import path from "node:path"; -import { fileURLToPath } from "node:url"; import { bundledSkillAssetsFor } from "../../shared/bundled-skill-library"; import { parseSkillMarkdown } from "../../shared/online-skills"; import { SKILL_TEMPLATES } from "../../shared/skill-templates"; @@ -70,27 +68,12 @@ interface ImportedSkillMetadata { importedFromId?: string; } -function bundledSkillSourceDir(template: SkillTemplate): string | undefined { - if (!template.sourcePath?.startsWith("src/shared/bundled-skills/")) return undefined; - const relativeDir = path.dirname(template.sourcePath); - const moduleDir = path.dirname(fileURLToPath(import.meta.url)); - const candidates = [ - path.resolve(process.cwd(), relativeDir), - path.resolve(moduleDir, "..", "..", relativeDir), - path.resolve(moduleDir, "..", "shared", "bundled-skills", template.id), - ]; - return candidates.find((candidate) => pathExistsSync(candidate)); -} - -function pathExistsSync(filePath: string): boolean { - return existsSync(filePath); -} - async function writeEmbeddedSkillSource(template: SkillTemplate, sourceDir: string): Promise { const assets = bundledSkillAssetsFor(template.id); await mkdir(sourceDir, { recursive: true }); const skillAsset = assets.find((asset) => asset.relativePath === "SKILL.md"); - await writeFile(path.join(sourceDir, "SKILL.md"), skillAsset?.contents ?? `${template.prompt.trim()}\n`, "utf8"); + if (!skillAsset) throw new Error(`Bundled Skill ${template.id} is missing SKILL.md.`); + await writeFile(path.join(sourceDir, "SKILL.md"), skillAsset.contents, "utf8"); for (const asset of assets) { if (asset.relativePath === "SKILL.md") continue; const targetPath = path.join(sourceDir, asset.relativePath); @@ -194,12 +177,7 @@ export async function installBundledSkill(request: InstallSkillRequest, homeDir: const existed = await pathExists(linkPath); if (!imported) { await rm(sourceDir, { recursive: true, force: true }); - const bundledSourceDir = bundledSkillSourceDir(template); - if (bundledSourceDir) { - await cp(bundledSourceDir, sourceDir, { recursive: true }); - } else { - await writeEmbeddedSkillSource(template, sourceDir); - } + await writeEmbeddedSkillSource(template, sourceDir); } await mkdir(path.dirname(linkPath), { recursive: true }); if (existed) { diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.test.ts b/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.test.ts index 264483931..d283a4456 100644 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.test.ts +++ b/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.test.ts @@ -1,10 +1,36 @@ +import { existsSync } from "node:fs"; +import { fileURLToPath } from "node:url"; import { describe, expect, it } from "vitest"; import { bundledSkillAssetsFor, loadBundledSkillTemplates } from "./bundled-skill-library"; +const canonicalSkillRoot = fileURLToPath(new URL("../../../../assets/bundled-skills", import.meta.url)); +const legacySkillRoot = fileURLToPath(new URL("../../../../src/automation/engine/shared/bundled-skills", import.meta.url)); + describe("bundled Skill assets", () => { + it("keeps bundled Skill content in the packaged assets directory only", () => { + expect(existsSync(canonicalSkillRoot)).toBe(true); + expect(existsSync(legacySkillRoot)).toBe(false); + }); + it("lists the technical writing and diagram Skills as official writing templates", () => { const templates = loadBundledSkillTemplates(); + expect(templates.map((template) => template.id)).toEqual([ + "brainstorming", + "frontend-design", + "feishu-tech-diagram", + "handoff", + "skill-creator", + "systematic-debugging", + "personal-finance-planning", + "resume-optimization", + "paper-writing", + "rewrite-technical-tutorial", + "refactor-review-knowledge", + "code-review-and-quality", + ]); + expect(templates.every((template) => template.sourcePath?.startsWith("assets/bundled-skills/") ?? false)).toBe(true); + expect(templates.find((template) => template.id === "rewrite-technical-tutorial")) .toMatchObject({ name: "rewrite-technical-tutorial", diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.ts b/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.ts index 9898c56ad..a498c7db5 100644 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.ts +++ b/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.ts @@ -22,27 +22,29 @@ const BUNDLED_SKILL_ORDER = [ "code-review-and-quality", ]; -const skillMarkdownFiles = import.meta.glob("./bundled-skills/*/SKILL.md", { +const BUNDLED_SKILL_ROOT = "/assets/bundled-skills"; + +const skillMarkdownFiles = import.meta.glob("/assets/bundled-skills/*/SKILL.md", { eager: true, import: "default", query: "?raw", }); -const skillTranslationFiles = import.meta.glob("./bundled-skills/*/SKILL.zh.md", { +const skillTranslationFiles = import.meta.glob("/assets/bundled-skills/*/SKILL.zh.md", { eager: true, import: "default", query: "?raw", }); -const skillMetadataFiles = import.meta.glob("./bundled-skills/*/metadata.json", { +const skillMetadataFiles = import.meta.glob("/assets/bundled-skills/*/metadata.json", { eager: true, import: "default", query: "?raw", }); -const directSkillAssetFiles = import.meta.glob("./bundled-skills/*/*", { +const directSkillAssetFiles = import.meta.glob("/assets/bundled-skills/*/*", { eager: true, import: "default", query: "?raw", }); -const nestedSkillAssetFiles = import.meta.glob("./bundled-skills/*/**/*", { +const nestedSkillAssetFiles = import.meta.glob("/assets/bundled-skills/*/**/*", { eager: true, import: "default", query: "?raw", @@ -54,17 +56,17 @@ export interface BundledSkillAsset { } function skillIdFromPath(filePath: string): string { - const match = filePath.match(/\.\/bundled-skills\/([^/]+)\/[^/]+$/); + const match = filePath.match(/\/assets\/bundled-skills\/([^/]+)\/[^/]+$/); if (!match?.[1]) throw new Error(`Invalid bundled skill path: ${filePath}`); return match[1]; } function sourcePathFor(filePath: string): string { - return `src/shared/${filePath.replace(/^\.\//, "")}`; + return filePath.replace(/^\//, ""); } export function bundledSkillAssetsFor(skillId: string): BundledSkillAsset[] { - const prefix = `./bundled-skills/${skillId}/`; + const prefix = `${BUNDLED_SKILL_ROOT}/${skillId}/`; const assets = new Map(); for (const [filePath, contents] of Object.entries({ ...directSkillAssetFiles, ...nestedSkillAssetFiles })) { if (!filePath.startsWith(prefix)) continue; @@ -103,7 +105,7 @@ function stripYamlScalar(value: string): string { } function metadataFor(skillId: string): BundledSkillMetadata { - const raw = skillMetadataFiles[`./bundled-skills/${skillId}/metadata.json`]; + const raw = skillMetadataFiles[`${BUNDLED_SKILL_ROOT}/${skillId}/metadata.json`]; if (!raw) return {}; const parsed = JSON.parse(raw) as Partial; const metadata: BundledSkillMetadata = {}; @@ -116,14 +118,16 @@ function metadataFor(skillId: string): BundledSkillMetadata { function orderedSkillEntries(): Array<[string, string]> { const order = new Map(BUNDLED_SKILL_ORDER.map((id, index) => [id, index])); - return Object.entries(skillMarkdownFiles).sort(([leftPath], [rightPath]) => { - const leftId = skillIdFromPath(leftPath); - const rightId = skillIdFromPath(rightPath); - const leftOrder = order.get(leftId) ?? Number.MAX_SAFE_INTEGER; - const rightOrder = order.get(rightId) ?? Number.MAX_SAFE_INTEGER; - if (leftOrder !== rightOrder) return leftOrder - rightOrder; - return leftId.localeCompare(rightId); - }); + return Object.entries(skillMarkdownFiles) + .filter(([filePath]) => order.has(skillIdFromPath(filePath))) + .sort(([leftPath], [rightPath]) => { + const leftId = skillIdFromPath(leftPath); + const rightId = skillIdFromPath(rightPath); + const leftOrder = order.get(leftId) ?? Number.MAX_SAFE_INTEGER; + const rightOrder = order.get(rightId) ?? Number.MAX_SAFE_INTEGER; + if (leftOrder !== rightOrder) return leftOrder - rightOrder; + return leftId.localeCompare(rightId); + }); } export function loadBundledSkillTemplates(): SkillTemplate[] { @@ -145,7 +149,7 @@ export function loadBundledSkillTemplates(): SkillTemplate[] { }; const sourceUrl = metadata.sourceUrl; if (sourceUrl) template.sourceUrl = sourceUrl; - const translationZh = skillTranslationFiles[`./bundled-skills/${id}/SKILL.zh.md`]; + const translationZh = skillTranslationFiles[`${BUNDLED_SKILL_ROOT}/${id}/SKILL.zh.md`]; if (translationZh) template.translationZh = normalizeNewlines(translationZh); return template; }); diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/SKILL.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/SKILL.md deleted file mode 100644 index 9c515acdb..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/SKILL.md +++ /dev/null @@ -1,159 +0,0 @@ ---- -name: brainstorming -description: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation." ---- - -# Brainstorming Ideas Into Designs - -Help turn ideas into fully formed designs and specs through natural collaborative dialogue. - -Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval. - - -Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity. - - -## Anti-Pattern: "This Is Too Simple To Need A Design" - -Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval. - -## Checklist - -You MUST create a task for each of these items and complete them in order: - -1. **Explore project context** — check files, docs, recent commits -2. **Offer the visual companion just-in-time** — NOT upfront. The first time a question would genuinely be clearer shown than described, offer it then (its own message); on approval its browser tab opens for you. If no visual question ever arises, never offer it. See the Visual Companion section below. -3. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria -4. **Propose 2-3 approaches** — with trade-offs and your recommendation -5. **Present design** — in sections scaled to their complexity, get user approval after each section -6. **Write design doc** — save to `docs/superpowers/specs//YYYY-MM-DD--design.md` and commit -7. **Spec self-review** — quick inline check for placeholders, contradictions, ambiguity, scope (see below) -8. **User reviews written spec** — ask user to review the spec file before proceeding -9. **Transition to implementation** — invoke writing-plans skill to create implementation plan - -## Process Flow - -```dot -digraph brainstorming { - "Explore project context" [shape=box]; - "Ask clarifying questions" [shape=box]; - "Propose 2-3 approaches" [shape=box]; - "Present design sections" [shape=box]; - "User approves design?" [shape=diamond]; - "Write design doc" [shape=box]; - "Spec self-review\n(fix inline)" [shape=box]; - "User reviews spec?" [shape=diamond]; - "Invoke writing-plans skill" [shape=doublecircle]; - - "Explore project context" -> "Ask clarifying questions"; - "Ask clarifying questions" -> "Propose 2-3 approaches"; - "Propose 2-3 approaches" -> "Present design sections"; - "Present design sections" -> "User approves design?"; - "User approves design?" -> "Present design sections" [label="no, revise"]; - "User approves design?" -> "Write design doc" [label="yes"]; - "Write design doc" -> "Spec self-review\n(fix inline)"; - "Spec self-review\n(fix inline)" -> "User reviews spec?"; - "User reviews spec?" -> "Write design doc" [label="changes requested"]; - "User reviews spec?" -> "Invoke writing-plans skill" [label="approved"]; -} -``` - -**The terminal state is invoking writing-plans.** Do NOT invoke frontend-design, mcp-builder, or any other implementation skill. The ONLY skill you invoke after brainstorming is writing-plans. - -## The Process - -**Understanding the idea:** - -- Check out the current project state first (files, docs, recent commits) -- Before asking detailed questions, assess scope: if the request describes multiple independent subsystems (e.g., "build a platform with chat, file storage, billing, and analytics"), flag this immediately. Don't spend questions refining details of a project that needs to be decomposed first. -- If the project is too large for a single spec, help the user decompose into sub-projects: what are the independent pieces, how do they relate, what order should they be built? Then brainstorm the first sub-project through the normal design flow. Each sub-project gets its own spec → plan → implementation cycle. -- For appropriately-scoped projects, ask questions one at a time to refine the idea -- Prefer multiple choice questions when possible, but open-ended is fine too -- Only one question per message - if a topic needs more exploration, break it into multiple questions -- Focus on understanding: purpose, constraints, success criteria - -**Exploring approaches:** - -- Propose 2-3 different approaches with trade-offs -- Present options conversationally with your recommendation and reasoning -- Lead with your recommended option and explain why - -**Presenting the design:** - -- Once you believe you understand what you're building, present the design -- Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced -- Ask after each section whether it looks right so far -- Cover: architecture, components, data flow, error handling, testing -- Be ready to go back and clarify if something doesn't make sense - -**Design for isolation and clarity:** - -- Break the system into smaller units that each have one clear purpose, communicate through well-defined interfaces, and can be understood and tested independently -- For each unit, you should be able to answer: what does it do, how do you use it, and what does it depend on? -- Can someone understand what a unit does without reading its internals? Can you change the internals without breaking consumers? If not, the boundaries need work. -- Smaller, well-bounded units are also easier for you to work with - you reason better about code you can hold in context at once, and your edits are more reliable when files are focused. When a file grows large, that's often a signal that it's doing too much. - -**Working in existing codebases:** - -- Explore the current structure before proposing changes. Follow existing patterns. -- Where existing code has problems that affect the work (e.g., a file that's grown too large, unclear boundaries, tangled responsibilities), include targeted improvements as part of the design - the way a good developer improves code they're working in. -- Don't propose unrelated refactoring. Stay focused on what serves the current goal. - -## After the Design - -**Documentation:** - -- Write the validated design (spec) to `docs/superpowers/specs//YYYY-MM-DD--design.md` - - (User preferences for spec location override this default) -- Use elements-of-style:writing-clearly-and-concisely skill if available -- Commit the design document to git - -**Spec Self-Review:** -After writing the spec document, look at it with fresh eyes: - -1. **Placeholder scan:** Any "TBD", "TODO", incomplete sections, or vague requirements? Fix them. -2. **Internal consistency:** Do any sections contradict each other? Does the architecture match the feature descriptions? -3. **Scope check:** Is this focused enough for a single implementation plan, or does it need decomposition? -4. **Ambiguity check:** Could any requirement be interpreted two different ways? If so, pick one and make it explicit. - -Fix any issues inline. No need to re-review — just fix and move on. - -**User Review Gate:** -After the spec review loop passes, ask the user to review the written spec before proceeding: - -> "Spec written and committed to ``. Please review it and let me know if you want to make any changes before we start writing out the implementation plan." - -Wait for the user's response. If they request changes, make them and re-run the spec review loop. Only proceed once the user approves. - -**Implementation:** - -- Invoke the writing-plans skill to create a detailed implementation plan -- Do NOT invoke any other skill. writing-plans is the next step. - -## Key Principles - -- **One question at a time** - Don't overwhelm with multiple questions -- **Multiple choice preferred** - Easier to answer than open-ended when possible -- **YAGNI ruthlessly** - Remove unnecessary features from all designs -- **Explore alternatives** - Always propose 2-3 approaches before settling -- **Incremental validation** - Present design, get approval before moving on -- **Be flexible** - Go back and clarify when something doesn't make sense - -## Visual Companion - -A browser-based companion for showing mockups, diagrams, and visual options during brainstorming. Available as a tool — not a mode. Accepting the companion means it's available for questions that benefit from visual treatment; it does NOT mean every question goes through the browser. - -**Offering the companion (just-in-time):** Do NOT offer it upfront. Wait until a question would genuinely be clearer shown than told — a real mockup / layout / diagram question, not merely a UI *topic*. The first time that happens, offer it then, as its own message: -> "This next part might be easier if I show you — I can put together mockups, diagrams, and comparisons in a browser tab as we go. It's still new and can be token-intensive. Want me to? I'll open it for you." - -**This offer MUST be its own message.** Only the offer — no clarifying question, summary, or other content. Wait for the user's response. If they accept, start the server with `--open` so their browser opens to the first screen automatically. If they decline, continue text-only and don't offer again unless they raise it. - -**Per-question decision:** Even after the user accepts, decide FOR EACH QUESTION whether to use the browser or the terminal. The test: **would the user understand this better by seeing it than reading it?** - -- **Use the browser** for content that IS visual — mockups, wireframes, layout comparisons, architecture diagrams, side-by-side visual designs -- **Use the terminal** for content that is text — requirements questions, conceptual choices, tradeoff lists, A/B/C/D text options, scope decisions - -A question about a UI topic is not automatically a visual question. "What does personality mean in this context?" is a conceptual question — use the terminal. "Which wizard layout works better?" is a visual question — use the browser. - -If they agree to the companion, read the detailed guide before proceeding: -`references/visual-companion.md` diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/references/visual-companion.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/references/visual-companion.md deleted file mode 100644 index fbb3610a9..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/brainstorming/references/visual-companion.md +++ /dev/null @@ -1,5 +0,0 @@ -# Visual companion - -This optional reference explains how the brainstorming skill can use a visual companion when a mockup, diagram, or layout comparison is clearer than text. - -Keep this file in the skill folder so local installation copies references alongside the original `SKILL.md`. diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/SKILL.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/SKILL.md deleted file mode 100644 index f9b2e97cb..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/SKILL.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -name: feishu-tech-diagram -description: Use when a Lark/Feishu technical document needs an editable architecture diagram, flowchart, sequence diagram, state model, data relationship, Agent workflow, development process, reliability view, learning map, roadmap, or decision visualization. ---- - -# 飞书技术图表 - -先讲清关系，再处理布局和配色。图只补充正文，不重复正文；最终交付优先使用可编辑飞书画板。 - -## 必做流程 - -1. 读取目标章节和相邻上下文；有现有画板时先回读代码、raw 节点或预览。 -2. 写图意图卡：一句话结论、目标读者、抽象层级、主链、分组、分支、方向和目标载体。 -3. 从 [template-catalog.md](references/template-catalog.md) 选择关系结构最接近的模板，再读取 [template-specs.json](references/template-specs.json) 中同编号的输入、必备语义和坏味道。 -4. 打开 [visual-examples.md](references/visual-examples.md) 中同编号 SVG，只复用构图；必须替换示例里的通用节点。 -5. 生成后检查文字截断、节点重叠、交叉线、空白、抽象层级、边界、边标签和失败路径；最多迭代两轮，仍拥挤则拆图。 -6. 写入飞书前预览；覆盖已有画板先 dry-run，写入后回读验证。 - -## 图意图卡 - -```text -一句话结论： -目标读者： -抽象层级：Context / Container / Component / Runtime / Process / Decision -主链： -分组： -分支或异常： -方向：LR / TB / 泳道 / 时序 / 状态 / 脑图 -目标：本地 SVG 预览 / 新建可编辑画板 / 更新已有画板 -``` - -## 选型规则 - -- 先按“要回答的问题”选模板，不按视觉外形选。 -- 一张图只使用一个主要抽象层级；跨层信息拆成图组。 -- 主节点控制在 6–12 个；边超过 15 条或多条跨层回边时拆图。 -- 横向主链用 LR，稳定层次用 TB，角色协作用泳道，调用先后用时序。 -- 节点写“短标题 + 一行职责”，边标签写协议、动作、数据或条件。 -- Context 与安全图必须标系统或信任边界；生产评审图必须表达失败路径。 - -## 最小图组 - -- 系统说明：Context + Container。 -- 核心链路：Container + 时序或数据流。 -- 生产评审：Container + 部署拓扑 + 故障传播 + SLO。 -- 安全评审：Context + 信任边界 + 认证授权 + 敏感操作审批。 -- Agent 系统：Context + Agent 平台 + 执行时序 + 工具权限 + Trace/Eval。 - -## 可编辑交付 - -- 本地 SVG 只使用飞书画板可识别的基础形状、文字、连线和安全变换。 -- 写入飞书时使用 `...` 或 ``，让基础元素转换为可编辑节点。 -- 禁止用 PNG/JPEG 作为模板交付；位图只用于临时预览。 -- 多个模板写入同一文档时，每个画板紧跟对应模板说明，不集中堆到文档末尾。 -- 交付物不得包含水印、来源声明、会话链接、任务标识、真实业务名或账号信息。 - -## 资产 - -- 模板目录：[template-catalog.md](references/template-catalog.md) -- 完整结构化规范：[template-specs.json](references/template-specs.json) -- 可改写提示词：[diagram-prompts.json](references/diagram-prompts.json) -- SVG 示例索引：[visual-examples.md](references/visual-examples.md) -- SVG 源文件：`assets/samples/` - -更新资产后运行： - -```bash -python3 tests/validate_assets.py -``` - -## 交付检查 - -- 主链、边界和结论三秒内可辨认。 -- 不含无依据新增的组件、依赖、日期或指标。 -- 同层对齐、同组同色，形状语义一致。 -- 箭头有方向，关键边有协议、动作、数据或条件。 -- 无文字截断、节点重叠、明显交叉线或大面积空白。 -- 飞书中的节点、文字和连线可以继续编辑。 -- 写入后已通过 preview、source 或 raw 至少一种方式回读。 diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/agents/openai.yaml b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/agents/openai.yaml deleted file mode 100644 index fdcc2d332..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/agents/openai.yaml +++ /dev/null @@ -1,4 +0,0 @@ -interface: - display_name: "飞书技术图表" - short_description: "生成、重绘并校验可编辑的飞书技术图表与六十六类模板" - default_prompt: "Use $feishu-tech-diagram to turn this technical design into a clear editable diagram." diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/sample-manifest.json b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/sample-manifest.json deleted file mode 100644 index d77567d97..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/sample-manifest.json +++ /dev/null @@ -1,402 +0,0 @@ -{ - "version": 1, - "total": 66, - "samples": [ - { - "id": "01", - "slug": "react-loop", - "svg_path": "assets/samples/01-react-loop.svg", - "status": "ready" - }, - { - "id": "02", - "slug": "plan-and-execute", - "svg_path": "assets/samples/02-plan-and-execute.svg", - "status": "ready" - }, - { - "id": "03", - "slug": "context-assembly", - "svg_path": "assets/samples/03-context-assembly.svg", - "status": "ready" - }, - { - "id": "04", - "slug": "memory-architecture", - "svg_path": "assets/samples/04-memory-architecture.svg", - "status": "ready" - }, - { - "id": "05", - "slug": "rag-agent", - "svg_path": "assets/samples/05-rag-agent.svg", - "status": "ready" - }, - { - "id": "06", - "slug": "supervisor-worker", - "svg_path": "assets/samples/06-supervisor-worker.svg", - "status": "ready" - }, - { - "id": "07", - "slug": "router-specialist", - "svg_path": "assets/samples/07-router-specialist.svg", - "status": "ready" - }, - { - "id": "08", - "slug": "parallel-fan-in", - "svg_path": "assets/samples/08-parallel-fan-in.svg", - "status": "ready" - }, - { - "id": "09", - "slug": "generator-reviewer", - "svg_path": "assets/samples/09-generator-reviewer.svg", - "status": "ready" - }, - { - "id": "10", - "slug": "handoff-human", - "svg_path": "assets/samples/10-handoff-human.svg", - "status": "ready" - }, - { - "id": "11", - "slug": "agent-development-lifecycle", - "svg_path": "assets/samples/11-agent-development-lifecycle.svg", - "status": "ready" - }, - { - "id": "12", - "slug": "prompt-development", - "svg_path": "assets/samples/12-prompt-development.svg", - "status": "ready" - }, - { - "id": "13", - "slug": "tool-mcp-integration", - "svg_path": "assets/samples/13-tool-mcp-integration.svg", - "status": "ready" - }, - { - "id": "14", - "slug": "agent-evaluation-loop", - "svg_path": "assets/samples/14-agent-evaluation-loop.svg", - "status": "ready" - }, - { - "id": "15", - "slug": "agent-trace-debugging", - "svg_path": "assets/samples/15-agent-trace-debugging.svg", - "status": "ready" - }, - { - "id": "16", - "slug": "software-development-lifecycle", - "svg_path": "assets/samples/16-software-development-lifecycle.svg", - "status": "ready" - }, - { - "id": "17", - "slug": "requirement-to-design", - "svg_path": "assets/samples/17-requirement-to-design.svg", - "status": "ready" - }, - { - "id": "18", - "slug": "tdd-cycle", - "svg_path": "assets/samples/18-tdd-cycle.svg", - "status": "ready" - }, - { - "id": "19", - "slug": "git-pr-review", - "svg_path": "assets/samples/19-git-pr-review.svg", - "status": "ready" - }, - { - "id": "20", - "slug": "cicd-release", - "svg_path": "assets/samples/20-cicd-release.svg", - "status": "ready" - }, - { - "id": "21", - "slug": "layered-architecture", - "svg_path": "assets/samples/21-layered-architecture.svg", - "status": "ready" - }, - { - "id": "22", - "slug": "monolith-to-microservices", - "svg_path": "assets/samples/22-monolith-to-microservices.svg", - "status": "ready" - }, - { - "id": "23", - "slug": "microservice-gateway", - "svg_path": "assets/samples/23-microservice-gateway.svg", - "status": "ready" - }, - { - "id": "24", - "slug": "plugin-architecture", - "svg_path": "assets/samples/24-plugin-architecture.svg", - "status": "ready" - }, - { - "id": "25", - "slug": "agent-platform", - "svg_path": "assets/samples/25-agent-platform.svg", - "status": "ready" - }, - { - "id": "26", - "slug": "synchronous-sequence", - "svg_path": "assets/samples/26-synchronous-sequence.svg", - "status": "ready" - }, - { - "id": "27", - "slug": "asynchronous-sequence", - "svg_path": "assets/samples/27-asynchronous-sequence.svg", - "status": "ready" - }, - { - "id": "28", - "slug": "human-agent-swimlane", - "svg_path": "assets/samples/28-human-agent-swimlane.svg", - "status": "ready" - }, - { - "id": "29", - "slug": "task-state-machine", - "svg_path": "assets/samples/29-task-state-machine.svg", - "status": "ready" - }, - { - "id": "30", - "slug": "retry-compensation", - "svg_path": "assets/samples/30-retry-compensation.svg", - "status": "ready" - }, - { - "id": "31", - "slug": "data-pipeline", - "svg_path": "assets/samples/31-data-pipeline.svg", - "status": "ready" - }, - { - "id": "32", - "slug": "data-lineage", - "svg_path": "assets/samples/32-data-lineage.svg", - "status": "ready" - }, - { - "id": "33", - "slug": "er-model", - "svg_path": "assets/samples/33-er-model.svg", - "status": "ready" - }, - { - "id": "34", - "slug": "domain-model", - "svg_path": "assets/samples/34-domain-model.svg", - "status": "ready" - }, - { - "id": "35", - "slug": "cache-consistency", - "svg_path": "assets/samples/35-cache-consistency.svg", - "status": "ready" - }, - { - "id": "36", - "slug": "observability-loop", - "svg_path": "assets/samples/36-observability-loop.svg", - "status": "ready" - }, - { - "id": "37", - "slug": "incident-response", - "svg_path": "assets/samples/37-incident-response.svg", - "status": "ready" - }, - { - "id": "38", - "slug": "resilience-control", - "svg_path": "assets/samples/38-resilience-control.svg", - "status": "ready" - }, - { - "id": "39", - "slug": "authentication-authorization", - "svg_path": "assets/samples/39-authentication-authorization.svg", - "status": "ready" - }, - { - "id": "40", - "slug": "sensitive-operation-approval", - "svg_path": "assets/samples/40-sensitive-operation-approval.svg", - "status": "ready" - }, - { - "id": "41", - "slug": "learning-roadmap", - "svg_path": "assets/samples/41-learning-roadmap.svg", - "status": "ready" - }, - { - "id": "42", - "slug": "knowledge-mindmap", - "svg_path": "assets/samples/42-knowledge-mindmap.svg", - "status": "ready" - }, - { - "id": "43", - "slug": "concept-dependency", - "svg_path": "assets/samples/43-concept-dependency.svg", - "status": "ready" - }, - { - "id": "44", - "slug": "mechanism-breakdown", - "svg_path": "assets/samples/44-mechanism-breakdown.svg", - "status": "ready" - }, - { - "id": "45", - "slug": "one-picture-overview", - "svg_path": "assets/samples/45-one-picture-overview.svg", - "status": "ready" - }, - { - "id": "46", - "slug": "architecture-evolution", - "svg_path": "assets/samples/46-architecture-evolution.svg", - "status": "ready" - }, - { - "id": "47", - "slug": "project-milestones", - "svg_path": "assets/samples/47-project-milestones.svg", - "status": "ready" - }, - { - "id": "48", - "slug": "technology-selection", - "svg_path": "assets/samples/48-technology-selection.svg", - "status": "ready" - }, - { - "id": "49", - "slug": "capability-map", - "svg_path": "assets/samples/49-capability-map.svg", - "status": "ready" - }, - { - "id": "50", - "slug": "troubleshooting-tree", - "svg_path": "assets/samples/50-troubleshooting-tree.svg", - "status": "ready" - }, - { - "id": "51", - "slug": "c4-context", - "svg_path": "assets/samples/51-c4-context.svg", - "status": "ready" - }, - { - "id": "52", - "slug": "c4-container", - "svg_path": "assets/samples/52-c4-container.svg", - "status": "ready" - }, - { - "id": "53", - "slug": "c4-component", - "svg_path": "assets/samples/53-c4-component.svg", - "status": "ready" - }, - { - "id": "54", - "slug": "deployment-runtime-topology", - "svg_path": "assets/samples/54-deployment-runtime-topology.svg", - "status": "ready" - }, - { - "id": "55", - "slug": "quality-attribute-utility-tree", - "svg_path": "assets/samples/55-quality-attribute-utility-tree.svg", - "status": "ready" - }, - { - "id": "56", - "slug": "architecture-tradeoff", - "svg_path": "assets/samples/56-architecture-tradeoff.svg", - "status": "ready" - }, - { - "id": "57", - "slug": "adr-decision", - "svg_path": "assets/samples/57-adr-decision.svg", - "status": "ready" - }, - { - "id": "58", - "slug": "capacity-bottleneck", - "svg_path": "assets/samples/58-capacity-bottleneck.svg", - "status": "ready" - }, - { - "id": "59", - "slug": "fault-propagation", - "svg_path": "assets/samples/59-fault-propagation.svg", - "status": "ready" - }, - { - "id": "60", - "slug": "slo-error-budget", - "svg_path": "assets/samples/60-slo-error-budget.svg", - "status": "ready" - }, - { - "id": "61", - "slug": "data-consistency-strategy", - "svg_path": "assets/samples/61-data-consistency-strategy.svg", - "status": "ready" - }, - { - "id": "62", - "slug": "trust-boundary-threat-model", - "svg_path": "assets/samples/62-trust-boundary-threat-model.svg", - "status": "ready" - }, - { - "id": "63", - "slug": "multi-tenant-isolation", - "svg_path": "assets/samples/63-multi-tenant-isolation.svg", - "status": "ready" - }, - { - "id": "64", - "slug": "team-topology-ownership", - "svg_path": "assets/samples/64-team-topology-ownership.svg", - "status": "ready" - }, - { - "id": "65", - "slug": "shared-context-architecture", - "svg_path": "assets/samples/65-shared-context-architecture.svg", - "status": "ready" - }, - { - "id": "66", - "slug": "ai-workflow-governance", - "svg_path": "assets/samples/66-ai-workflow-governance.svg", - "status": "ready" - } - ] -} diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/01-react-loop.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/01-react-loop.svg deleted file mode 100644 index caf64a2da..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/01-react-loop.svg +++ /dev/null @@ -1,63 +0,0 @@ - - - - - - - - - - - ReAct Agent 核心循环 - - - - - - - - - - - - - - 是 - 否 - - - - - 用户目标 - User Goal - - - - 思考 - Thought - - - - 选择工具 - Select Tool - - - - 执行工具 - Execute - - - - 观察结果 - Observation - - - - 是否完成 - Is Complete? - - - - 最终输出 - Final Output - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/02-plan-and-execute.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/02-plan-and-execute.svg deleted file mode 100644 index c74ae4a05..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/02-plan-and-execute.svg +++ /dev/null @@ -1,79 +0,0 @@ - - - - - - - - - - - - - - - 计划阶段 (Plan) - - - - 执行阶段 (Execute) - - - - - - - - - - - - - - - - - - - 否 - 是 - 是 (遇到新信息，触发重规划) - 否 (继续执行下一任务) - - - - - 用户目标 - - - - 规划器 - 分解并排期 - - - - 任务列表 - 管理执行队列 - - - - 执行器 - 调用具体工具 - - - - 更新状态 - 记录执行反馈 - - - - 遇到新信息? - - - - 全部完成? - - - - 汇总输出 - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/03-context-assembly.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/03-context-assembly.svg deleted file mode 100644 index 751f79c64..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/03-context-assembly.svg +++ /dev/null @@ -1,155 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 上下文来源 (分级路由) - - - - - 组装与处理管道 - - - - 严格把控质量与冗余度，动态截断长尾信息以匹配目标模型上下文窗口限制 - - - - - - 系统指令 - System Prompt - - P0 - - - - - 用户输入 - User Query - - P0 - - - - - 对话历史 - Chat History - - P1 - - - - - 长期记忆 - Long-term Memory - - P2 - - - - - 知识检索 - Knowledge Base - - P1 - - - - - 工具结果 - Tool Results - - P1 - - - - - 无效过滤 - Filter - - - 裁剪 - - - - 语义去重 - Deduplicate - - - 裁剪 - - - - 相关性排序 - Ranking - - - - Token 控制 - Budgeting - - - 裁剪 - - - Final Prompt - - - - - 模型输入 - Model Input - - - - - - - - Agent 上下文多源组装与控制架构图 - Multi-source Context Assembly & Token Budget Control - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/04-memory-architecture.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/04-memory-architecture.svg deleted file mode 100644 index f796b47ed..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/04-memory-architecture.svg +++ /dev/null @@ -1,160 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 感知 / 截获 - 更新上下文 - 提取实体 - 持久化入库 - 按需组装注入 - - - - - - - - - - - - - 工作记忆 - Working Memory - - • 维护当前 Token 窗口与短期状态 - • 即时逻辑推理与任务意图解析 - - - - - - 会话记忆 - Session Memory - - • 记录对话历史与近远期交互轮次 - • 保留多轮对话连贯性与局部实体 - - - - - - - - 长期记忆 - Long-Term Memory - - • 持久化向量库 (Vector) 与图谱 - • 提供全局领域知识及长周期经验 - - - - - - - - - - 记忆抽取 - 感知结构化片段 - - - - - - 价值评分 - 权重筛选与重要度 - - - - - - - - 去重写入 - 合并相似及覆写 - - - - - - - - - - 按需检索 - - • 混合相似度搜索 - • 实体关系追溯 - - - - - - - - - - - 遗忘清理 - 衰减与周期淘汰 - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/05-rag-agent.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/05-rag-agent.svg deleted file mode 100644 index acd2207af..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/05-rag-agent.svg +++ /dev/null @@ -1,141 +0,0 @@ - - - - - - - - - - - - - - - 检索与处理链路 - - - - 生成与校验链路 - - - - - - - - - - - - - - - - - - - - - - - - - - 提问 - - - - 查询 - - - - 文档 - - - - 文档 - - - - 提示词 - - - - 引用 - - - - 回答 - - - - 查询 - - - - 查询 - - - - 文档 - - - - 文档 - - - - - 用户 - - - - 查询改写 - Query Rewrite - - - - 多路检索 - Multi-way Retrieval - - - - 召回合并 - Recall & Merge - - - - 重排 - Reranking - - - - 上下文构造 - Context Builder - - - - 模型生成 - Model Generation - - - - 引用校验 - Citation Validation - - - - 输出 - - - - 向量索引 - Vector Index - - - - 知识库 - Knowledge Base - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/06-supervisor-worker.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/06-supervisor-worker.svg deleted file mode 100644 index 84bf72ab7..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/06-supervisor-worker.svg +++ /dev/null @@ -1,165 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Supervisor (主管中枢域) - - - 基于全局上下文的 - 意图与调度控制 - - - - Worker (并发执行池) - - - - - - - - - - - - - - - - - - - - - - 多路并行派发 - - - - - - - - - - - - 上传节点输出 - - 底层通道: 统一结果入流与映射 - - - - - - - - - - - - 阻断: 不通过则返工 - - - - - - - - - - - - - - - 业务目标 - (输入参数/Prompt) - - - - - - - 接收目标 - 解析意图与约束 - - - - - - - 规划与拆分 - 生成执行子任务 - 依赖关系编排 - - - - - - - 汇总与验收 - 聚合 Worker 产出 - 校验标准及逻辑闭环 - - - - - - - - - 最终结果输出 - - - - - - - - 研究 Worker - • 广度信息定向采集 - • 提供基础决策数据 - - - - - 执行 Worker - • 核心任务指令推进 - • 产出结构化中间态 - - - - - 验证 Worker - • 交叉校验局部逻辑 - • 评估偏差与格式对齐 - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/07-router-specialist.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/07-router-specialist.svg deleted file mode 100644 index a9d1d82e0..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/07-router-specialist.svg +++ /dev/null @@ -1,93 +0,0 @@ - - - - - - - - - - - - - 专家 Agent 集群 (Specialist Agents) - - - - - - - - - - - - - - - - - - - - - - - 代码相关 - 数据分析 - 文档检索 - 未识别 / 其他 - - - - - - - - 用户请求 - User Request - - - - - - 意图识别与路由 - Router Agent - - - - - - 代码专家 - Code Agent - - - - - - 数据专家 - Data Agent - - - - - - 文档专家 - Doc Agent - - - - - - 通用助手 - General Agent - - - - - - 统一适配与输出 - Response Formatting - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/08-parallel-fan-in.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/08-parallel-fan-in.svg deleted file mode 100644 index 26935a365..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/08-parallel-fan-in.svg +++ /dev/null @@ -1,99 +0,0 @@ - - - - - - - - - - - Multi-Agent 并行执行池 - - - - - - - - Task 1 载荷 - Task 2 载荷 - Task 3 载荷 - - - - - - - 结果校验码 - 标准化产物 - 返回结果集 - - - - Final Data - - - - - - - 任务接收与分发 - Fan-out 路由控制 - - 异步触发并行链路 - - - - - 子任务 Agent A - 独立进程隔离执行 - - - 超时监控 - - 结果校验 - - - - - 子任务 Agent B - 独立进程隔离执行 - - - 超时监控 - - 结果校验 - - - - - 子任务 Agent C - 独立进程隔离执行 - - - 超时监控 - - 结果校验 - - - - 结果聚合器 - Fan-in 汇合引擎 - - - - 1. 冲突去重 (Dedup) - - - 2. 按权重排序 (Sort) - - - 3. 结果合并 (Merge) - - - - 合并输出 - 下游链路处理结果 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/09-generator-reviewer.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/09-generator-reviewer.svg deleted file mode 100644 index 637667dc1..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/09-generator-reviewer.svg +++ /dev/null @@ -1,82 +0,0 @@ - - - - - - - - - - - - - - - - - - Generator–Reviewer Agent 闭环架构 - 通过多维度审查与自动反馈机制，实现任务输出的多轮自我优化 (Max = 3) - - - - - 任务需求 - - - - 提交草稿 - - - - 打分结果 - - - - Yes - - - - - - 未通过：附带评审反馈并打回（累计 < 3 轮） - - - - - - 业务需求 - - - - - - Generator Agent - (生成任务草稿) - - - - - - - - Reviewer Agent - - - - - 维度一：正确性 - - 维度二：完整性 - - 维度三：格式合规 - - - - 是否评审通过? - (或达3轮上限) - - - - 最终输出 - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/10-handoff-human.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/10-handoff-human.svg deleted file mode 100644 index 6a4bebc12..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/10-handoff-human.svg +++ /dev/null @@ -1,113 +0,0 @@ - - - - - - - - - - Agent Handoff 核心路由工作流 - 跨智能体交接与高风险人工接管的标准封装协议 - - - - - - - - - - - - Agent A - (前端接待) - - - - 编排平台 - (Orchestration) - - - - Agent B - (专业技能) - - - - 人工专家 - (Human) - - - - - - - - - - - - - - 常规意图 / 低风险 - - - 状态同步 - - - 高风险或未决异常 - - - - - - - - - - 执行当前意图 - - - 超出能力边界 - 触发交接 - - - - - 接收交接请求 - - - 封装上下文与未决事项 - - - 风险路由 - - - - - - - - 交接包 (Payload) - - - • 上下文: ctx_98a2 - • 历史: 附带最近5轮 - • 未决: 需验证用户身份 - • 风险值: 待安全评估 - - - - - - 接收并确认交接包 - - - 无缝继续处理 - - - - - 转由人工介入处理 - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/11-agent-development-lifecycle.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/11-agent-development-lifecycle.svg deleted file mode 100644 index a0f2930e4..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/11-agent-development-lifecycle.svg +++ /dev/null @@ -1,107 +0,0 @@ - - - - - - - - - - - - - - - - - - Agent 开发全流程 - - - - - 需求与设计 - - - - 开发与评测 - - - - 部署与运维 - - - - - - - - - - - - - - - - 不通过，重新调整 - - - - 失败样本触发优化迭代 - - - - - - - - 1 - 场景定义 - - - - - 2 - 成功指标 - - - - - 3 - 方案设计 - - - - - 4 - Prompt 与 - Tool 实现 - - - - - 5 - 离线评测 - - - - - 6 - 真实流量 - 灰度发布 - - - - - 7 - 线上监控 - - - - - 8 - 失败样本 - 回流分析 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/12-prompt-development.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/12-prompt-development.svg deleted file mode 100644 index 09bbf5c43..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/12-prompt-development.svg +++ /dev/null @@ -1,92 +0,0 @@ - - - - - - - - - - - - - Prompt 开发与评测迭代闭环 - 标准化的模板编写、测试验证、自动化数据对比与人工 Review 流程 - - - - - - - - - - - - - - - - - - - - - - 指标下降 - - - - Review 不通过 - - - - 修改 Prompt 并重新评测 - - - - - 编写 / 修改模板 - Prompt 设定与调优 - - - - 样例测试 - 单样本初步验证 - - - - 固定评测集批量运行 - 自动化数据验证 - - - - 与基线对比 - 核心指标评估分析 - - - - 人工 Review - 边缘 Case 与体感审查 - - - - 版本发布 - 基线更替与对外输出 - - - - - - Prompt 版本 - - - - - 评测集版本 - - - - - 线上版本 - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/13-tool-mcp-integration.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/13-tool-mcp-integration.svg deleted file mode 100644 index 262fca37e..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/13-tool-mcp-integration.svg +++ /dev/null @@ -1,184 +0,0 @@ - - - - - - - - - - - - - - Agent Tool/MCP 接入时序流程 - - - - - Agent - - - - MCP Client - - - - Tool Server - - - - - - - - Phase 1: 需求与定义 - - - - - 业务需求与场景 - - - - Tool 服务实现 - - - - - - MCP Schema 定义 - - - - 服务权限配置 - - - - - - - - - - - - - Phase 2: 工具注册与联调 - - - - - 触发工具注册 - - - - 解析与注册 Tool - - - - 加载 Tool 能力 - - - - - 提交注册信息 - - - 暴露能力 - - - - - 发起联调验证 - - - - 转发与日志记录 - - - - 响应验证请求 - - - - - 测试调用 - - - RPC / HTTP - - - - - Phase 3: 运行期交互 - - - - - 发起 Tool 调用 - - - - 协议校验与路由 - - - - 执行核心逻辑 - - - - - Invoke Tool - - - 转发执行 - - - - - - 正常返回结果 - - - - 格式化响应 - - - - 消费响应数据 - - - - - Response - - - 返回标准结果 - - - - - Phase 4: 容错与降级 - - - - - - 超时错误处理 - - - - - 触发降级策略 - - - - - 等待请求超时 - 触发异常流程 - - - - 返回 Error 状态 - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/14-agent-evaluation-loop.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/14-agent-evaluation-loop.svg deleted file mode 100644 index f78900098..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/14-agent-evaluation-loop.svg +++ /dev/null @@ -1,118 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - 真实样本采集 - 线上日志 / 用户反馈 - - - - - - - - - 数据处理 - - - - 清洗 - - - - - - 脱敏 - - - - - - 标注 - - - - - - - - - 数据集版本化 - - Release v1.0.0 - 打标签锁定，确保基线一致 - - - - - - - - - 运行 Agent - 执行与生成结果 - - - - - - - - - 评测分析环节 - 闭环优化的核心步骤 - - - - - - 规则与模型评分 - 多维度评估 - - - - - - - - - 失败聚类 - 寻找共性特征 - - - - - - - - - 根因分析 - 定位 Bad Case - - - - - - - - - - 优化结果回流，形成新样本 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/15-agent-trace-debugging.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/15-agent-trace-debugging.svg deleted file mode 100644 index dad72bde9..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/15-agent-trace-debugging.svg +++ /dev/null @@ -1,136 +0,0 @@ - - - - - - - - - - - - - - 阶段 1: 节点识别 - - - - - 阶段 2: 载荷穿透分析 - - - - - 阶段 3: 诊断根因树 - - - - - - - - - - - - - - - - - - - - - 钻取数据 - - - - - - - - - - - - - - - 归因 - - - - - - - - - - - - - - - - - - - - - - 失败请求 / 报警 - - - - Trace 链路总览 - - - - 检查长耗时慢节点 - - - 定位异常报错节点 - - - - - - 核验 Prompt 组装与渲染 - - - - - 校验 Tool 传参与返回值 - - - - - 分析模型推理与 JSON - - - - - - Agent 编排与路由故障 - - - - - 下游工具与 API 异常 - - - - - 上下文缺失或 Prompt 缺陷 - - - - - 模型理解偏差与严重幻觉 - - - - 修复后回归验证 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/16-software-development-lifecycle.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/16-software-development-lifecycle.svg deleted file mode 100644 index 3d476ce53..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/16-software-development-lifecycle.svg +++ /dev/null @@ -1,121 +0,0 @@ - - - - - - - - - 软件研发全流程与产物门禁 - - - - - - - - - - - - - - - - - Phase 01 - 需求提出 - - - 关键产物 - 原始需求池 - - - - - - Phase 02 - 需求评审 - - - 门禁条件 - PRD 定稿基线 - - - - - - Phase 03 - 技术设计 - - - 关键产物 - 技术设计文档 - - - - - - Phase 04 - 开发阶段 - - - 关键产物 - 功能代码提交 - - - - - - Phase 05 - 代码评审 - - - 门禁条件 - CR 通过准入 - - - - - - Phase 06 - 测试验证 - - - 关键产物 - 测试通过报告 - - - - - - Phase 07 - 灰度发布 - - - 门禁条件 - 灰度指标达标 - - - - - - Phase 08 - 全量上线 - - - 门禁条件 - 线上故障清零 - - - - - - Phase 09 - 监控复盘 - - - 关键产物 - 业务洞察报告 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/17-requirement-to-design.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/17-requirement-to-design.svg deleted file mode 100644 index 5260fb7c3..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/17-requirement-to-design.svg +++ /dev/null @@ -1,119 +0,0 @@ - - - - - - - - - - - - - - 需求到技术方案流程图 - - - - 阶段一：需求与风险对齐 - - - 阶段二：技术方案设计与确认 - - - - - - - - - - - 产 - 品 - - - - - 研 - 发 - - - - - 测 - 试 - - - - - - - - - - - - - - - - - - - - - - 需求变更 / 不通过 - - - 评审需修改 - - - - - - 需求澄清 - 对齐业务痛点与目标 - - - - 范围确认 - 划定MVP核心边界 - - - - 风险识别 (技术) - 评估架构可行性 - - - - 风险识别 (质量) - 识别质量保障难点 - - - - 需求评审 - 产研测三方达共识 - - - - 技术调研 - 核心难点选型评估 - - - - 方案编写 - 系统架构与接口设计 - - - - 方案评审 - 技术架构内部Review - - - - 修改确认 - 方案定稿与排期计划 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/18-tdd-cycle.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/18-tdd-cycle.svg deleted file mode 100644 index b69928dd6..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/18-tdd-cycle.svg +++ /dev/null @@ -1,67 +0,0 @@ - - - - - - - - - - - - TDD - CYCLE - - - - - - - - - 编写最小实现 - - - - 保持测试通过 - - - - 添加下一个测试 - - - - 任何测试失败 - - - - - - - 写一个失败测试 - - - - - Red - - 失败的测试 - - - - - - Green - - 测试通过 - - - - - - Refactor - - 代码重构 - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/19-git-pr-review.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/19-git-pr-review.svg deleted file mode 100644 index 38be0de14..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/19-git-pr-review.svg +++ /dev/null @@ -1,125 +0,0 @@ - - - - - - - - - - Git Feature Branch & PR Review 泳道图 - - - - - - - - - - - - 开发者 - Developer - - 自动集成 - CI - - 审核人 - Reviewer - - - - - - - - - - - - - - - - - - - - - - - - 触发检查 - 通过 (Pass) - 自动触发 - - 检查失败 (Fail) - 需修改 (Needs Work) - - - - - - - 创建分支 - Create branch - - - - - - 提交代码 - commit - - - - - - 推送到远端 - push - - - - - - 发起合并请求 - Create PR - - - - - - 自动检查 - Auto Check - - - - - - 人工 Review - Manual Review - - - - - - 审核批准 - Approve - - - - - - 合并代码 - merge - - - - - - 删除分支 - Delete branch - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/20-cicd-release.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/20-cicd-release.svg deleted file mode 100644 index e7963ad73..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/20-cicd-release.svg +++ /dev/null @@ -1,144 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - 持续集成阶段 (Continuous Integration) - 代码提交 -> 构建 -> 自动化测试 -> 安全扫描 - - - - 持续部署阶段 (Continuous Deployment) - 部署测试 -> UAT验收 -> 小流量灰度 -> 全量发布 - - - - - - 核心枢纽节点 - - - - - - - - - 触发 - - - - - 通过 - - - - - 达标扩量 - - - - - - - - - - - - - 部署相同制品 (Pull Artifact) - - - - - - - - - - - 指标异常 - - - 验收不通过 - - - - 代码回滚与重新触发修复 - - - - - - - 代码提交 - Commit - - - - 项目构建 - Build - - - - 单元测试 - Unit Test - - - - 安全扫描 - Sec Scan - - - - - - 唯一制品 - Artifact - 不可重复构建 - - - - 部署测试 - Test Env - - - - - 验收通过? - UAT Gate - - - - 灰度发布 - Canary - - - - - 指标正常? - Monitor - - - - 全量发布 - Rollout - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/21-layered-architecture.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/21-layered-architecture.svg deleted file mode 100644 index 54e0156e7..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/21-layered-architecture.svg +++ /dev/null @@ -1,176 +0,0 @@ - - - - - - - - - - - - - - - - - 经典分层系统架构 - 遵循自上而下严格依赖与管控的旁路直通能力设计 - - - - - - - - - 客户端层 - Client Layer - - - - Web 客户端 - - - 移动端 App - - - 开放平台 (Open API) - - - - - - 接入层 - API Gateway - - - - 负载均衡 (LB) - - - API 网关 (流量入口) - - - 身份与认证网关 - - - - - - 应用层 - Application Layer - - - - 交易聚合服务 - - - 用户支撑服务 - - - 消息路由分发 - - - - - - 领域层 - Domain Layer - - - - 订单领域模型 - - - 会员等级领域 - - - 事件通知策略 - - - - - - 基础设施层 - Infrastructure - - - - 分布式缓存 (Redis) - - - 消息队列 (MQ) - - - 调度执行器 - - - - - - 数据存储层 - Data Storage - - - - 关系型数据库 (MySQL) - - - 文档数据库 (NoSQL) - - - 对象存储 (OSS) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 客户端文件直传 - 旁路鉴权接口通道 - - - - - - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/22-monolith-to-microservices.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/22-monolith-to-microservices.svg deleted file mode 100644 index f0e0a0151..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/22-monolith-to-microservices.svg +++ /dev/null @@ -1,241 +0,0 @@ - - - - - - - - - - - - - - 单体到微服务架构演进图 - 从单一进程向高内聚、低耦合的分布式自治架构平滑演进 - - - - 1. 单体应用 - - - - 单体大容器 - - - - 前端应用 UI - - - - 业务逻辑 (紧耦合无明显边界) - - - - 模块 A - - 模块 B - - 模块 C - - - - 单一关系型数据库 - - - - - - - - - 2. 模块化单体 - - - 单体大容器 - - - 前端应用 UI - - - - - 逻辑边界 - - - - 模块 A - - 模块 B - - 模块 C - - - 单一关系型数据库 - - - - - - - - - 3. 抽离共享能力 - - - - 瘦身后的核心系统 - - - 前端应用 UI - - - - 核心业务 - - - 模块 A - - 模块 B - - - 主数据库 - - - - 共享服务 - (独立进程) - - - - 共享 DB - - - - - - - - - - - - - - 4. 按领域拆解服务 - - - - API 路由网关 - - - - 领域 - 服务 A - - - 领域 - 服务 B - - - - 共享 - 服务 - - - - 分布式数据库集群 - (按域逻辑隔离) - - - - - - - - - - - - - - 5. 独立数据与治理 - - - - 平台治理控制面 - (微服务网关 / 服务网格 / 鉴权中心) - - - - 领域 - 服务 A - - - 领域 - 服务 B - - - - 共享 - 域服务 - - - - 独立 - DB A - - - 独立 - DB B - - - 专属 - 存储 - - - - - - - - - - - - - - - - - - - - - - - - 阶段一：业务起步 - 全量代码/资源强耦合，敏捷快跑 - - - 阶段二：结构化分离 - 代码内部划定边界，降低修改冲突 - - - 阶段三：能力沉淀 - 通用能力下沉，提升业务复用率 - - - 阶段四：全面微服务化 - 按业务域垂直拆分，进程级物理隔离 - - - 阶段五：平台化与自治 - 独立数据资产，引入网格与全局治理 - - - - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/23-microservice-gateway.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/23-microservice-gateway.svg deleted file mode 100644 index aa4fa0372..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/23-microservice-gateway.svg +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - - - - - - - - - - Client Applications - - - - - - - API Gateway - - - - - Cache - Access - - - - - - - Telemetry - & Metrics - - - - - - - - - - - User Domain - - - User Service - - - [DB] User DB - - - - - Event - - - - Order Domain - - - Order Service - - - [DB] Order DB - - - - - Event - - - - Inventory Domain - - - Inventory Service - - - [DB] Inv DB - - - - - Event - - - - - - - - Sync API - - - Sync API - - - - - Message Bus (Kafka / RabbitMQ) - - - - - - - Distributed Cache Layer (Redis) - - - - - - - Observability Platform (Metrics / Tracing / Logs) - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/24-plugin-architecture.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/24-plugin-architecture.svg deleted file mode 100644 index 84af0c97b..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/24-plugin-architecture.svg +++ /dev/null @@ -1,132 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - 统一契约 (Unified Contract) - 定义标准化接口：注册 · 加载 · 执行 · 卸载 - - - - - - - - - - Core Host - - - - - - - - - Extension API - - - - - - - - Plugin Registry - - - - - - - 权限隔离 - Permission Isolation - - - 沙箱隔离 - - 资源鉴权 - - 拦截保护 - - - - - - - 生命周期管理 - Lifecycle Management - - - 注册 - - 加载 - - 执行 - - 卸载 - - - - - - - - - - - - - - - - - - - - - - - - - - Plugin A - - - - - - Plugin B - - - - - - Plugin C - - - - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/25-agent-platform.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/25-agent-platform.svg deleted file mode 100644 index 2aa39d4b6..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/25-agent-platform.svg +++ /dev/null @@ -1,191 +0,0 @@ - - - - - - - - - - - - - Agent 平台整体架构图 - - - - - - - - - 接入层 - - - - - 编排层 - - - - - 底座层 - - - - - - - 应用入口 - - - Web UI - - - API 接口 - - - SDK 接入 - - - 企微 / 钉钉 - - - - - - - Agent 编排 - Orchestration - - - 意图识别 - 意图与槽位提取 - - - 任务规划 - DAG 与依赖解析 - - - Prompt 组装 - 上下文模板构建 - - - 多轮控制 - 状态机与会话路由 - - - - - - - - - 模型服务 - - 大语言模型 (LLM) - - Embedding 模型 - - - - 知识检索 - - 向量相似度查询 - - 混合检索 (RAG) - - - - 工具平台 - - 内置 API 插件 - - 外部沙盒执行 - - - - 记忆服务 - - 短期会话 (Session) - - 长期记忆 (Vector) - - - - - - - 数据存储 - Infrastructure - - - 关系型数据库 - - - 向量数据库 - - - 对象存储 - - - 缓存与日志 - - - - - - - 运行与评测 - - - - 链路追踪 - - - 日志监控 - - - 质量评测 - - - 版本与模型管理 - - - 权限与安全 - - - 统计分析报表 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/26-synchronous-sequence.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/26-synchronous-sequence.svg deleted file mode 100644 index ec9f3d48e..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/26-synchronous-sequence.svg +++ /dev/null @@ -1,99 +0,0 @@ - - - - - - - - - - - - - 同步调用时序图 - - - - - - - - - - - - alt - [外部服务正常] - - - [请求超时] - - - - - 调用方 - - - API 网关 - - - 业务服务 - - - 数据库 - - - 外部服务 - - - - - - - - - - - - - 1. 发起同步请求 - - - - 2. 鉴权通过并路由 - - - - 3. 读取业务上下文 - - - - 4. 返回数据 - - - - 5. 同步调用外部服务 - - - - 6. 成功响应 - - - - 7. 写入最终结果 - - - - 8. 同步业务响应 - - - - 9. 返回 200 OK - - - - - - 10. 返回 504 Gateway Timeout - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/27-asynchronous-sequence.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/27-asynchronous-sequence.svg deleted file mode 100644 index 948694388..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/27-asynchronous-sequence.svg +++ /dev/null @@ -1,133 +0,0 @@ - - - - - - - - - - - - - - - - - 异步事件处理时序图 - 含幂等检查、正常业务落库流程、失败重试及死信队列(DLQ)降级机制 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 生产者 (Producer) - - - - Broker - - - - 消费者 (Consumer) - - - - 数据库 (Database) - - - - 死信队列 (DLQ) - - - - - - - 1. 发布事件消息 (Publish) - - - - 2. Broker 确认接收 (ACK) - - - - 3. 异步投递 / Consumer 拉取 - - - - 4. 执行幂等性防重检查 - - - - - - - - - - alt - [ 检查通过，执行正常业务流 ] - - - - 5. 业务操作入库 (Transaction) - - - - 6. 落库成功与结果返回 - - - - 7. 成功消费确认 (ACK) - - - - [ 处理异常与内部延迟重试 ] - - - - 8. 抛出异常，执行内部等待及重试 (Retry) - - - - [ 重试次数达上限，启动降级保护 ] - - - - 9. 路由投递至死信队列 (DLQ) - - - - 10. 死信写入成功 - - - - 11. 提交最终偏移量 / NACK 丢弃 - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/28-human-agent-swimlane.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/28-human-agent-swimlane.svg deleted file mode 100644 index 1771ed159..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/28-human-agent-swimlane.svg +++ /dev/null @@ -1,132 +0,0 @@ - - - - - - - - - - - - - - 人机协作自动化处理流程 - AI 风险研判与人工干预无缝交接 - - - - - - - - - - - - - - - - - - 用 户 - - - - - 业务系统 - - - - - 智能 Agent - - - - - 人工审核 - - - - - - - - - - - - - - - - - - - - - - - - 低风险 - - - - 高风险 - - - - - - - 提交请求 - 发起业务流程 - - - - - - 系统受理 - 记录并调度 - - - - - - 智能分析 - 意图与特征提取 - - - - - 风险判定 - - - - - 自动处理 - 极速放行执行 - - - - - - 人工审批 - 复杂案件介入 - - - - - - 结果汇总 - 状态更新及流转 - - - - - - 接收结果 - 业务流程闭环 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/29-task-state-machine.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/29-task-state-machine.svg deleted file mode 100644 index 3b524e45e..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/29-task-state-machine.svg +++ /dev/null @@ -1,101 +0,0 @@ - - - - - - - - - - - - - - 任务生命周期状态机 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 开始 - - - 等待外部结果 - - - 收到结果 - - - 执行成功 - - - 超时 - - - 执行失败 - - - 取消 - - - 重试 - - - - - - Created - - - - - - Running - - - - - - Waiting - - - - - - Failed - - - - - Succeeded - - - - - Cancelled - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/30-retry-compensation.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/30-retry-compensation.svg deleted file mode 100644 index de266bec8..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/30-retry-compensation.svg +++ /dev/null @@ -1,141 +0,0 @@ - - - - - - - - - - - - - - - - - - - 异常分类与处理策略 (Exception Classification & Fallback Zone) - - - - - - - - 成功 (Success) - - - - 异常 (Exception) - - - - - - 超过重试阈值 - - - - 发起重试 (Max Retries & Backoff) - - - - - - - - - - - - - - - 成功 - - - 失败 - - - - - - - - - 触发执行 - - - - 执行核心业务 - (Execute Task) - - - - 状态 - - - - 业务成功 - - - - - 瞬时错误 - (网络抖动/超时) - - - - 退避重试 - (Backoff Retry) - - - - 系统异常终止 - - - - - 依赖不可用 - (下游熔断/限流) - - - - 服务降级 - (返回默认值/缓存) - - - - 降级成功 - - - - - 业务逻辑失败 - (数据校验不通过等) - - - - 业务补偿 - (逆向回滚/状态重置) - - - - 校验 - - - - 补偿成功 - - - - 触发告警 - 及人工介入 - - - - 待人工干预 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/31-data-pipeline.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/31-data-pipeline.svg deleted file mode 100644 index ea95b96ff..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/31-data-pipeline.svg +++ /dev/null @@ -1,163 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - 接入与预处理层 - - - 计算处理层 - - - 数据汇聚与存储 - - - 数据应用层 - - - - - 数据清洗与加工组 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 原始数据 - - - - 标准数据 - - - - 聚合数据 - - - - - - - - - - 多源数据系统 - (DB, API, Log) - - - - - - - - 数据采集 - Ingestion - - - - - 数据清洗 - Cleaning - - - - - 标准化 - Standard - - - - - - - - 实时流处理 - 高吞吐、低延迟计算 - - - - - - 离线批处理 - 海量规模复杂计算 - - - - - - - - 数据湖 Data Lake - 海量半结构化汇聚 - - - - - - 数仓 Data Warehouse - 结构化、高性能查询 - - - - - - - - 在线服务系统 - 推荐、风控、API分发 - - - - - - 分析与报表系统 - BI 仪表盘与决策分析 - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/32-data-lineage.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/32-data-lineage.svg deleted file mode 100644 index c313633e1..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/32-data-lineage.svg +++ /dev/null @@ -1,180 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 数据源 (Source) - 处理任务 (Process) - 数据模型 (Model) - 数据消费 (Consume) - - - - - - - - - - - - - - - - - - - - - - - - - 源表: src_user_profile - 引发源: 字段 user_id 变更 - (由 Int 变更为 String 类型) - - - - - - 源表: src_order_detail - 表结构未变更 - 正常产出 order_id, amount - - - - - - 任务: sync_user_data - 异常波及: 核心流式解析失败 - 类型不兼容，导致任务熔断 - - - - - - 任务: join_user_order - 异常波及: 离线关联查询报错 - Join 字段类型冲突无法匹配 - - - - - - 任务: agg_daily_sales - 销售额聚合任务产出正常 - 逻辑不涉及被破坏的 user_id - - - - - - 宽表: dwd_user_order - 数据异常: 核心主表产出延迟 - 上游中断，下游数据大面积空缺 - - - - - - 指标: dws_sales_summary - 按天交易额指标更新正常 - 未依赖受污染模型的宽表 - - - - - - 报表: User Activity BI - 展现报错: 活跃用户分析大盘 - 底层空表及类型错乱，图表崩溃 - - - - - - API: User Profile Svc - 服务熔断: 画像查询反序列化报错 - 读取数据超时，接口大面积降级 - - - - - - 报表: Sales Dashboard - 销售业务大盘展示正常 - 核心指标无数据缺失与延迟 - - - - - 字段变更波及链路 - - - - 未受影响的常规链路 - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/33-er-model.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/33-er-model.svg deleted file mode 100644 index 22bd06680..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/33-er-model.svg +++ /dev/null @@ -1,253 +0,0 @@ - - - - - - - - - - - - 系统实体关系图 (ER Diagram) - 展示用户、项目、任务、执行记录与结果的数据从属与衍生关系 - - - - - - - - - - - - - 用户 (User) - - - - - - - - - - PK - id - int - - - - username - varchar - - - - email - varchar - - - - status - tinyint - - - - - - - - - - - - - 项目 (Project) - - - - - - - - - - PK - id - int - - - - FK - user_id - int - - - - name - varchar - - - - created_at - datetime - - - - - - - - - - - - - 任务 (Task) - - - - - - - - - - PK - id - int - - - - FK - project_id - int - - - - title - varchar - - - - status - tinyint - - - - - - - - - - - - - 执行记录 (Record) - - - - - - - - - - PK - id - int - - - - FK - task_id - int - - - - start_time - datetime - - - - end_time - datetime - - - - - - - - - - - - - 结果 (Result) - - - - - - - - - - PK - id - int - - - - FK - record_id - int - - - - output_data - json - - - - success - boolean - - - - - - - - - - 1 - - N - - - - - 1 - - N - - - - - 1 - - N - - - - - 1 - - 1 - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/34-domain-model.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/34-domain-model.svg deleted file mode 100644 index 1d1910267..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/34-domain-model.svg +++ /dev/null @@ -1,93 +0,0 @@ - - - - - - - - - - - - - Aggregate Boundary - - - - - - - - - - - - - - - - publishes - - - - - - - - - - - - - <<Aggregate Root>> - Task - - - id: String - - steps: List<Step> - - status: Status - - + complete() - - - - <<Entity>> - Step - - - stepId: String - - title: String - - + update() - - - - <<Value Object>> - Status - - - value: String - - + isCompleted() - - - - <<Domain Event>> - TaskCompleted - - - taskId: String - - timestamp: Date - - - - <<Domain Service>> - TaskService - - + createTask() - + completeTask() - - - - <<Repository>> - TaskRepository - - + findById(id): Task - + save(Task) - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/35-cache-consistency.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/35-cache-consistency.svg deleted file mode 100644 index 712caee2a..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/35-cache-consistency.svg +++ /dev/null @@ -1,152 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - 读流程 (Read Flow) - - - - - 发起读请求 - Client Request - - - - 查询缓存 - Query Redis - - - - 缓存命中? - - - - 直接返回数据 - Return Cache Data - - - - 查询数据库 - Query MySQL - - - - 返回真实数据 - Return DB Data - - - - 回填缓存 - Set Redis Cache - - - - - - - - Y 命中 - - - - N 未命中 - - - - - - - - - - 异步/同步更新数据 - - - - - - - - - 写流程 (Write Flow) - - - - - 发起写请求 - Client Request - - - - 更新数据库 - Update MySQL - - - - 操作缓存 - Del / Set Redis - - - - 操作成功? - - - - 完成写入 - Return Success - - - - 发送补偿消息 - Produce to MQ - - - - 异步重试 / 告警 - Consume & Retry - - - - 并发控制：推荐结合 延迟双删 或 分布式锁 防脏数据 - - - - - - - - - - - - Y 成功 - - - - N 失败 - - - - - - - MQ 触发最终一致性重试 - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/36-observability-loop.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/36-observability-loop.svg deleted file mode 100644 index f7e8187ab..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/36-observability-loop.svg +++ /dev/null @@ -1,145 +0,0 @@ - - - - - - - - - - - - - - - - - 可观测性闭环架构图 - - - - - - 数据产生 - Data Generation - - - - - 处理与分析 - Process & Observe - - - - - 响应与行动闭环 - Action & Response - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 验证结果反馈到规则和服务 - - - - - - - - 业务服务 - Services - - - - - 指标 - Metrics - - - - - 日志 - Logs - - - - - Trace - Tracing - - - - - 采集 - Collector - - - - - 存储分析 - Storage - - - - - 数据看板 - Dashboard - - - - - 监控告警 - Alerting - - - - - 值班响应 - Response - - - - - 定位分析 - Root Cause - - - - - 故障修复 - Recovery - - - - - 闭环验证 - Verification - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/37-incident-response.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/37-incident-response.svg deleted file mode 100644 index 791e80f92..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/37-incident-response.svg +++ /dev/null @@ -1,191 +0,0 @@ - - - - - - - - - - - - - - - - - 线上故障响应与处理泳道图 - - - - - 常规流转 - - - 条件分支 - - - 高优 / 核心动作 - - - - - - - - - - - - - - - 监控平台 - Monitor - - - - - 值班工程师 - On-call - - - - - 故障指挥 - Commander - - - - - 业务团队 - Business - - - - - - - - - - - - - L3/L4 故障 - - - - - - - - L1/L2 升级 - - - - - - - - 分发动作 - - - - - 全阶段信息同步 - - - - - - - - - - - - - - - - - - - - 告警规则触发 - - - - - - 认领并响应告警 - - - - - - 故障定级 - 评估 - - - - - - 常规排查处理 - (独立闭环) - - - - - - 拉起紧急作战室 - (指挥调度) - - - - - - 全局调度与通报 - (信息同步) - - - - - - - - ! - - 优先紧急止损 - (熔断/降级/回滚) - - - - - - 根因排查与定位 - - - - - - 实施修复方案 - - - - - - 业务指标验证 - (确认恢复) - - - - - - 故障复盘总结 - (改进项追踪) - - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/38-resilience-control.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/38-resilience-control.svg deleted file mode 100644 index 2d7442f80..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/38-resilience-control.svg +++ /dev/null @@ -1,112 +0,0 @@ - - - - - - - - - - - - - 服务韧性控制流程 (Service Resiliency Control) - 容量检查 · 依赖监控 · 熔断降级 - - - - 熔断状态机 (Circuit Breaker) - - - - - - - - 否 (请求超限) - - - - 是 (充足) - - - - 是 (健康) - - - - - - - 否 (非核心依赖异常) - - - - 否 (核心依赖异常) - - - - 熔断期满 - - - - 探测成功 - - - - 探测失败 (继续阻断) - - - - - - - 外部请求 - - - - 容量充足？ - Capacity - - - - 依赖健康？ - Health - - - - - - - 限流 - Rate Limit - - - - 正常放行 - Pass - - - - 降级 - Fallback - - - - - - - 熔断 - Open State - - - - 半开探测 - Half-Open - - - - 恢复 - Closed State - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/39-authentication-authorization.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/39-authentication-authorization.svg deleted file mode 100644 index fe2fdb99e..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/39-authentication-authorization.svg +++ /dev/null @@ -1,118 +0,0 @@ - - - - - - - - - 认证授权时序与信任边界图 - - - - - 外部信任区 - - - - 身份管控区 - - - - 内部受信任区 - - - - - - - - - - - - - - - 用户 (User) - - - - 客户端 (Client) - - - - 身份提供方 (IdP) - - - - API 网关 - - - - 策略引擎 - - - - 资源服务 - - - - - - - - - - - - - - - - - - - - - - - 1. 发起访问 - - - - 2. 登录跳转 (OIDC/OAuth2) - - - - 3. 用户身份认证交互 (Credentials) - - - - 4. 回调 & Token 签发 (Issue Token) - - - - 5. 携带 Token 请求业务 API - - - - 6. Token 校验 & 权限决策 - - - - 7. 决策结果 (Decision: Allow) - - - - 8. 转发授权请求 - - - - 9. 资源响应 (Resource Response) - - - - 10. 返回 API 数据 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/40-sensitive-operation-approval.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/40-sensitive-operation-approval.svg deleted file mode 100644 index 5d3b17cda..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/40-sensitive-operation-approval.svg +++ /dev/null @@ -1,141 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 申请人 - 系统 - 风险引擎 - 审批人 - 审计平台 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 通过 - - - - 无权限 - - - - 有权限 - - - - 低风险 - - - - 高风险 - - - - 拒绝 - - - - 通过 - - - - - - - 发起操作 - - - - 身份校验 - - - - 权限校验 - - - - 风险评估 - - - - 人工审批 - - - - 拒绝请求 - - - - 允许执行 - - - - 记录审计 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/41-learning-roadmap.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/41-learning-roadmap.svg deleted file mode 100644 index c9e6c7f75..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/41-learning-roadmap.svg +++ /dev/null @@ -1,128 +0,0 @@ - - - - - - - - - - - - - 通用技术学习路线图 - 从基础认知到深入实践的核心路径 - - - - - - - - 1 - 前置知识 - - - 编程语言基础 - - - 运行环境搭建 - - - - - - - - - - 2 - 基础概念 - - - 核心语法与规范 - - - 常用数据结构 - - - 基础工具库 - - - - - - - - - - 3 - 核心机制 - - - 并发与异步处理 - - - 内存管理与回收 - - - - - - - - - - 4 - 项目实战 - - - 业务需求拆解 - - - 核心模块开发 - - - 工程化构建部署 - - - - - - - - - - 5 - 性能调优 - - - 性能瓶颈定位 - - - 资源调度优化 - - - 自动化监控告警 - - - - - - - - - - 6 - 深入专题 - - - 底层源码剖析 - - - 架构模式设计 - - - 行业前沿探索 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/42-knowledge-mindmap.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/42-knowledge-mindmap.svg deleted file mode 100644 index 980ebe240..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/42-knowledge-mindmap.svg +++ /dev/null @@ -1,160 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 核心概念 - - - 工作原理 - - - 关键组件 - - - - 实践方法 - - - 常见问题 - - - 生态工具 - - - - - - - - - - - - - - - - - - - - 基础定义 - 核心架构 - 演进历程 - - 请求链路 - 数据流转 - 调度机制 - - 接入网关层 - 计算处理组 - 底层存储库 - - - - - - - - - - - - - - - - - - - - 部署方案 - 性能调优 - 安全策略 - - 网络抖动 - 内存溢出 - 数据防丢 - - CLI 工具 - 可视化面板 - 官方插件库 - - - - - 某技术 - 全景知识脑图 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/43-concept-dependency.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/43-concept-dependency.svg deleted file mode 100644 index f709f88bc..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/43-concept-dependency.svg +++ /dev/null @@ -1,100 +0,0 @@ - - - - - - - - - - - - - - 概念依赖 DAG 模板 - - - 基础层 - 中间层 - 高阶层 - - - - - - - - - - - - - - - - - - 对比 - - - 对比 - - - - - - - 基础概念 A - - - 提供底层数据与前置 - 计算逻辑支撑 - - - - - 基础概念 B - - - 作为核心依赖模块 - 保障流转的独立性 - - - - - 中间概念 C - - - 汇聚上游依赖，完成 - 初级业务形态转换 - - - - - 中间概念 D - - - 加工组合底层元素， - 抽象出中阶语义 - - - - - 高阶概念 E - - - 沉淀顶层业务价值， - 对外输出统一接口 - - - - - - 前置依赖 (主干) - - - 组成关系 (成分) - - - 相关/对比 - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/44-mechanism-breakdown.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/44-mechanism-breakdown.svg deleted file mode 100644 index 8a83cc342..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/44-mechanism-breakdown.svg +++ /dev/null @@ -1,114 +0,0 @@ - - - - - - - - - - - - - - - - 核心内部处理模块组 (Core Engine) - 提供隔离的计算环境，各阶段模块解耦并共享上下文状态 - - - - - - 原始输入 - Raw Data - - - - 预处理 - 参数清洗与校验 - - - - 阶段 I: 解析 - 结构化重组 - - - 阶段 II: 计算 - 核心业务逻辑 - - - 阶段 III: 转换 - 产物协议适配 - - - - 中间结果 - Intermediate - Data Snapshot - - - - 共享状态字典 (Shared Context / State) - 提供跨模块的实时数据共享、缓存支持与状态追踪 - - - - 后处理 - 结果过滤与封装 - - - - 最终输出 - Final Result - - - - 关键不变量 (Key Invariants) - - - 1. 状态一致性保证 - 事务隔离，确保失败时数据回滚 - - 2. 数据流严格单向 - 控制流不可逆，降低耦合复杂度 - - - - - - 进入 - - - 分发调度 - - - - - - 聚合 - - - 提取产物 - - - 响应 - - - - - 读/写 - - - - 读/写 - - - - 读/写 - - - - 更新 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/45-one-picture-overview.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/45-one-picture-overview.svg deleted file mode 100644 index b4dfad6da..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/45-one-picture-overview.svg +++ /dev/null @@ -1,140 +0,0 @@ - - - - - - - - - - 一句话定义 - - - 模板占位：在此处用一句话简明扼要地描述该技术的核心本质、定位与解决的主要问题。 - 例如：一种基于流批一体架构的高效异构数据流转、清洗过滤与实时计算处理方案。 - - - - 核心组件 - Core Components - - - - - - 组件 A: 数据入口网关 - 负责高吞吐量多源并发接入与初始格式校验 - - - - - - 组件 B: 实时处理引擎 - 提供极低延迟的流式分析与复杂事件计算能力 - - - - - - 组件 C: 分布式存储池 - 保障异构数据的多副本持久化分层存储与检索 - - - - 工作流程 - Workflow Pipeline - - - - - - 01 采集 - - 多数据源实时抽取接入 - - - - 流转 - - - - - - 02 过滤 - - 脏数据清洗与去重处理 - - - - 解析 - - - - - - 03 分析 - - 核心聚合与复杂事件计算 - - - - 输出 - - - - - - 04 呈现 - - 业务指标与可视化大屏 - - - - 校验失败 - - - - - 异常处理 - - 拦截并记录异常错误日志 - - - - 典型场景 - Scenarios - - - - 场景 A: 金融级高并发实时流处理与风控监控 - - - - 场景 B: 跨地域大规模多节点离线数据同步 - - - - 主要优点 - Advantages - - - - 优势 A: 毫秒级端到端极低系统延迟与高效吞吐 - - - - 优势 B: 基于云原生容器的无缝动态弹性扩缩容 - - - - 限制与注意事项 - Limitations - - - - 限制 A: 对跨 IDC 网络专线带宽质量与抖动要求极高 - - - - 限制 B: 强一致性事务要求场景下可能引发性能退化 - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/46-architecture-evolution.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/46-architecture-evolution.svg deleted file mode 100644 index f439bb96a..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/46-architecture-evolution.svg +++ /dev/null @@ -1,210 +0,0 @@ - - - - - - - - - - - - - - - - 系统架构阶段演进路线图 - 核心结构、主要驱动力与新引入能力的演化模型 - - - - - - - 01 - 快速起步 - - - - 核心结构 - - - 单体应用架构体系 - - 集中式单节点数据库 - - - 主要驱动力 - - - 快速验证核心业务模型 - - 追求最短产品上线周期 - - - 新引入能力 - - - 基础增删改查(CRUD) - - 简单的用户权限管控 - - 本地业务日志记录 - - - - - - - - - - 02 - 模块化 - - - - 核心结构 - - - 垂直分层与模块解耦 - - 数据库分库分表拆分 - - - 主要驱动力 - - - 业务膨胀导致结构臃肿 - - 多团队并行协作防冲突 - - - 新引入能力 - - - 业务代码按领域域拆分 - - 引入本地缓存降低延迟 - - 主从数据库读写分离 - - - - - - - - - - 03 - 服务化 - - - - 核心结构 - - - 微服务架构(MSA) - - 引入异步消息中间件 - - - 主要驱动力 - - - 突破单体系统性能瓶颈 - - 应对高并发与大流量 - - - 新引入能力 - - - 高性能 RPC 远程调用 - - Redis 集中式分布式缓存 - - 全局链路追踪与监控 - - - - - - - - - - 04 - 平台化 - - - - 核心结构 - - - 大中台微前台企业架构 - - 容器化集群编排(K8s) - - - 主要驱动力 - - - 消除跨业务线重复建设 - - 大幅提升基础资源复用率 - - - 新引入能力 - - - 统一 API 流量网关路由 - - 自动化 CI/CD 部署流水线 - - 全局分布式任务调度框架 - - - - - - - - - - 05 - 智能化 - - - - 核心结构 - - - AI Native 融合智能架构 - - 湖仓一体流批数据处理 - - - 主要驱动力 - - - 深度挖掘海量数据价值 - - 数据驱动赋能业务创新 - - - 新引入能力 - - - 机器学习模型托管与推理 - - 实时复杂事件流计算引擎 - - 基于负载的自动弹性扩缩 - - - - 系统演进时间推移方向 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/47-project-milestones.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/47-project-milestones.svg deleted file mode 100644 index 82592796a..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/47-project-milestones.svg +++ /dev/null @@ -1,212 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - 前期规划阶段 - 研发攻坚阶段 - 上线交付阶段 - - - 调研 - 设计 - 开发 - 联调 - 灰度 - 发布 - - - - - - 基础建设 - Platform Env - - - - - 业务接入 - Business Line - - - - - - - - - - - - - - - - - - - - - - - - 阻塞依赖 - - - 版本汇合 - - - - - - - - 架构调研 - - - 技术栈选型 - - 可行性验证 - - - - 业务梳理 - - - 核心场景定义 - - 需求边界划分 - - - - - 系统设计 - - - 接口与契约 - - 底层数据模型 - - - - 交互/UI - - - 页面原型设计 - - 用户体验闭环 - - - - - 核心开发 - - - 通用组件沉淀 - - 基础服务开发 - - - - 逻辑开发 - - - 核心逻辑实现 - - 视图页面渲染 - - - - - 服务提供 - - - 接口联调可用 - - 测试环境就绪 - - - - 业务联调 - - - 依赖基建跑通 - - 全链路联调测 - - - - - 基建灰度 - - - 基础性能监控 - - 资源弹性扩容 - - - - 业务内测 - - - 种子用户体验 - - 需求反馈闭环 - - - - - 基建全量 - - - 生产环境部署 - - 平台稳定保障 - - - - 业务全量 - - - 对外正式发布 - - 运营活动支撑 - - - - - - - - - - - - - - - - - - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/48-technology-selection.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/48-technology-selection.svg deleted file mode 100644 index e7c9cd7b8..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/48-technology-selection.svg +++ /dev/null @@ -1,164 +0,0 @@ - - - - - - - - - - - - - 系统级架构选型决策树 - 通过评估业务规模、一致性、实时性与运维成本，推导最适配的架构形态 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 极高 / 核心链路 - - - - 中低 / 敏捷业务 - - - - 要求强一致 (事务级) - - - - 允许最终一致性 - - - - 毫秒级极速 - - - - 宽容 / 秒级离线 - - - - 无专职运维 / 求托管 - - - - 资深团队 / 强自控 - - - - - - - - - 规模与复杂度 - - - - 一致性要求 - - - - 实时性要求 - - - - 团队经验与运维 - - - - - - - - - - - 方案 A：强基建高可用架构 - - - 适用：金融交易 / 零丢数据核心系统 - - - 适用：团队具备深厚底座运维经验 - - - 风险：基础设施成本偏高 - - - 风险：重度耦合架构，扩容周期较长 - - - - - - - 方案 B：高性能实时架构 - - - 适用：读写吞吐极高 / 延迟极度敏感 - - - 适用：允许阶段性数据不一致 - - - 风险：引入过多组件，排查链路拉长 - - - 风险：极端下需应用层手动对齐数据 - - - - - - - 方案 C：轻量级托管架构 - - - 适用：业务快速试错 / 结构迭代频繁 - - - 适用：无专职运维，追求极速上线 - - - 风险：深度绑定特定厂商 Serverless 生态 - - - 风险：遇底层疑难杂症时排查受限 - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/49-capability-map.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/49-capability-map.svg deleted file mode 100644 index 0810daf12..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/49-capability-map.svg +++ /dev/null @@ -1,202 +0,0 @@ - - - - - - - - - 业务目标 - - - - - - 提升研发效能 - - - 保障系统稳定 - - - 沉淀数据资产 - - - 加速业务创新 - - - - - - - - - 接 入 - Access Domain - - - - - API 网关 - API Gateway - - 成熟 - - - - 统一鉴权 - Auth Center - - 成熟 - - - - 流量控制 - Traffic Control - - 基础 - - - - - - 编 排 - Orchestration - - - - - 服务编排 - Service Orch - - 成熟 - - - - 事件总线 - Event Bus - - 成长 - - - - 规则引擎 - Rule Engine - - 成长 - - - - - - 数 据 - Data Domain - - - - - 实时计算 - Real-time Comp - - 成长 - - - - 主数据管理 - Master Data - - 基础 - - - - 数据共享层 - Data API - - 成长 - - - - - - 工 具 - DevOps Tools - - - - - CI/CD 流水线 - Pipeline - - 成熟 - - - - 链路追踪 - Tracing - - 成熟 - - - - 智能巡检 - Inspection - - 基础 - - - - - - 治 理 - Governance - - - - - 资产大盘 - Dashboard - - 成长 - - - - 降级熔断 - Circuit Break - - 成熟 - - - - 容量评估 - Capacity Eval - - 基础 - - - - - - - - 平台支撑 - - - - - - 多云混合架构 - - - 容器调度底座 - - - 统一存储网络 - - - 集中可观测性 - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/50-troubleshooting-tree.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/50-troubleshooting-tree.svg deleted file mode 100644 index 40bf30364..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/50-troubleshooting-tree.svg +++ /dev/null @@ -1,287 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 大面积受影响 - - - - - 指标正常 - - - - - 指标正常 - - - - - 指标正常 - - - - - 指标正常 - - - - - 均未发现异常 - - - - - - - - 个别单点 - - - - - - 命中发现 - - - - 命中发现 - - - - 命中发现 - - - - 命中发现 - - - - 命中发现 - - - - 触发转交 - - - - - - - - - - - - - - - - - - - - - - - - - - 止损后深入探查 - - - - - - - - - - 用户现象接报 - - - - 评估初步影响范围 - - - - 1. 检查应用监控指标 - - - - 2. 检查外部依赖与存储 - - - - 3. 检查数据流与队列 - - - - 4. 检查资源容量监控 - - - - 5. 检查配置与发布记录 - - - - 排查无果，触发兜底 - - - - - - - - - 单点现象评估 - - 零星客户反馈 / 监控大盘无波动 - - 常态化流转 - - 转交一线客服走标准工单排查 - - - - - - - 异常线索 - - Error 日志飙升 / 5xx 状态码激增 - - 处置动作 - - 定位异常代码行，快速执行服务重启 - - - - - - - 异常线索 - - 下游 RPC 超时 / 数据库慢查询告警 - - 处置动作 - - 手动触发降级策略，切换备用链路 - - - - - - - 异常线索 - - 消息队列严重积压 / 数据写入受阻 - - 处置动作 - - 隔离阻断脏数据，紧急扩容消费队列 - - - - - - - 异常线索 - - CPU/内存水位飙升触顶 / 网络频繁丢包 - - 处置动作 - - 弹性扩缩容资源，限流丢弃非核心请求 - - - - - - - 异常线索 - - 排查出近期存在发布单或灰度比例调整 - - 处置动作 - - 一键回滚近期变更，并实施系统封网观察 - - - - - - - 排查阻断 - - L1排查项全部正常，未发现任何异常指标 - - 处置动作 - - 打包收集全链路日志与系统快照，准备升级 - - - - - - - - - 引导工单跟进 - 转交一线客服团队 - - - - - - - - 最高优先级 - 执行紧急止损 - - - - 通过重启/限流/降级 - 或回滚等短期手段 - 第一时间恢复核心业务 - - - - - - 定位并修复根因 - 长效彻底解决业务隐患 - - - - - - 升级 L2/L3 专家介入 - 协同深挖未知复杂故障 - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/51-c4-context.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/51-c4-context.svg deleted file mode 100644 index 5b2b83345..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/51-c4-context.svg +++ /dev/null @@ -1,81 +0,0 @@ - - - - - - - - - - 系统上下文图 (System Context) - 展现核心业务系统与各端角色、外部依赖系统的高层次边界与交互流向 - - - - - - 提交数据与请求 - - - 配置与日常维护 - - - - - - - - 身份鉴权与 SSO - - - 发起支付与退款 - - - 推送业务消息 - - - 上报关键事件 - - - - [角色] - 最终用户 - 访问前端应用系统， - 使用核心业务能力的消费者 - - - [角色] - 运营人员 - 内部管理与运营人员， - 负责业务配置与日常维护 - - - - [目标系统] - 核心业务系统 - 提供整体业务处理能力， - 编排外部服务与内部逻辑， - 响应多端用户的各项操作请求 - - - - [外部系统] - 身份认证服务 - 提供集中的身份验证与鉴权 - - - [外部系统] - 支付核心中心 - 处理全网交易、对账及退款 - - - [外部系统] - 消息触达平台 - 统一管理模板与全渠道推送 - - - [外部系统] - 实时风控引擎 - 业务风险评估与异常拦截 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/52-c4-container.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/52-c4-container.svg deleted file mode 100644 index 475107ad5..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/52-c4-container.svg +++ /dev/null @@ -1,91 +0,0 @@ - - - - - - - - - - - - 系统边界 (Internal System) - - - - - - - - - - - - - - HTTPS - - - HTTPS - - - HTTPS / RPC - - - RPC (读写) - - - TCP (缓存) - - - HTTPS API - - - Pub (发布事件) - - - Sub (订阅事件) - - - JDBC (读写) - - - JDBC (批量写) - - - 用户 - 与系统交互的最终使用者 - - - Web / 移动端 - 提供用户侧界面体验与本地交互 - - - API 服务 - 统一网关路由与安全鉴权 - - - 核心业务服务 - 处理主要业务逻辑与资源调度 - - - 分布式缓存 - 加速热点数据读取与状态维护 - - - 主数据存储 - 持久化核心业务记录与事务管理 - - - 事件总线 - 异步消息解耦分发与流量削峰 - - - 后台任务系统 - 执行耗时计算、定时任务与对账 - - - 外部依赖系统 - 第三方支付及外部消息通知服务 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/53-c4-component.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/53-c4-component.svg deleted file mode 100644 index 3edfa021b..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/53-c4-component.svg +++ /dev/null @@ -1,84 +0,0 @@ - - - - - - - - - - 发起调用 - - - 业务客户端 - [Person/System] - - - 业务服务 [Container] - - - 入口适配器 [Component] - 处理 HTTP/RPC 请求，参数校验与转换 - - - - - 应用编排 [Component] - 组合领域服务，编排业务用例与事务 - - - - - - - - 用户领域 [Component] - 封装用户核心业务 - 逻辑与状态流转 - - - 订单领域 [Component] - 订单创建、状态流转 - 与生命周期管理 - - - 支付领域 [Component] - 支付单生成、金额 - 计算与对账逻辑 - - - 营销策略 [Component] - 折扣计算、优惠券 - 等规则执行判定 - - - - - - - - - 仓储端口 [Component] - 领域模型持久化与防腐层适配 - - - 外部能力端口 [Component] - 第三方服务网关对接与防腐隔离 - - - - 读写数据 - - - - API 调用 - - - 业务数据库 [Database] - 存储系统核心领域数据 - - - 第三方服务 [System] - 外部风控、支付网关等 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/54-deployment-runtime-topology.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/54-deployment-runtime-topology.svg deleted file mode 100644 index 18b8af7ef..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/54-deployment-runtime-topology.svg +++ /dev/null @@ -1,158 +0,0 @@ - - - - - - - - - - - - 公网边缘区 (Public Edge) - - - 应用运行区 (App Runtime) - - - 数据区 (Data Layer) - - - 管理区 (Management) - - - Internet - - - - - 状态与流量上报 - 指标与日志收集 - 遥测数据上报 - - - - - - TCP 80 / 443 - - - - HTTP 流量分发 - - - - - - - - - TCP / 6379 - TCP / 3306 - TCP / AMQP - - - - - - - 持久化与归档 - HTTP / S3 API - - - - - 拉取消费 / 事件订阅 - - - - - 无状态 - 负载入口 (Load Balancer) - SSL/TLS 卸载 · 路由转发 - - - - - 扩缩容单元 (ASG) - - - - - 无状态 - 应用实例 1 - Web API · 业务逻辑 - - - - - - 无状态 - 应用实例 2 - Web API · 业务逻辑 - - - - - - 无状态 - 后台任务集群 - 异步调度 · 批处理 - - - - - - 有状态 - - - 分布式缓存 - 会话状态 · 查询加速 - - - - - - 有状态 - - - 主数据库 - 核心关系型存储 - - - - - - 有状态 - - - 消息系统 - 削峰填谷 · 异步解耦 - - - - - - 有状态 - - - 对象存储 - 附件 · 非结构化数据 - - - - - 监控与控制面 - Control Plane & Monitor - - - 日志聚合分析 (Logging) - - - 全链路追踪 (Tracing) - - - 指标监控预警 (Metrics) - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/55-quality-attribute-utility-tree.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/55-quality-attribute-utility-tree.svg deleted file mode 100644 index 4a62b2101..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/55-quality-attribute-utility-tree.svg +++ /dev/null @@ -1,98 +0,0 @@ - - - - - - - 质量属性效用树 (Utility Tree) - - 业务目标 - 质量属性 - 可验证场景 (Scenarios) - - - - - - - - - - - - - - - 业务成功 - - - 性能 - - - 可用性 - - - 安全 - - - 可演进性 - - - 成本 - - - 秒杀/大促高并发场景 - - 重要 H - - 风险 H - 刺激：瞬时并发请求量激增至平时 10 倍以上 - 环境：双十一大促或核心秒杀活动期间 - 响应：系统能够平滑处理请求，核心服务不断线 - 指标：P99 延迟 < 200ms，吞吐量 ≥ 10万 TPS - - - 核心机房/可用区故障场景 - - 重要 H - - 风险 M - 刺激：核心计算节点或单可用区网络整体瘫痪 - 环境：系统日常高负载运行期间发生的不可预知故障 - 响应：自动触发容灾切换，备用节点无缝接管核心流量 - 指标：RTO < 5 分钟，RPO = 0（数据零丢失） - - - 恶意 CC / 爬虫高频攻击防御 - - 重要 M - - 风险 L - 刺激：黑客或竞争对手发起大量高频爬虫与 CC 攻击 - 环境：开放互联网接口，未登录及登录态混合访问 - 响应：网关层自动识别异常特征并阻断恶意流量 - 指标：恶意流量拦截率 > 99%，正常请求误杀率 < 0.1% - - - 新增第三方支付渠道接入 - - 重要 M - - 风险 M - 刺激：业务侧要求一周内新增一种第三方支付方式 - 环境：主交易链路处于日常敏捷迭代与维护周期内 - 响应：开发团队仅需新增配置和少量实现类即可完成接入 - 指标：开发及测试总耗时 < 3 人天，对原有逻辑零侵入 - - - 资源闲置期弹性缩容 - - 重要 L - - 风险 L - 刺激：业务低谷期（如凌晨）请求量降至峰值的 10% - 环境：云原生微服务架构下的日常低负载运行态 - 响应：系统自动识别低负载状态并平滑回收冗余计算资源 - 指标：集群 CPU 整体利用率维持在 40%~60%，硬件成本降 30% - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/56-architecture-tradeoff.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/56-architecture-tradeoff.svg deleted file mode 100644 index 306dcffd8..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/56-architecture-tradeoff.svg +++ /dev/null @@ -1,147 +0,0 @@ - - - - 架构选型权衡与决策 (Architecture Trade-off) - 基于业务约束的横向对比评估，明确“获得什么”与“放弃什么” - - - 核心约束 - - - - 业务规模 - 日均千万级核心请求 - 峰值 QPS 10w+ 预期 - - - - 响应延迟 - 交易类核心链路 - 严格要求 P99 < 50ms - - - - 团队储备 - 以 Java/Spring 为主 - 极度缺乏云原生运维经验 - - - - 资源成本 - 单机房物理机主导 - 本财年预算严格受限 - - - - - 方案 A: 单体平滑演进 - - - - 推荐 - 方案 B: 微服务拆分 - - - 方案 C: Serverless - - - - - - - 获得收益 - • 团队研发惯性极小 - • 当前环境运维最简单 - - - - 获得收益 - • 获得极致的横向扩展性 - • 业务域故障物理隔离 - - - - 获得收益 - • 流量按需极致自动扩缩 - • 彻底免除底层节点运维 - - - - 放弃代价 - • 代码全局耦合依然存在 - • 单节点性能将触及天花板 - - - - 放弃代价 - • 前期基建与重构成本高 - • 跨链路排障复杂度陡增 - - - - 放弃代价 - • 丧失基础设施绝对控制权 - • 部署层逻辑需全部重写 - - - - 主要风险 - • 流量突增引发全局雪崩 - • 发版过慢拖延核心业务 - - - - 主要风险 - • 分布式事务致数据不一致 - • 运维不熟导致系统拥堵 - - - - 主要风险 - • 冷启动致 P99 延迟劣化 - • 被公有云厂商深度绑定 - - - - 退出成本 - • 极低，可随时终止演进 - • 无历史包袱与沉没成本 - - - - 退出成本 - • 极高，退回单体几无可能 - • 业务代码已被 RPC 污染 - - - - 退出成本 - • 较高，需剥离云服务依赖 - • 需重建本地容器调度体系 - - - - 决策结论与动作 - - - - 最终推荐方案 - 方案 B (微服务拆分) - 在满足核心 P99 延迟前提下 - “长痛不如短痛”，彻底解决 - 因规模上升带来的扩展瓶颈。 - - - - 方案成立条件 - 1. 核心链路基建必须先行到位 - 2. 团队急需引入云原生架构师 - 补充服务化治理与排障经验 - - - - 触发重新评审条件 - • 月度云资源成本超预算 30% - • 核心业务延迟超限致生产事故 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/57-adr-decision.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/57-adr-decision.svg deleted file mode 100644 index ce0316297..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/57-adr-decision.svg +++ /dev/null @@ -1,106 +0,0 @@ - - - - - - - - - - 架构决策记录 (ADR) - Architecture Decision Record Template - - - - 决策背景 (Context) - • 随着业务用户量持续激增，系统整体负载不断攀升 - • 当前的单体架构已成为业务快速迭代的阻碍与瓶颈 - - - - 架构痛点 (Problem) - • 核心数据层查询严重超时，缺乏水平扩展能力 - • 各业务模块强耦合，导致牵一发而动全身，发布风险高 - - - - 不可变约束 (Constraints) - • 必须在今年 Q3 业务旺季前完成核心链路的架构改造 - • 新架构增加的服务器和基建预算年度同比不能超过 20% - - - - - - - - - - - - - 方案 A (单体拆分) - • 仅做服务级别水平拆分 - • 实施快，但无法根治痛点 - - - - 方案 B (微服务化) - • 引入微服务及消息中间件 - • 扩展性佳，满足长期演进诉求 - - - - 方案 C (Serverless) - • 采用全托管云原生计算架构 - • 重构成本极高，超出当前预算 - - - - - - - - - 最终决策 (Decision) - • 决定采用 方案 B (微服务化架构) - • 综合评估下，该方案能够在严格的改造时间限制以及系 - 统长期扩展性之间取得最佳的技术与成本平衡。 - - - - 已接受 - - - - - - - - - 正面后果 (Positive Consequences) - • 极大提升系统水平扩展与高并发数据处理能力 - • 业务服务实现解耦，显著降低了后期的代码维护成本 - - - - 负面后果 (Negative Consequences) - • 前期基建搭建与微服务化架构重构的成本显著增加 - • 引入了分布式系统调用延迟以及相对较高的运维复杂度 - - - - - - - 已接受风险 (Accepted Risks) - • 团队对新引入的消息中间件及相关组件尚需时间熟悉 - • 架构演进期间可能出现短暂的向后兼容性问题或 Bug - - - - 复审触发条件 (Review Triggers) - • 核心链路响应耗时连续一周超过定义的 SLA 预警标准 - • 业务用户量和系统并发量提前达到三年后的规划上限 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/58-capacity-bottleneck.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/58-capacity-bottleneck.svg deleted file mode 100644 index a0af08760..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/58-capacity-bottleneck.svg +++ /dev/null @@ -1,188 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - HTTP / HTTPS - - - 异步解耦 - - - 同步读写 - - - 批量写入 - - - - - 入口峰值流量 (QPS: [10,000]) - - - - - - - - - - 接入层 (API Gateway) - - 需求: - [10,000] QPS - - 能力: - [15,000] QPS - - 利用率: - [66]% - - - - - - - - - - 业务服务 A (查询) - - 需求: - [3,000] QPS - - 能力: - [5,000] QPS - - 利用率: - [60]% - - - - - - - - - 核心服务 B (交易) - - - 首个瓶颈 - - 需求: - [5,000] QPS - - 能力: - [4,500] QPS - - 利用率: - [111]% - - - - - - - - - 聚合服务 C (报表) - - 需求: - [2,000] QPS - - 能力: - [4,000] QPS - - 利用率: - [50]% - - - - - - - - - - 消息队列 (Kafka) - - - 降载排队 - - 需求: - [3,000] TPS - - 能力: - [2,000] TPS - - 利用率: - [100]% - - - - - - - - - 核心数据库 (MySQL) - - 需求: - [4,500] TPS - - 能力: - [8,000] TPS - - 利用率: - [56]% - - - - - - - - - 对象存储 (S3) - - 需求: - [500] TPS - - 能力: - [2,000] TPS - - 利用率: - [25]% - - - - - - 日增: [50] GB - 保留: [30] 天 - - - - - 日增: [1.2] TB - 保留: [365] 天 - - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/59-fault-propagation.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/59-fault-propagation.svg deleted file mode 100644 index 2a09e1518..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/59-fault-propagation.svg +++ /dev/null @@ -1,138 +0,0 @@ - - - - - - - - - - - - - 外部边界域 - - - - 中间路由域 - - - - 核心业务域 - - - - 爆炸半径 - - - - - - - - - - - - - - - - - 超时 - - - - - - 熔断 - - - - - - 舱壁 - - - - - - 限流 - - - - - - 降级 - - - - - - - 外部依赖延迟 - 响应骤增 / 超时 - - - - - - - 重试放大 - 并发请求激增 - - - - - - - 连接池耗尽 - 线程阻塞 / 挂起 - - - - - - - 请求堆积 - 队列满载溢出 - - - - - - - 核心服务受损 - 响应变慢 / 拒绝 - - - - - - - 用户失败 - 大面积报错 - - - - - - - - 局部影响 - 单一接口可用性下降 - - - - - 故障升级 - - - - - 全局影响 - 服务雪崩 / 全站宕机 - - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/60-slo-error-budget.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/60-slo-error-budget.svg deleted file mode 100644 index 2ee70e14e..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/60-slo-error-budget.svg +++ /dev/null @@ -1,78 +0,0 @@ - - - - - - - - - - - - - - - - - 监控与目标输入链路 - - - 用户关键旅程 - 核心业务场景 - - - 可用性与延迟 - SLI 关键指标采集 - - - SLO 目标判定 - 30 天滚动窗口 - - - - 当前预算状态 - - 计算剩余错误预算 - 计算 30 天燃烧率 - - - - 低消耗 (健康) - 允许进行变更发布 - - - - 高消耗 (超标) - 燃烧率触达限制阈值 - 触发冻结变更拦截 - - - - 可靠性改进 - 停止业务功能迭代 - 投入资源修复稳定性 - - - - 故障诊断与复盘 - 深度分析超标根因 - 生成对应 Action Item - - - - - - - - 预算健康 - - - 预算耗尽 - - - - - - 完成可靠性闭环修复，更新下一个 30 天滚动窗口 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/61-data-consistency-strategy.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/61-data-consistency-strategy.svg deleted file mode 100644 index 33be7f838..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/61-data-consistency-strategy.svg +++ /dev/null @@ -1,84 +0,0 @@ - - - - - - - - - - - - 订单服务 (Upstream) - - - 本地事务边界 - - - 写业务表 - - - 事实源 - - - 写 Outbox 表 - - - 提交点 - - Saga 补偿动作 - - 执行 Saga 回滚 / 冲正 - - - 消息系统 (Event Bus) - 异步发布 / 订阅分发 - - - 定时对账修复 (全局兜底) - - - 下游服务 (Downstream) - - - 最终一致 - - - 幂等键校验 (Idempotent) - - - 更新业务本地状态 - - - Saga 补偿 - - - 重试策略 - - - - - - 至少一次投递 - - - 发布事件 - - - 校验通过 - - - 业务拒绝 - - - 并发/网络异常 - - - - - 触发补偿回调 - - - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/62-trust-boundary-threat-model.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/62-trust-boundary-threat-model.svg deleted file mode 100644 index 315e4d7b2..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/62-trust-boundary-threat-model.svg +++ /dev/null @@ -1,176 +0,0 @@ - - - - - - - - - - - - - 信任边界与威胁模型架构图 - 全局跨域数据流转、安全隔离控制及 STRIDE 威胁消减模型 - - - - 安全威胁 (Threat) - - - 控制措施 (Control) - - - 信任边界定义 - - - - - 不可信域 (Untrusted) - - - - 公网入口 (DMZ) - - - - 应用信任域 (Trusted) - - - - 数据核心域 (Secured) - - - - - 互联网边界 - - - - 内网隔离界 - - - - 数据核心界 - - - - - - - - - - - - - - - - - - - 身份冒用 - - DDoS攻击 - - WAF 过滤 - - TLS 加密 - - - 重放攻击 - - 数据泄露 - - IP 白名单 - - 频率限制 - - - 越权访问 - - 会话劫持 - - Token校验 - - 动态加盐 - - - 接口篡改 - - 异常报文 - - 数字签名 - - 报文校验 - - - 内部窃听 - - 凭证拖库 - - VPC 隔离 - - 强散列存 - - - 事件丢弃 - - 审计篡改 - - 确认机制 - - 签名防伪 - - - SQL 注入 - - 核心泄露 - - 参数绑定 - - 存储加密 - - - - - 外部终端应用 - - - - 第三方接入方 - - - - 前端接入网关 - - - - 开放 API 网关 - - - - 认证与会话服务 - - - - 审计与风控引擎 - - - - 业务应用微服务 - - - - 核心缓存与配置 - - - - 日志与 MQ 总线 - - - - 核心业务数据库 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/63-multi-tenant-isolation.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/63-multi-tenant-isolation.svg deleted file mode 100644 index 574503396..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/63-multi-tenant-isolation.svg +++ /dev/null @@ -1,145 +0,0 @@ - - - - - - - - - - - - 计算资源隔离层 - 隔离度与成本递增 → - - - 数据存储隔离层 - 隔离度与成本递增 → - - - 全局安全与治理 - - - - - - - - 操作审计 - - - 全链路租户行为追踪 - - 防篡改日志独立存储 - - - 配额限流 - - - 租户级水位监控防雪崩 - - API调用与资源硬限流 - - - 租户密钥 (KMS) - - - BYOK 独立加密机制 - - 凭据单独轮转与吊销 - - - - - - - - - - - - 租 - 户 - 上 - 下 - 文 - - - 租 - 户 - 上 - 下 - 文 - - - - - - - - 租户入口与身份策略 - 网关鉴权 / Token 解析 / 租户路由 - - - - 共享计算池 - - - 多租户混部极高密度 - - 资源完全池化与调度 - - 适合长尾客户成本优 - - - 独立工作空间 - - - 基于命名空间软隔离 - - 计算实例与配额独立 - - 适合中大型标准客户 - - - 专属计算 - - - 节点或集群完全独占 - - 物理级别无网络互通 - - 适合高安全需求客户 - - - - 共享表逻辑隔离 - - - 按租户 ID 路由拦截 - - 同表共享极高存储密度 - - 易于聚合且成本最优化 - - - 独立 Schema - - - 一租户对应一命名空间 - - 表级安全隔离单独备份 - - 隔离度与成本动态平衡 - - - 独立数据库 - - - 一租户一物理 DB 实例 - - 数据物理阻断杜绝渗透 - - 满足金融政企安全合规 - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/64-team-topology-ownership.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/64-team-topology-ownership.svg deleted file mode 100644 index a8949f6c8..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/64-team-topology-ownership.svg +++ /dev/null @@ -1,135 +0,0 @@ - - - - - - - - - 业务流交付层 - Stream-aligned Domain - - - 辅导与专长层 - Enabling & Subsystem Domain - - - 平台基础底座 - Platform Domain - - - 故障升级路径 - Escalation Path - - - - - - - - - - - - - - - 促进 - - - - 协作 - - - - - X-as-a-Service - - - - - 业务流团队 A - 端到端交付交易闭环能力 - - - - 服务 A1 - 核心交易链路 - - - - 服务 A2 - 订单状态引擎 - - - - - 业务流团队 B - 端到端交付履约售后闭环 - - - - 服务 B1 - 物流追踪服务 - - - - 服务 B2 - 售后工单中心 - - - - - 赋能辅导团队 - 辅导测试自动化最佳实践 - - - - 复杂子系统团队 - 研发维护运筹与排班算法 - - - - - 基础架构与平台团队 - 提供标准化支撑底座，降低业务认知负担 - - - - CI/CD 流水线 - 自动化构建部署环境 - - - - 多云资源编排 - 全生命周期架构即代码 - - - - - 升级支持 - - - - 重度攻关 - - - - Level 1 - 一线业务流响应 - 接收报警、优先排查减损 - - - - Level 2 - 专长与底层基础设施 - 深挖组件异常与平台故障 - - - - Level 3 - 全域架构专家组 - 协同修复重特大系统缺陷 - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/65-shared-context-architecture.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/65-shared-context-architecture.svg deleted file mode 100644 index 5834f8f49..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/65-shared-context-architecture.svg +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - - - - - - - - - - - - - 版本化事实源 - - - Owner - - - 时效 - - - - PRD (产品需求) - - - - ADR (架构决策) - - - - 代码仓库 (Code) - - - - 观测数据 (Trace) - - - - 任务 (Ticket) - - - - 评测集 (Eval Sets) - - - - 复盘记录 - - - - 上下文装配流 (Context Assembly Pipeline) - - - 采集索引 - Indexing - - - 权限隔离 - - - 权限过滤 - Auth Filter - - - 检索排序 - Retrieval & Rank - - - 引用溯源 - - - 预算装配 - Budget Assembly - - - - - - - - 上下文应用端 - - - 工程师 (Engineer) - - - 多个 Agent 阵列 - - - - 执行结果 / 失败样本 - Results & Fallbacks - - - - 汇聚拉取 - - - 注入分发 - - - - - 闭环修正与样本回写数据总线 (Feedback Bus) - - - - - - - - - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/66-ai-workflow-governance.svg b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/66-ai-workflow-governance.svg deleted file mode 100644 index a40cf059a..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/assets/samples/66-ai-workflow-governance.svg +++ /dev/null @@ -1,111 +0,0 @@ - - - - - - - - - - - - - - - - 治理控制面 (Governance & Control) - - AI 核心工作流 (Core Workflow) - - - 观测与反馈闭环 (Observability & Feedback) - - - - - - - - - - - - - - - 高风险进入审批 - - - - - - - - - - - - - - - - - - - Owner - 责任归属 - - - 权限策略 - 细粒度控制 - - - 风险分级 - 敏感度评估 - - - 审计 - 行为追溯 - - - - - 场景定义 - - - 模板 / Skill - - - Flow 编排 - - - 模型与工具执行 - - - 离线评测 - - - 审批发布 - - - 在线运行 - - - - - 模板改进 - - - 失败样本 - - - 回滚 - - - 线上指标 - - - Trace - - - diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/metadata.json b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/metadata.json deleted file mode 100644 index 5353d92e6..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/metadata.json +++ /dev/null @@ -1,10 +0,0 @@ -{ - "tags": [ - "diagram", - "architecture", - "feishu", - "whiteboard" - ], - "sourceLabel": "AgentRecall bundled original skill", - "categoryId": "writing" -} diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/diagram-prompts.json b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/diagram-prompts.json deleted file mode 100644 index 07533fe97..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/diagram-prompts.json +++ /dev/null @@ -1,530 +0,0 @@ -[ - { - "id": "01", - "slug": "react-loop", - "category": "Agent 核心机制", - "title": "ReAct 思考—行动—观察循环", - "style": "流程图配色", - "prompt": "生成一张 ReAct Agent 循环流程图模板。节点为用户目标、思考、选择工具、执行工具、观察结果、判断是否完成、最终输出；未完成则从判断回到思考。横向主链结合下方回环，结束分支清晰。中文短标签，6-8 个主节点，不使用具体产品名。" - }, - { - "id": "02", - "slug": "plan-and-execute", - "category": "Agent 核心机制", - "title": "Plan-and-Execute 规划执行", - "style": "飞书经典", - "prompt": "生成一张 Plan-and-Execute Agent 流程图。用户目标进入规划器形成任务列表，执行器逐项执行并更新状态；遇到新信息时回到规划器重规划，全部完成后汇总输出。左到右布局，计划与执行分组，最多 10 个节点，中文通用标签。" - }, - { - "id": "03", - "slug": "context-assembly", - "category": "Agent 核心机制", - "title": "Agent 上下文组装与裁剪", - "style": "低饱和", - "prompt": "生成一张 Agent 上下文组装架构图。系统指令、用户输入、对话历史、长期记忆、知识检索、工具结果六类来源汇入过滤、排序、去重和 Token 预算控制，最终组装为模型输入。多源汇聚布局，标注优先级和裁剪，中文短标签。" - }, - { - "id": "04", - "slug": "memory-architecture", - "category": "Agent 核心机制", - "title": "Agent 多层记忆架构", - "style": "飞书经典", - "prompt": "生成一张 Agent 记忆架构图。展示工作记忆、会话记忆、长期记忆三层，以及记忆抽取、价值评分、去重写入、按需检索和遗忘清理。三层纵向布局，读写箭头语义清楚，节点不超过 11 个。" - }, - { - "id": "05", - "slug": "rag-agent", - "category": "Agent 核心机制", - "title": "RAG Agent 检索生成", - "style": "飞书经典", - "prompt": "生成一张 RAG Agent 数据流程图。问题依次经过查询改写、多路检索、召回合并、重排、上下文构造、模型生成和引用校验，知识库与向量索引作为数据源。横向数据流，边标注查询、文档、引用，低信息噪声。" - }, - { - "id": "06", - "slug": "supervisor-worker", - "category": "多 Agent 协作", - "title": "Supervisor–Worker 多 Agent", - "style": "飞书经典", - "prompt": "生成一张 Supervisor–Worker 多 Agent 架构图。主管 Agent 接收目标、拆分任务并派发给研究、执行、验证三个 Worker；Worker 回传结果，主管汇总验收，不通过则返工。主管居中，扇出扇入布局，职责边界清晰。" - }, - { - "id": "07", - "slug": "router-specialist", - "category": "多 Agent 协作", - "title": "Router–Specialist 智能路由", - "style": "流程图配色", - "prompt": "生成一张 Router–Specialist 多 Agent 路由图。请求经过意图识别与路由判断，分别进入代码、数据、文档三个专家 Agent，无法识别时进入通用 Agent；结果经统一适配输出。判断边写真实类别，横向分支布局。" - }, - { - "id": "08", - "slug": "parallel-fan-in", - "category": "多 Agent 协作", - "title": "多 Agent 并行汇总", - "style": "低饱和", - "prompt": "生成一张多 Agent Fan-out/Fan-in 工作流图。任务被拆成三个独立子任务并行执行，每路带超时与结果校验，随后聚合器去重、排序、合并并输出。并行泳道或扇出扇入布局，突出并发与汇合。" - }, - { - "id": "09", - "slug": "generator-reviewer", - "category": "多 Agent 协作", - "title": "Generator–Reviewer 评审闭环", - "style": "流程图配色", - "prompt": "生成一张 Generator–Reviewer Agent 闭环图。需求进入生成 Agent 产生草稿，审核 Agent 按正确性、完整性、格式评分；通过则输出，不通过则给出反馈并回到生成 Agent，最多三轮。环形评审流程，条件和终止规则明确。" - }, - { - "id": "10", - "slug": "handoff-human", - "category": "多 Agent 协作", - "title": "Agent Handoff 与人工接管", - "style": "飞书经典", - "prompt": "生成一张 Agent Handoff 泳道图。泳道为 Agent A、编排平台、Agent B、人工专家；展示触发交接、封装上下文和未决事项、接收确认、继续处理，以及高风险场景转人工。时间从左到右，交接包字段简洁。" - }, - { - "id": "11", - "slug": "agent-development-lifecycle", - "category": "Agent 开发与调试", - "title": "Agent 从需求到上线", - "style": "流程图配色", - "prompt": "生成一张 Agent 开发全流程图。阶段为场景定义、成功指标、方案设计、Prompt 与 Tool 实现、离线评测、真实流量灰度、线上监控、失败样本回流。横向阶段布局，评测不通过回到实现，节点 8-10 个。" - }, - { - "id": "12", - "slug": "prompt-development", - "category": "Agent 开发与调试", - "title": "Prompt 开发与版本管理", - "style": "流程图配色", - "prompt": "生成一张 Prompt 开发流程图。编写模板后进行样例测试、固定评测集批量运行、与基线对比、人工 Review、版本发布；指标下降则修改 Prompt 并重新评测。标出 Prompt 版本与评测集版本，横向闭环。" - }, - { - "id": "13", - "slug": "tool-mcp-integration", - "category": "Agent 开发与调试", - "title": "Tool/MCP 接入与联调", - "style": "飞书经典", - "prompt": "生成一张 Agent Tool/MCP 接入泳道图。泳道为 Agent、MCP Client、Tool Server；流程包含需求、Schema 定义、服务实现、权限配置、工具注册、联调、超时错误处理和降级。协议边界与请求响应清晰，中文短标签。" - }, - { - "id": "14", - "slug": "agent-evaluation-loop", - "category": "Agent 开发与调试", - "title": "Agent 评测集与效果迭代", - "style": "流程图配色", - "prompt": "生成一张 Agent 评测闭环图。真实样本采集后经过清洗、脱敏、标注、数据集版本化，再运行 Agent、规则与模型评分、失败聚类、根因分析，优化结果回流为新样本。环形流程，突出数据集版本。" - }, - { - "id": "15", - "slug": "agent-trace-debugging", - "category": "Agent 开发与调试", - "title": "Agent Trace 调试与归因", - "style": "流程图配色", - "prompt": "生成一张 Agent Trace 排障诊断图。从失败请求进入 Trace 总览，依次检查慢节点、错误节点、Prompt 输入输出、Tool 参数结果、模型响应，最终归因到上下文、模型、工具或编排并回归验证。决策树布局，检查项简短。" - }, - { - "id": "16", - "slug": "software-development-lifecycle", - "category": "软件研发流程", - "title": "软件开发全流程", - "style": "飞书经典", - "prompt": "生成一张软件研发全流程图。需求提出、需求评审、技术设计、开发、代码评审、测试、灰度发布、全量上线、监控复盘依次推进；每阶段标一个关键产物或门禁。横向阶段布局，避免具体组织名称。" - }, - { - "id": "17", - "slug": "requirement-to-design", - "category": "软件研发流程", - "title": "需求评审到技术方案", - "style": "飞书经典", - "prompt": "生成一张需求到技术方案泳道图。泳道为产品、研发、测试；展示需求澄清、范围确认、风险识别、需求评审、技术调研、方案编写、方案评审和修改确认。责任交接清楚，时间从左到右。" - }, - { - "id": "18", - "slug": "tdd-cycle", - "category": "软件研发流程", - "title": "TDD Red–Green–Refactor", - "style": "流程图配色", - "prompt": "生成一张 TDD 循环学习图。写一个失败测试进入 Red，编写最小实现进入 Green，保持测试通过进行 Refactor，随后添加下一个测试；任何测试失败返回最小实现。使用环形结构和红、绿、蓝三种克制语义色。" - }, - { - "id": "19", - "slug": "git-pr-review", - "category": "软件研发流程", - "title": "Git、PR 与 Code Review", - "style": "飞书经典", - "prompt": "生成一张 Git Feature Branch 与 PR Review 泳道图。泳道为开发者、CI、Reviewer；流程包括创建分支、提交、推送、创建 PR、自动检查、人工 Review、修改、批准、合并和删除分支。失败与修改回路明确。" - }, - { - "id": "20", - "slug": "cicd-release", - "category": "软件研发流程", - "title": "CI/CD 灰度与回滚", - "style": "流程图配色", - "prompt": "生成一张 CI/CD 发布流程图。Commit 经构建、单测、安全扫描生成唯一制品，依次部署测试环境、验收、生产小流量灰度、指标观察、扩量或回滚。用判断节点表示门禁，强调制品不重复构建。" - }, - { - "id": "21", - "slug": "layered-architecture", - "category": "系统架构", - "title": "经典分层架构", - "style": "飞书经典", - "prompt": "生成一张经典分层系统架构图。自上而下为客户端、接入层、应用层、领域层、基础设施层、数据存储层；每层 2-3 个通用组件，只画允许的向下依赖和一个关键跨层接口。16:9 纵向分层，低信息噪声。" - }, - { - "id": "22", - "slug": "monolith-to-microservices", - "category": "系统架构", - "title": "单体到微服务演进", - "style": "低饱和", - "prompt": "生成一张单体到微服务的架构演进图。阶段为单体应用、模块化单体、抽离共享能力、按领域拆服务、独立数据与平台治理；每阶段展示核心结构变化和迁移箭头。横向时间轴，不使用具体业务名。" - }, - { - "id": "23", - "slug": "microservice-gateway", - "category": "系统架构", - "title": "微服务与 API Gateway", - "style": "飞书经典", - "prompt": "生成一张微服务架构图。客户端经 API Gateway 进入三个领域服务，服务通过同步 API 与异步事件协作，并连接消息总线、缓存、独立数据库和可观测平台。按领域分组，只保留关键依赖，避免蜘蛛网连线。" - }, - { - "id": "24", - "slug": "plugin-architecture", - "category": "系统架构", - "title": "插件化与扩展点架构", - "style": "低饱和", - "prompt": "生成一张插件化架构图。核心 Host 依赖 Extension API 和 Plugin Registry，三个插件通过统一契约注册、加载、执行与卸载；展示权限隔离和生命周期管理。核心居中、插件环绕，依赖方向清楚。" - }, - { - "id": "25", - "slug": "agent-platform", - "category": "系统架构", - "title": "Agent 平台整体架构", - "style": "飞书经典", - "prompt": "生成一张 Agent 平台整体架构图。分为应用入口、Agent 编排、模型服务、知识检索、工具平台、记忆服务、运行与评测、数据存储八个区域；展示核心调用关系和治理边界。16:9 分层架构，节点 10-12 个。" - }, - { - "id": "26", - "slug": "synchronous-sequence", - "category": "交互与状态", - "title": "同步服务调用时序", - "style": "简约黑白", - "prompt": "生成一张同步调用时序图。参与方为调用方、API 网关、业务服务、数据库、外部服务；展示鉴权、读取数据、调用外部服务、写入结果和同步响应，包含一个超时返回。请求实线、响应虚线，步骤不超过 10 个。" - }, - { - "id": "27", - "slug": "asynchronous-sequence", - "category": "交互与状态", - "title": "异步事件消费时序", - "style": "简约黑白", - "prompt": "生成一张异步事件时序图。生产者发布消息到 Broker，Broker 确认后消费者拉取或接收、做幂等检查、写入数据库并 ACK；失败时重试，超过上限进入死信队列。参与方按顺序排列，异步语义明确。" - }, - { - "id": "28", - "slug": "human-agent-swimlane", - "category": "交互与状态", - "title": "用户、Agent 与人工审核泳道", - "style": "飞书经典", - "prompt": "生成一张人机协作泳道图。泳道为用户、业务系统、Agent、人工审核；用户提交后系统受理，Agent 分析并按风险判断，低风险自动处理，高风险转人工审批，最后通知用户。时间从左到右，交接点清楚。" - }, - { - "id": "29", - "slug": "task-state-machine", - "category": "交互与状态", - "title": "任务生命周期状态机", - "style": "低饱和", - "prompt": "生成一张任务生命周期状态机。状态包括 Created、Running、Waiting、Succeeded、Failed、Cancelled；边标注开始、等待外部结果、收到结果、超时、重试、取消，成功失败取消为终态。结构均衡，突出允许重试的回边。" - }, - { - "id": "30", - "slug": "retry-compensation", - "category": "交互与状态", - "title": "失败重试、降级与补偿", - "style": "流程图配色", - "prompt": "生成一张异常处理流程图。执行失败后分类为瞬时错误、依赖不可用、业务失败；分别进入退避重试、降级或补偿，补偿失败触发告警与人工介入，所有路径落到明确终态。正常路径居中，异常路径下沉。" - }, - { - "id": "31", - "slug": "data-pipeline", - "category": "数据与领域建模", - "title": "数据处理管道", - "style": "飞书经典", - "prompt": "生成一张数据处理管道图。数据源经采集、清洗、标准化后分为实时流处理和离线批处理，两路汇聚到数据湖或数仓，再供在线服务和分析报表使用。横向数据流，边标注原始、标准、聚合数据。" - }, - { - "id": "32", - "slug": "data-lineage", - "category": "数据与领域建模", - "title": "数据血缘与影响关系", - "style": "低饱和", - "prompt": "生成一张数据血缘 DAG。两个源表经过三个转换任务形成中间表和指标层，最终被报表和 API 消费；展示一个字段变更向下游传播的影响路径。按源、处理、模型、消费四层布局，箭头表示数据来源。" - }, - { - "id": "33", - "slug": "er-model", - "category": "数据与领域建模", - "title": "ER 数据实体关系", - "style": "简约黑白", - "prompt": "生成一张通用 ER 图。实体为用户、项目、任务、执行记录、结果；每个实体只保留主键、外键和 2-3 个关键字段，展示一对多与一对一关系。自动布局，关系基数清楚，不堆完整表字段。" - }, - { - "id": "34", - "slug": "domain-model", - "category": "数据与领域建模", - "title": "领域模型与类关系", - "style": "简约黑白", - "prompt": "生成一张领域模型图。包含聚合根 Task、子实体 Step、值对象 Status、领域事件 TaskCompleted、仓储接口 TaskRepository 和服务 TaskService；展示组合、依赖和事件发布关系。类中只写关键属性或方法。" - }, - { - "id": "35", - "slug": "cache-consistency", - "category": "数据与领域建模", - "title": "缓存与数据库一致性", - "style": "流程图配色", - "prompt": "生成一张缓存一致性双流程图。读流程为请求、查缓存、命中返回、未命中查数据库并回填；写流程为更新数据库、删除或更新缓存、发送补偿消息，包含并发与失败补偿。上下两条主链并列。" - }, - { - "id": "36", - "slug": "observability-loop", - "category": "稳定性与安全", - "title": "指标、日志、Trace 与告警闭环", - "style": "低饱和", - "prompt": "生成一张可观测性闭环架构图。服务产生指标、日志、Trace，经采集和存储分析形成看板与告警，值班响应后定位、修复并验证，结果反馈到规则和服务。三类信号并行汇聚，形成行动闭环。" - }, - { - "id": "37", - "slug": "incident-response", - "category": "稳定性与安全", - "title": "线上故障响应", - "style": "流程图配色", - "prompt": "生成一张线上故障响应泳道图。泳道为监控平台、值班工程师、故障指挥、业务团队；流程从发现、分级、拉群、止损、定位、修复、验证到复盘，展示升级条件和并行沟通。止损优先，责任边界清楚。" - }, - { - "id": "38", - "slug": "resilience-control", - "category": "稳定性与安全", - "title": "熔断、限流与降级", - "style": "流程图配色", - "prompt": "生成一张服务韧性控制流程图。请求依次检查容量和依赖健康，根据结果选择放行、限流、熔断或降级；熔断后经过半开探测，成功则恢复，失败则继续熔断。决策节点写明条件，状态变化清楚。" - }, - { - "id": "39", - "slug": "authentication-authorization", - "category": "稳定性与安全", - "title": "认证、令牌与授权", - "style": "飞书经典", - "prompt": "生成一张认证授权时序与边界图。用户、客户端、身份提供方、API 网关、策略引擎、资源服务参与；展示登录跳转、回调、Token 签发、Token 校验、权限决策和资源响应。用分组区分信任边界。" - }, - { - "id": "40", - "slug": "sensitive-operation-approval", - "category": "稳定性与安全", - "title": "敏感操作审批", - "style": "流程图配色", - "prompt": "生成一张敏感操作审批泳道图。泳道为申请人、系统、风险引擎、审批人、审计平台；操作请求经过身份校验、权限校验和风险评估，低风险自动允许，高风险人工审批，无权限拒绝，最终记录审计。" - }, - { - "id": "41", - "slug": "learning-roadmap", - "category": "学习与知识表达", - "title": "技术学习路线图", - "style": "浅色糖果", - "prompt": "生成一张通用技术学习路线图。阶段为前置知识、基础概念、核心机制、项目实战、性能调优、深入专题；每阶段列 2-3 个短标签，并用依赖箭头表示先后。横向路线图，不使用具体日期。" - }, - { - "id": "42", - "slug": "knowledge-mindmap", - "category": "学习与知识表达", - "title": "技术知识脑图", - "style": "浅色糖果", - "prompt": "生成一张技术知识脑图模板。中心为某技术，一级分支为核心概念、工作原理、关键组件、实践方法、常见问题、生态工具；每个分支 2-3 个短词。结构均衡、中文、避免长句。" - }, - { - "id": "43", - "slug": "concept-dependency", - "category": "学习与知识表达", - "title": "概念关系与知识依赖", - "style": "低饱和", - "prompt": "生成一张概念依赖 DAG 模板。基础概念 A/B 支撑中间概念 C/D，再汇聚到高阶概念 E；另用虚线表示相关或对比关系。由左到右，区分前置依赖、组成和对比三种关系。" - }, - { - "id": "44", - "slug": "mechanism-breakdown", - "category": "学习与知识表达", - "title": "技术原理内部机制拆解", - "style": "飞书经典", - "prompt": "生成一张技术原理拆解图模板。输入先经过预处理，再进入三个核心内部模块，模块共享一份状态并产生中间结果，最终经后处理输出；旁边标注关键不变量。分层机制图，适合教学解释。" - }, - { - "id": "45", - "slug": "one-picture-overview", - "category": "学习与知识表达", - "title": "一图看懂某技术", - "style": "浅色糖果", - "prompt": "生成一张一图看懂某技术的综合学习图模板。分区展示一句话定义、核心组件、工作流程、典型场景、主要优点、限制与注意事项。使用卡片加小流程的版式，16:9，信息丰富但每块文字不超过两行。" - }, - { - "id": "46", - "slug": "architecture-evolution", - "category": "规划、演进与决策", - "title": "系统架构阶段演进", - "style": "低饱和", - "prompt": "生成一张系统架构阶段演进图。阶段依次为快速起步、模块化、服务化、平台化、智能化；每阶段展示核心结构、主要驱动力和新引入能力，并用箭头表示演进。横向时间轴，不给具体年份。" - }, - { - "id": "47", - "slug": "project-milestones", - "category": "规划、演进与决策", - "title": "项目里程碑与依赖", - "style": "浅色糖果", - "prompt": "生成一张项目里程碑路线图。主阶段为调研、设计、开发、联调、灰度、发布，同时展示基础建设与业务接入两个并行工作包及其依赖。使用阶段而非具体日期，突出关键里程碑和汇合点。" - }, - { - "id": "48", - "slug": "technology-selection", - "category": "规划、演进与决策", - "title": "技术选型与选择条件", - "style": "流程图配色", - "prompt": "生成一张技术选型决策树。先判断规模与复杂度，再判断一致性要求、实时性、团队经验和运维成本，最终选择方案 A、B 或 C，并在叶子节点标出适用条件和主要风险。条件写在边上，避免主观排名。" - }, - { - "id": "49", - "slug": "capability-map", - "category": "规划、演进与决策", - "title": "能力地图与成熟度", - "style": "低饱和", - "prompt": "生成一张技术能力地图。顶部为业务目标，中间分为接入、编排、数据、工具、治理五个能力域，每域 2-3 个二级能力，底部为平台支撑；用基础、成长、成熟三档标记成熟度。分层卡片，不画调用箭头。" - }, - { - "id": "50", - "slug": "troubleshooting-tree", - "category": "规划、演进与决策", - "title": "问题排查与诊断决策树", - "style": "流程图配色", - "prompt": "生成一张通用问题排查决策树。从用户现象开始，先判断影响范围，再依次检查应用错误、外部依赖、数据异常、资源瓶颈和配置变更；每个分支包含证据检查与下一步动作，最终落到根因、临时止损或升级。" - }, - { - "id": "51", - "slug": "c4-context", - "category": "架构视图", - "title": "C4 Context 系统上下文", - "style": "飞书经典", - "prompt": "生成一张 C4 Context 系统上下文图模板。中心只有一个“目标系统”边界，左侧放最终用户、运营人员等用户角色，右侧放身份服务、支付能力、通知渠道等外部系统；每条箭头标注真实业务交互含义和方向。不要展开目标系统内部组件。中文短标签，7–9 个节点，面向非技术和技术干系人，不使用产品名、来源标识或水印。" - }, - { - "id": "52", - "slug": "c4-container", - "category": "架构视图", - "title": "C4 Container 容器视图", - "style": "飞书经典", - "prompt": "生成一张 C4 Container 容器视图模板。画出用户、Web/移动端、API 服务、核心服务、后台任务、主数据存储、缓存、事件总线和一个外部系统；所有内部容器位于清晰的系统边界内，每个容器写“名称 + 一行职责”，边标注 HTTPS、RPC、事件或读写数据。中文短标签，单一 Container 抽象层级，不使用产品名、来源标识或水印。" - }, - { - "id": "53", - "slug": "c4-component", - "category": "架构视图", - "title": "C4 Component 组件视图", - "style": "飞书经典", - "prompt": "生成一张 C4 Component 组件视图模板，只展开一个“业务服务”容器。内部包含入口适配器、应用编排、三个领域组件、策略组件、仓储端口和外部能力端口；箭头表示允许依赖方向，边界外只保留调用方与数据库/外部能力。组件写名称和职责，单一 Component 层级，中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "54", - "slug": "deployment-runtime-topology", - "category": "架构视图", - "title": "部署与运行拓扑", - "style": "低饱和", - "prompt": "生成一张通用部署与运行拓扑图。按公网边缘区、应用运行区、数据区和管理区划分边界；展示负载入口、两个应用实例、后台任务集群、消息系统、主数据库、缓存、对象存储以及监控控制面。标注主要网络方向、端口类别、无状态/有状态和扩缩容单元。中文短标签，不画多地域，不使用产品名、来源标识或水印。" - }, - { - "id": "55", - "slug": "quality-attribute-utility-tree", - "category": "架构决策", - "title": "质量属性效用树", - "style": "浅色糖果", - "prompt": "生成一张质量属性效用树模板。从“业务成功”根节点展开为性能、可用性、安全、可演进性和成本五个质量属性；每个属性再展开一个可验证场景，叶子写刺激、环境、响应和量化指标，并用 H/M/L 标重要性与技术风险。树状布局，中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "56", - "slug": "architecture-tradeoff", - "category": "架构决策", - "title": "架构权衡图", - "style": "飞书经典", - "prompt": "生成一张架构权衡图模板。左侧列规模、延迟、团队、成本四个约束；中部并列方案 A、B、C，每个方案用相同四行展示收益、代价、主要风险和退出成本；右侧给出推荐方案、成立条件以及何时重新评审。强调“获得什么、放弃什么”，中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "57", - "slug": "adr-decision", - "category": "架构决策", - "title": "ADR 架构决策记录", - "style": "低饱和", - "prompt": "生成一张 ADR 架构决策记录图模板。主链为决策背景、问题、不可变约束、候选方案 A/B/C、最终决策；决策下方分成正面后果、负面后果、已接受风险和复审触发条件四个区域，并标记状态“已接受”。中文短标签，突出可追溯性，不使用产品名、来源标识或水印。" - }, - { - "id": "58", - "slug": "capacity-bottleneck", - "category": "架构决策", - "title": "容量与瓶颈图", - "style": "流程图配色", - "prompt": "生成一张容量与瓶颈分析图模板。入口标峰值 QPS，经接入层扇出到三个服务，再进入队列、数据库和对象存储；每个关键节点同时标“需求、能力、利用率”，用红色突出首个瓶颈，用黄色标排队与降载点，旁边展示日数据增长和保留期。所有数字使用示例占位值并明确可替换，中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "59", - "slug": "fault-propagation", - "category": "可靠性与安全架构", - "title": "故障传播与爆炸半径", - "style": "流程图配色", - "prompt": "生成一张故障传播与爆炸半径图。左侧外部依赖延迟上升，经重试放大、连接池耗尽、请求堆积传播到核心服务和用户失败；用虚线框标三个隔离域，在传播边上放超时、熔断、舱壁、限流和降级五个控制点，右侧标局部影响与全局影响。中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "60", - "slug": "slo-error-budget", - "category": "可靠性与安全架构", - "title": "SLO 与错误预算闭环", - "style": "飞书经典", - "prompt": "生成一张 SLO 与错误预算闭环图。用户关键旅程产生可用性与延迟 SLI，进入 SLO 目标和 30 天窗口，计算剩余错误预算与燃烧率；低消耗允许发布，高消耗触发冻结变更、可靠性改进和复盘，再回到下一周期。中心显示预算状态，中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "61", - "slug": "data-consistency-strategy", - "category": "可靠性与安全架构", - "title": "数据一致性方案", - "style": "低饱和", - "prompt": "生成一张数据一致性方案图。订单服务在本地事务中同时写业务表与 Outbox，发布事件到消息系统，下游服务用幂等键更新本地状态；失败分支进入重试、Saga 补偿和定时对账修复。明确标出事实源、事务边界、提交点、至少一次投递和最终一致。中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "62", - "slug": "trust-boundary-threat-model", - "category": "可靠性与安全架构", - "title": "信任边界与威胁模型", - "style": "流程图配色", - "prompt": "生成一张信任边界与威胁模型图。外部用户与第三方位于不可信域，请求穿过公网入口进入应用信任域，再访问数据域和外部能力；在每个跨边界数据流上标身份冒用、篡改、重放、数据泄露等威胁，以及认证、授权、输入校验、加密、限流和审计控制。中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "63", - "slug": "multi-tenant-isolation", - "category": "组织与 AI 生产流程", - "title": "多租户隔离架构", - "style": "飞书经典", - "prompt": "生成一张多租户隔离架构图。顶层是租户入口与身份策略，中层是共享计算池、独立工作空间和专属计算三种选择，底层是共享表逻辑隔离、独立 Schema、独立数据库三级数据隔离；旁边放租户密钥、配额限流和审计。用贯穿全链路的租户上下文标识连接各层，中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "64", - "slug": "team-topology-ownership", - "category": "组织与 AI 生产流程", - "title": "团队拓扑与系统所有权", - "style": "浅色糖果", - "prompt": "生成一张团队拓扑与系统所有权图。展示两个业务流团队分别拥有若干服务，一个平台团队提供共享能力，一个赋能团队短期辅导，一个复杂子系统团队提供专长；团队与系统用所有权实线连接，团队间用 X-as-a-Service、协作、促进三种标注连接，右侧给出升级路径。中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "65", - "slug": "shared-context-architecture", - "category": "组织与 AI 生产流程", - "title": "共享上下文架构", - "style": "低饱和", - "prompt": "生成一张共享上下文架构图。左侧 PRD、ADR、任务、代码、Trace、评测集和复盘作为版本化事实源，经采集索引、权限过滤、检索排序和上下文预算装配，供工程师与多个 Agent 使用；结果与失败样本回写任务、评测和复盘。标出 Owner、时效、权限和引用溯源，中文短标签，不使用产品名、来源标识或水印。" - }, - { - "id": "66", - "slug": "ai-workflow-governance", - "category": "组织与 AI 生产流程", - "title": "AI 工作流与治理", - "style": "飞书经典", - "prompt": "生成一张 AI 工作流与治理架构图。主链为场景定义、模板/Skill、Flow 编排、模型与工具执行、离线评测、审批发布、在线运行；上方治理控制面包含 Owner、风险分级、权限策略和审计，下方反馈闭环包含 Trace、线上指标、失败样本、回滚和模板改进，高风险动作进入人工审批。中文短标签，不使用产品名、来源标识或水印。" - } -] diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/template-catalog.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/template-catalog.md deleted file mode 100644 index a152dd79b..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/template-catalog.md +++ /dev/null @@ -1,151 +0,0 @@ -# 50 类画图模板目录 - -先选关系结构，再替换变量。模板只提供骨架，不代表真实系统一定存在这些节点。默认中文短标签、低信息噪声；流程主链优先 LR，稳定层次优先 TB，角色协作使用泳道，调用先后使用时序。 - -## 01–05 Agent 核心机制 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 01 ReAct 循环 | 解释 Agent 如何边推理边行动 | Agent 根据工具观察持续修正下一步 | 用户目标 → 思考 → 选工具 → 执行 → 观察 → 判断 → 输出/继续 | 环形流程，结束分支向右 | 目标、工具、观察、终止条件 | -| 02 Plan-and-Execute | 复杂任务拆解与执行 | 先形成计划，再逐步执行并按结果调整 | 目标 → 规划器 → 任务列表 → 执行器 → 状态更新 → 重规划/完成 | LR 主链，重规划回边置下 | 计划项、执行器、状态、重规划条件 | -| 03 上下文组装 | 说明模型最终看到哪些信息 | 多种上下文经筛选、排序和预算控制后组装 | 系统指令/历史/记忆/知识/工具结果 → 过滤 → 排序 → 截断 → Prompt | 多源汇聚到中央管道 | 来源、优先级、Token 预算 | -| 04 Agent 记忆 | 区分工作、会话与长期记忆 | 不同记忆按时效和价值读写 | 工作记忆 ↔ 会话记忆 ↔ 长期记忆；抽取 → 评分 → 去重 → 写入 | 三层架构 + 写入旁路 | 记忆层、检索条件、遗忘策略 | -| 05 RAG Agent | 解释带检索的回答链路 | 检索结果必须经过重排和引用约束 | 问题 → 改写 → 检索 → 重排 → 上下文 → 生成 → 引用校验 | LR 数据流 | 数据源、召回数、重排、引用 | - -## 06–10 多 Agent 协作 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 06 Supervisor–Worker | 主管分配多个子任务 | 主管负责任务分解、派发和验收 | 目标 → Supervisor → Worker A/B/C → 结果汇总 → 验收/返工 | 主管居中，工人扇出扇入 | Worker 角色、任务、验收规则 | -| 07 Router–Specialist | 按意图路由领域专家 | 路由只做分类，专家负责领域处理 | 请求 → 意图识别 → Router → 专家 A/B/C → 统一输出 | LR 分支流程 | 路由条件、专家、兜底 | -| 08 Fan-out/Fan-in | 并行搜索、分析或计算 | 独立任务并行完成后统一聚合 | 任务 → 拆分 → 并行节点 → 结果校验 → 聚合 → 输出 | 并行泳道或扇出扇入 | 分片、并发、超时、聚合规则 | -| 09 Generator–Reviewer | 生成与审核闭环 | Reviewer 给出可执行反馈并控制重试 | 需求 → Generator → 草稿 → Reviewer → 通过/反馈 → 修订 | 环形评审流程 | 质量标准、最大轮次、反馈 | -| 10 Handoff 与人工接管 | 跨 Agent 或转人工 | 交接必须携带上下文、状态和未决事项 | Agent A → 交接包 → Agent B/人工 → 确认接收 → 继续处理 | 泳道图 | 触发条件、交接字段、接收方 | - -## 11–15 Agent 开发与调试 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 11 Agent 开发全流程 | 从需求到上线 | Agent 功能需要需求、原型、评测和发布闭环 | 场景定义 → 方案 → Prompt/Tool → 实现 → 评测 → 灰度 → 监控 | 阶段流程 | 场景、指标、门禁、发布策略 | -| 12 Prompt 开发 | Prompt 迭代与版本化 | 变更必须用固定评测集验证 | 编写 → 样例测试 → 批量评测 → 对比 → Review → 版本发布 | LR + 失败回路 | 模板、变量、评测集、阈值 | -| 13 Tool/MCP 接入 | 新工具集成 Agent | 工具契约、权限和失败语义必须先定义 | 需求 → Schema → 服务实现 → 权限 → Agent 注册 → 联调 → 降级 | 双泳道：Agent/Tool Server | Schema、权限、超时、错误码 | -| 14 Agent 评测集 | 构建可持续评测闭环 | 真实失败样本驱动评测集增长 | 样本采集 → 清洗 → 标注 → 数据集 → 执行 → 评分 → 失败回流 | 闭环流程 | 来源、标签、评分器、版本 | -| 15 Agent Trace 调试 | 定位 Agent 失败原因 | 从整条 Trace 下钻到节点、Prompt 和工具 | 失败请求 → Trace → 慢/错节点 → 输入输出 → Tool/Prompt → 根因 → 修复验证 | 诊断树 | Trace ID、节点、错误类型、修复 | - -## 16–20 软件研发流程 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 16 软件开发全流程 | 通用 SDLC | 每阶段有明确产物与门禁 | 需求 → 设计 → 开发 → 测试 → 发布 → 监控 → 复盘 | 阶段主链 | 产物、负责人、门禁 | -| 17 需求到技术方案 | 需求评审和方案设计 | 需求澄清后才进入技术设计 | 原始需求 → 澄清 → 范围 → 评审 → 技术调研 → 方案 → 方案评审 | 产品/研发泳道 | 范围、约束、风险、评审人 | -| 18 TDD | 测试驱动开发 | 先失败测试，再最小实现和重构 | 写测试 → Red → 最小实现 → Green → Refactor → 回归 | 环形流程 | 测试、行为、重构范围 | -| 19 Git/PR/Review | 分支开发与合并 | 自动检查与人工 Review 共同守门 | 建分支 → 提交 → 推送 → PR → CI → Review → 修改 → 合并 | 开发/CI/Reviewer 泳道 | 分支、检查、Reviewer、合并策略 | -| 20 CI/CD | 从提交到生产 | 制品只构建一次，经多环境晋级 | Commit → Build → Test/Scan → Artifact → Staging → 验证 → 灰度 → 全量/回滚 | LR 门禁流程 | 环境、制品、指标、回滚 | - -## 21–25 系统架构 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 21 经典分层架构 | 展示职责边界 | 上层通过稳定接口依赖下层 | 客户端 → 接入层 → 应用层 → 领域层 → 基础设施层 → 存储 | 纵向分层 | 层、组件、允许依赖 | -| 22 单体到微服务演进 | 展示架构阶段变化 | 拆分按业务边界渐进完成 | 模块化单体 → 抽离共享能力 → 拆服务 → 独立数据 → 平台治理 | 时间轴/阶段图 | 阶段、迁移对象、门槛 | -| 23 微服务与网关 | 服务调用和基础设施 | 网关处理横切能力，服务按领域自治 | 客户端 → Gateway → 服务群 → 消息/缓存/数据库 → 可观测平台 | 分层 + 领域分组 | 服务、协议、资源、治理 | -| 24 插件化架构 | 可扩展系统设计 | 核心只依赖扩展契约 | Host → Extension API → Plugin Registry → Plugin A/B/C → 隔离与生命周期 | 核心居中，插件环绕 | 扩展点、插件、加载、隔离 | -| 25 Agent 平台架构 | 展示 Agent 平台全景 | 编排层统一连接模型、知识、工具、记忆和治理 | 应用 → Agent 编排 → 模型/知识/工具/记忆 → 运行与评测 → 存储 | 分层平台架构 | 模块、接口、治理能力 | - -## 26–30 交互与状态 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 26 同步调用时序 | 展示请求调用顺序 | 请求在返回前依次完成鉴权、读取和处理 | 调用方 → API → 服务 → 存储/外部能力 → 返回 | 时序图 | 参与方、请求、响应、超时 | -| 27 异步事件时序 | 消息投递与消费 | 生产与消费解耦，确认和重试独立存在 | Producer → Broker → Consumer → Store → Ack/Retry/DLQ | 时序图 | Topic、确认、重试、幂等 | -| 28 人机审核泳道 | 用户、系统、Agent、人工协作 | 自动处理与人工审批在明确节点交接 | 用户提交 → 系统受理 → Agent 分析 → 低风险自动/高风险人工 → 结果 | 四泳道 | 角色、风险规则、审批 | -| 29 生命周期状态机 | 任务或会话状态 | 状态变化由事件驱动且终态明确 | Created → Running → Waiting → Succeeded/Failed/Cancelled；Retry 回边 | 状态图 | 状态、事件、守卫条件 | -| 30 异常补偿流程 | 失败处理 | 重试、降级、补偿、人工介入按失败类型选择 | 执行 → 失败分类 → 重试/降级/补偿 → 验证 → 人工/终态 | 决策流程 | 错误、次数、补偿、告警 | - -## 31–35 数据与领域建模 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 31 数据处理管道 | 数据从源到消费 | 实时与离线链路可分流后汇聚 | 数据源 → 采集 → 清洗 → 实时/离线计算 → 湖仓 → 服务/报表 | LR 数据流 | 来源、格式、处理、输出 | -| 32 数据血缘 | 上下游影响分析 | 字段或数据集的来源、转换和消费可追踪 | 源表 → 转换任务 → 中间表 → 指标层 → 报表/API | 分层 DAG | 表、字段、任务、消费者 | -| 33 ER 数据模型 | 核心实体关系 | 只展示关键实体、主外键和基数 | 用户/项目/任务/事件/结果等 4–7 实体 | ER 自动布局 | 实体、PK/FK、基数 | -| 34 领域模型 | 聚合和领域关系 | 聚合根控制内部一致性边界 | 聚合根 → 实体/值对象 → 领域事件 → 仓储接口 | 类图/关系图 | 聚合、实体、事件、接口 | -| 35 缓存一致性 | 缓存与数据库协作 | 读写顺序和失效策略决定一致性 | 读请求 → Cache → DB；写请求 → DB → 失效/更新 Cache → 消息补偿 | 双流程并列 | 策略、TTL、补偿、并发 | - -## 36–40 稳定性与安全 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 36 可观测性闭环 | Trace、日志、指标到行动 | 遥测信号必须转成告警、定位和修复 | 服务 → 采集 → 指标/日志/Trace → 分析 → 告警 → 响应 → 修复 | 闭环架构 | 信号、规则、通知、动作 | -| 37 线上故障响应 | 应急处置流程 | 止损优先，定位、恢复与沟通并行 | 发现 → 分级 → 指挥 → 止损 → 定位 → 修复 → 验证 → 复盘 | 多角色泳道 | 等级、角色、SLA、措施 | -| 38 熔断限流降级 | 过载与依赖故障保护 | 先判断风险，再选择限流、熔断或降级 | 请求 → 容量/健康判断 → 限流/熔断/降级 → 探测 → 恢复 | 决策状态流程 | 阈值、策略、探测、恢复 | -| 39 认证授权 | 身份和权限校验 | 认证确认是谁，授权决定能做什么 | 用户 → IdP → Token → Gateway 验证 → Policy 决策 → Resource | 时序 + 信任边界 | 协议、Token、角色、策略 | -| 40 敏感操作审批 | 高风险操作治理 | 权限、风险和人工审批共同守门 | 操作请求 → 身份 → 权限 → 风险评估 → 自动允许/人工审批/拒绝 → 审计 | 泳道/决策流 | 操作、风险、审批人、审计 | - -## 41–45 学习与知识表达 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 41 技术学习路线 | 学习顺序规划 | 基础、进阶、实战、深入逐级推进 | 前置知识 → 基础概念 → 核心机制 → 项目实战 → 调优 → 深入专题 | 时间轴/路线图 | 主题、阶段、练习、里程碑 | -| 42 技术知识脑图 | 快速构建知识全景 | 一个主题从概念、原理、实践、问题展开 | 中心主题 → 概念/原理/实践/工具/问题 → 子项 | 放射脑图 | 主题、分支、关键词 | -| 43 概念依赖图 | 解释概念关系 | 学习顺序由前置依赖决定 | 基础概念 → 中间概念 → 高阶概念；相关/对比边 | DAG/概念图 | 概念、依赖、相关、对比 | -| 44 原理拆解图 | 解释内部工作机制 | 输入经过关键内部模块转成输出 | 输入 → 预处理 → 核心机制 A/B/C → 状态变化 → 输出 | 分层机制图 | 输入、模块、状态、输出 | -| 45 一图看懂某技术 | 综合教学概览 | 定义、架构、流程、场景和限制共同构成全貌 | 是什么 → 核心组件 → 工作流程 → 使用场景 → 优缺点 | 信息分区图 | 主题、组件、场景、限制 | - -## 46–50 规划、演进与决策 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 46 架构阶段演进 | 展示系统演变 | 每阶段解决当前主要矛盾并引入新能力 | 起步 → 模块化 → 服务化 → 平台化 → 智能化 | 时间轴 | 阶段、驱动、能力、代价 | -| 47 项目里程碑 | 计划和依赖沟通 | 阶段、并行任务和关键依赖可视化 | 调研 → 设计 → 开发 → 联调 → 灰度 → 发布；并行工作包 | 甘特/路线图 | 阶段、任务、依赖、负责人 | -| 48 技术选型决策 | 根据条件选择方案 | 选择由规模、复杂度、成本和团队约束共同决定 | 需求条件 → 决策节点 → 方案 A/B/C → 风险检查 → 结论 | 决策树 | 条件、方案、权衡、结论 | -| 49 能力地图 | 展示能力边界和成熟度 | 业务目标由领域能力和平台能力支撑 | 目标 → 能力域 → 二级能力 → 平台支撑；成熟度标记 | 分层卡片 | 目标、能力、成熟度、团队 | -| 50 排障诊断树 | 从现象定位根因 | 按可观测信号逐步缩小问题范围 | 现象 → 范围判断 → 服务/依赖/数据/资源分支 → 验证 → 根因/升级 | 决策树 | 现象、检查项、证据、动作 | - -## 51–54 架构视图 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 51 C4 Context 系统上下文 | 面向全部干系人说明系统职责和外部关系 | 系统作为整体，通过有含义的关系连接用户与外部系统 | 用户/外部系统 → 目标系统 → 外部能力 | 中心辐射 + 系统边界 | 系统、角色、外部系统、关系 | -| 52 C4 Container 容器视图 | 展示系统内部可独立运行或部署的单元 | 容器是可独立运行或存储的单元，关系需标协议与数据 | 用户/外部系统 → 客户端 → 服务 → 存储/消息 | 系统边界内分层 | 容器、职责、协议、数据 | -| 53 C4 Component 组件视图 | 拆解复杂容器内部模块职责与依赖 | 组件只描述同一容器内部的稳定模块边界 | 入口适配 → 应用编排 → 领域组件 → 端口/仓储 | 单容器三层图 | 组件、接口、依赖、端口 | -| 54 部署与运行拓扑 | 说明软件单元实际运行位置和网络隔离 | 实例、集群、网络区和持久化资源共同形成运行边界 | 用户 → 边缘入口 → 应用集群 → 后台集群 → 数据资源 | 网络区 + 集群分层 | 网络区、实例、端口、存储、扩缩容 | - -## 55–58 架构决策 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 55 质量属性效用树 | 把高性能、高可用等目标转成可验证场景 | 业务效用逐层拆成质量属性、场景和优先级 | 业务目标 → 质量属性 → 场景 → 刺激/响应/指标 | 左右树状展开 | 目标、属性、场景、指标、风险 | -| 56 架构权衡图 | 比较候选方案获得什么并牺牲什么 | 选择必须绑定约束、收益、代价与退出成本 | 约束 → 方案 A/B/C → 收益/代价/风险 → 推荐 | 约束 + 方案卡片 + 结论 | 约束、方案、收益、代价、风险 | -| 57 ADR 架构决策记录 | 记录重要架构选择的来龙去脉 | 上下文、选项、后果和复审条件让决策可追溯 | 问题 → 约束 → 选项 → 决策 → 后果 → 复审 | 决策主链 + 后果分支 | 问题、选项、决策、后果、触发器 | -| 58 容量与瓶颈图 | 估算链路中的流量放大、排队与瓶颈 | 峰值、扇出、服务能力和数据增长共同约束容量 | 入口 QPS → 扇出 → 服务容量 → 队列 → 存储 | 流量主链 + 瓶颈高亮 | 流量、扇出、并发、能力、增长 | - -## 59–62 可靠性与安全架构 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 59 故障传播与爆炸半径 | 分析局部故障如何放大并影响用户 | 隔离、超时、熔断和降级共同决定爆炸半径 | 故障源 → 依赖耗尽 → 资源耗尽 → 级联失败 → 用户影响 | 传播链 + 隔离区 | 故障源、共享资源、传播路径、控制点 | -| 60 SLO 与错误预算闭环 | 将可靠性目标连接到告警与发布决策 | 错误预算连接用户体验、运行信号与研发节奏 | 用户旅程 → SLI → SLO → 错误预算 → 行动 → 新周期 | 环形闭环 | SLI、SLO、窗口、预算、燃烧率、行动 | -| 61 数据一致性方案 | 选择跨组件或服务的一致性机制 | 一致性、可用性、复杂度和恢复方式必须共同决策 | 本地事务 → Outbox/事件 → 下游幂等 → 补偿 → 对账 | 正常主链 + 失败恢复路径 | 事实源、事务、事件、幂等、补偿、对账 | -| 62 信任边界与威胁模型 | 识别数据跨信任域时的攻击面和控制 | 每次跨越信任边界都要验证身份、权限、输入和审计 | 外部参与方 → 公网域 → 应用域 → 数据域 → 外部能力 | 分区信任域 + 数据流 | 参与方、数据流、资产、威胁、控制、审计 | - -## 63–66 组织与 AI 生产流程 - -| ID / 模板 | 场景 | 核心结论 | 骨架 | 布局 | 变量 | -|-|-|-|-|-|-| -| 63 多租户隔离架构 | 说明租户在身份、计算、数据和密钥上的隔离 | 隔离是多层边界与成本的组合，不是单一开关 | 租户入口 → 身份策略 → 计算隔离 → 数据隔离 → 密钥/配额/审计 | 资源分层 + 隔离级别 | 租户、身份、计算、数据、密钥、配额 | -| 64 团队拓扑与系统所有权 | 对齐团队、系统边界、Owner 和协作模式 | 清晰所有权与低耦合协作降低系统认知负担 | 业务流团队 ↔ 所属服务；平台/赋能/复杂子系统团队协作 | 团队卡片 + 系统映射 | 团队、系统、Owner、依赖、协作、升级路径 | -| 65 共享上下文架构 | 让人和 Agent 使用同一组可追溯事实源 | 稳定事实源、检索装配、权限与反馈形成共享上下文 | 多类事实源 → 索引与权限 → 上下文装配 → 消费者 → 反馈 | 多源汇聚 + 治理闭环 | 事实源、索引、权限、上下文、消费者、反馈 | -| 66 AI 工作流与治理 | 将个人提示沉淀为可复用、可审批、可评测的生产流程 | 生产流程需要模板、权限、评测、审计和明确责任 | 场景 → 模板 → 编排 → 工具/模型 → 门禁 → 运行 → 审计 → 改进 | 生命周期主链 + 治理控制面 | 场景、流程、权限、门禁、审批、审计、Owner | - -## 通用视觉令牌 - -| 语义 | 背景 | 边框 | -|-|-|-| -| 入口、控制、适配 | `#F0F4FC` | `#5178C6` | -| 核心处理、运行时 | `#EAE2FE` | `#8569CB` | -| 存储、成功、稳定 | `#DFF5E5` | `#509863` | -| 判断、临时、提示 | `#FEF1CE` | `#D4B45B` | -| 错误、拒绝、风险 | `#FEE3E2` | `#D25D5A` | - -正文 `#1F2329`，辅助说明 `#646A73`，普通连线 `#BBBFC4`。分区间距 24–32px，分区内边距 16–24px，整图外边距 48–64px。 diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/template-specs.json b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/template-specs.json deleted file mode 100644 index fb1888dab..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/template-specs.json +++ /dev/null @@ -1,3142 +0,0 @@ -[ - { - "id": "01", - "slug": "react-loop", - "category": "Agent 核心机制", - "title": "ReAct 思考—行动—观察循环", - "scene": "解释 Agent 如何边推理边行动", - "core_conclusion": "Agent 根据工具观察持续修正下一步", - "skeleton": "用户目标 → 思考 → 选工具 → 执行 → 观察 → 判断 → 输出/继续", - "layout": "环形流程，结束分支向右", - "variables": [ - "目标", - "工具", - "观察", - "终止条件" - ], - "audience": [ - "Agent 开发者", - "技术评审者" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "目标", - "工具", - "观察", - "终止条件" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "02", - "03", - "04" - ] - }, - { - "id": "02", - "slug": "plan-and-execute", - "category": "Agent 核心机制", - "title": "Plan-and-Execute 规划执行", - "scene": "复杂任务拆解与执行", - "core_conclusion": "先形成计划，再逐步执行并按结果调整", - "skeleton": "目标 → 规划器 → 任务列表 → 执行器 → 状态更新 → 重规划/完成", - "layout": "LR 主链，重规划回边置下", - "variables": [ - "计划项", - "执行器", - "状态", - "重规划条件" - ], - "audience": [ - "Agent 开发者", - "技术评审者" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "计划项", - "执行器", - "状态", - "重规划条件" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "01", - "03", - "04" - ] - }, - { - "id": "03", - "slug": "context-assembly", - "category": "Agent 核心机制", - "title": "Agent 上下文组装与裁剪", - "scene": "说明模型最终看到哪些信息", - "core_conclusion": "多种上下文经筛选、排序和预算控制后组装", - "skeleton": "系统指令/历史/记忆/知识/工具结果 → 过滤 → 排序 → 截断 → Prompt", - "layout": "多源汇聚到中央管道", - "variables": [ - "来源", - "优先级", - "Token 预算" - ], - "audience": [ - "Agent 开发者", - "技术评审者" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "来源", - "优先级", - "Token 预算" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "01", - "02", - "04" - ] - }, - { - "id": "04", - "slug": "memory-architecture", - "category": "Agent 核心机制", - "title": "Agent 多层记忆架构", - "scene": "区分工作、会话与长期记忆", - "core_conclusion": "不同记忆按时效和价值读写", - "skeleton": "工作记忆 ↔ 会话记忆 ↔ 长期记忆；抽取 → 评分 → 去重 → 写入", - "layout": "三层架构 + 写入旁路", - "variables": [ - "记忆层", - "检索条件", - "遗忘策略" - ], - "audience": [ - "Agent 开发者", - "技术评审者" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "记忆层", - "检索条件", - "遗忘策略" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "01", - "02", - "03" - ] - }, - { - "id": "05", - "slug": "rag-agent", - "category": "Agent 核心机制", - "title": "RAG Agent 检索生成", - "scene": "解释带检索的回答链路", - "core_conclusion": "检索结果必须经过重排和引用约束", - "skeleton": "问题 → 改写 → 检索 → 重排 → 上下文 → 生成 → 引用校验", - "layout": "LR 数据流", - "variables": [ - "数据源", - "召回数", - "重排", - "引用" - ], - "audience": [ - "Agent 开发者", - "技术评审者" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "数据源", - "召回数", - "重排", - "引用" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "01", - "02", - "03" - ] - }, - { - "id": "06", - "slug": "supervisor-worker", - "category": "多 Agent 协作", - "title": "Supervisor–Worker 多 Agent", - "scene": "主管分配多个子任务", - "core_conclusion": "主管负责任务分解、派发和验收", - "skeleton": "目标 → Supervisor → Worker A/B/C → 结果汇总 → 验收/返工", - "layout": "主管居中，工人扇出扇入", - "variables": [ - "Worker 角色", - "任务", - "验收规则" - ], - "audience": [ - "Agent 架构师", - "业务流程 Owner" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "Worker 角色", - "任务", - "验收规则" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "07", - "08", - "09" - ] - }, - { - "id": "07", - "slug": "router-specialist", - "category": "多 Agent 协作", - "title": "Router–Specialist 智能路由", - "scene": "按意图路由领域专家", - "core_conclusion": "路由只做分类，专家负责领域处理", - "skeleton": "请求 → 意图识别 → Router → 专家 A/B/C → 统一输出", - "layout": "LR 分支流程", - "variables": [ - "路由条件", - "专家", - "兜底" - ], - "audience": [ - "Agent 架构师", - "业务流程 Owner" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "路由条件", - "专家", - "兜底" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "06", - "08", - "09" - ] - }, - { - "id": "08", - "slug": "parallel-fan-in", - "category": "多 Agent 协作", - "title": "多 Agent 并行汇总", - "scene": "并行搜索、分析或计算", - "core_conclusion": "独立任务并行完成后统一聚合", - "skeleton": "任务 → 拆分 → 并行节点 → 结果校验 → 聚合 → 输出", - "layout": "并行泳道或扇出扇入", - "variables": [ - "分片", - "并发", - "超时", - "聚合规则" - ], - "audience": [ - "Agent 架构师", - "业务流程 Owner" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "分片", - "并发", - "超时", - "聚合规则" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "06", - "07", - "09" - ] - }, - { - "id": "09", - "slug": "generator-reviewer", - "category": "多 Agent 协作", - "title": "Generator–Reviewer 评审闭环", - "scene": "生成与审核闭环", - "core_conclusion": "Reviewer 给出可执行反馈并控制重试", - "skeleton": "需求 → Generator → 草稿 → Reviewer → 通过/反馈 → 修订", - "layout": "环形评审流程", - "variables": [ - "质量标准", - "最大轮次", - "反馈" - ], - "audience": [ - "Agent 架构师", - "业务流程 Owner" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "质量标准", - "最大轮次", - "反馈" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "06", - "07", - "08" - ] - }, - { - "id": "10", - "slug": "handoff-human", - "category": "多 Agent 协作", - "title": "Agent Handoff 与人工接管", - "scene": "跨 Agent 或转人工", - "core_conclusion": "交接必须携带上下文、状态和未决事项", - "skeleton": "Agent A → 交接包 → Agent B/人工 → 确认接收 → 继续处理", - "layout": "泳道图", - "variables": [ - "触发条件", - "交接字段", - "接收方" - ], - "audience": [ - "Agent 架构师", - "业务流程 Owner" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "触发条件", - "交接字段", - "接收方" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "06", - "07", - "08" - ] - }, - { - "id": "11", - "slug": "agent-development-lifecycle", - "category": "Agent 开发与调试", - "title": "Agent 从需求到上线", - "scene": "从需求到上线", - "core_conclusion": "Agent 功能需要需求、原型、评测和发布闭环", - "skeleton": "场景定义 → 方案 → Prompt/Tool → 实现 → 评测 → 灰度 → 监控", - "layout": "阶段流程", - "variables": [ - "场景", - "指标", - "门禁", - "发布策略" - ], - "audience": [ - "Agent 开发者", - "质量负责人" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "场景", - "指标", - "门禁", - "发布策略" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "12", - "13", - "14" - ] - }, - { - "id": "12", - "slug": "prompt-development", - "category": "Agent 开发与调试", - "title": "Prompt 开发与版本管理", - "scene": "Prompt 迭代与版本化", - "core_conclusion": "变更必须用固定评测集验证", - "skeleton": "编写 → 样例测试 → 批量评测 → 对比 → Review → 版本发布", - "layout": "LR + 失败回路", - "variables": [ - "模板", - "变量", - "评测集", - "阈值" - ], - "audience": [ - "Agent 开发者", - "质量负责人" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "模板", - "变量", - "评测集", - "阈值" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "11", - "13", - "14" - ] - }, - { - "id": "13", - "slug": "tool-mcp-integration", - "category": "Agent 开发与调试", - "title": "Tool/MCP 接入与联调", - "scene": "新工具集成 Agent", - "core_conclusion": "工具契约、权限和失败语义必须先定义", - "skeleton": "需求 → Schema → 服务实现 → 权限 → Agent 注册 → 联调 → 降级", - "layout": "双泳道：Agent/Tool Server", - "variables": [ - "Schema", - "权限", - "超时", - "错误码" - ], - "audience": [ - "Agent 开发者", - "质量负责人" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "Schema", - "权限", - "超时", - "错误码" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "11", - "12", - "14" - ] - }, - { - "id": "14", - "slug": "agent-evaluation-loop", - "category": "Agent 开发与调试", - "title": "Agent 评测集与效果迭代", - "scene": "构建可持续评测闭环", - "core_conclusion": "真实失败样本驱动评测集增长", - "skeleton": "样本采集 → 清洗 → 标注 → 数据集 → 执行 → 评分 → 失败回流", - "layout": "闭环流程", - "variables": [ - "来源", - "标签", - "评分器", - "版本" - ], - "audience": [ - "Agent 开发者", - "质量负责人" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "来源", - "标签", - "评分器", - "版本" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "11", - "12", - "13" - ] - }, - { - "id": "15", - "slug": "agent-trace-debugging", - "category": "Agent 开发与调试", - "title": "Agent Trace 调试与归因", - "scene": "定位 Agent 失败原因", - "core_conclusion": "从整条 Trace 下钻到节点、Prompt 和工具", - "skeleton": "失败请求 → Trace → 慢/错节点 → 输入输出 → Tool/Prompt → 根因 → 修复验证", - "layout": "诊断树", - "variables": [ - "Trace ID", - "节点", - "错误类型", - "修复" - ], - "audience": [ - "Agent 开发者", - "质量负责人" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "Trace ID", - "节点", - "错误类型", - "修复" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "11", - "12", - "13" - ] - }, - { - "id": "16", - "slug": "software-development-lifecycle", - "category": "软件研发流程", - "title": "软件开发全流程", - "scene": "通用 SDLC", - "core_conclusion": "每阶段有明确产物与门禁", - "skeleton": "需求 → 设计 → 开发 → 测试 → 发布 → 监控 → 复盘", - "layout": "阶段主链", - "variables": [ - "产物", - "负责人", - "门禁" - ], - "audience": [ - "研发团队", - "项目负责人" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "产物", - "负责人", - "门禁" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "17", - "18", - "19" - ] - }, - { - "id": "17", - "slug": "requirement-to-design", - "category": "软件研发流程", - "title": "需求评审到技术方案", - "scene": "需求评审和方案设计", - "core_conclusion": "需求澄清后才进入技术设计", - "skeleton": "原始需求 → 澄清 → 范围 → 评审 → 技术调研 → 方案 → 方案评审", - "layout": "产品/研发泳道", - "variables": [ - "范围", - "约束", - "风险", - "评审人" - ], - "audience": [ - "研发团队", - "项目负责人" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "范围", - "约束", - "风险", - "评审人" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "16", - "18", - "19" - ] - }, - { - "id": "18", - "slug": "tdd-cycle", - "category": "软件研发流程", - "title": "TDD Red–Green–Refactor", - "scene": "测试驱动开发", - "core_conclusion": "先失败测试，再最小实现和重构", - "skeleton": "写测试 → Red → 最小实现 → Green → Refactor → 回归", - "layout": "环形流程", - "variables": [ - "测试", - "行为", - "重构范围" - ], - "audience": [ - "研发团队", - "项目负责人" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "测试", - "行为", - "重构范围" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "16", - "17", - "19" - ] - }, - { - "id": "19", - "slug": "git-pr-review", - "category": "软件研发流程", - "title": "Git、PR 与 Code Review", - "scene": "分支开发与合并", - "core_conclusion": "自动检查与人工 Review 共同守门", - "skeleton": "建分支 → 提交 → 推送 → PR → CI → Review → 修改 → 合并", - "layout": "开发/CI/Reviewer 泳道", - "variables": [ - "分支", - "检查", - "Reviewer", - "合并策略" - ], - "audience": [ - "研发团队", - "项目负责人" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "分支", - "检查", - "Reviewer", - "合并策略" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "16", - "17", - "18" - ] - }, - { - "id": "20", - "slug": "cicd-release", - "category": "软件研发流程", - "title": "CI/CD 灰度与回滚", - "scene": "从提交到生产", - "core_conclusion": "制品只构建一次，经多环境晋级", - "skeleton": "Commit → Build → Test/Scan → Artifact → Staging → 验证 → 灰度 → 全量/回滚", - "layout": "LR 门禁流程", - "variables": [ - "环境", - "制品", - "指标", - "回滚" - ], - "audience": [ - "研发团队", - "项目负责人" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "环境", - "制品", - "指标", - "回滚" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "16", - "17", - "18" - ] - }, - { - "id": "21", - "slug": "layered-architecture", - "category": "系统架构", - "title": "经典分层架构", - "scene": "展示职责边界", - "core_conclusion": "上层通过稳定接口依赖下层", - "skeleton": "客户端 → 接入层 → 应用层 → 领域层 → 基础设施层 → 存储", - "layout": "纵向分层", - "variables": [ - "层", - "组件", - "允许依赖" - ], - "audience": [ - "架构师", - "开发与运维团队" - ], - "abstraction_level": "Container / Runtime", - "required_inputs": [ - "层", - "组件", - "允许依赖" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "22", - "23", - "24" - ] - }, - { - "id": "22", - "slug": "monolith-to-microservices", - "category": "系统架构", - "title": "单体到微服务演进", - "scene": "展示架构阶段变化", - "core_conclusion": "拆分按业务边界渐进完成", - "skeleton": "模块化单体 → 抽离共享能力 → 拆服务 → 独立数据 → 平台治理", - "layout": "时间轴/阶段图", - "variables": [ - "阶段", - "迁移对象", - "门槛" - ], - "audience": [ - "架构师", - "开发与运维团队" - ], - "abstraction_level": "Container / Runtime", - "required_inputs": [ - "阶段", - "迁移对象", - "门槛" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "21", - "23", - "24" - ] - }, - { - "id": "23", - "slug": "microservice-gateway", - "category": "系统架构", - "title": "微服务与 API Gateway", - "scene": "服务调用和基础设施", - "core_conclusion": "网关处理横切能力，服务按领域自治", - "skeleton": "客户端 → Gateway → 服务群 → 消息/缓存/数据库 → 可观测平台", - "layout": "分层 + 领域分组", - "variables": [ - "服务", - "协议", - "资源", - "治理" - ], - "audience": [ - "架构师", - "开发与运维团队" - ], - "abstraction_level": "Container / Runtime", - "required_inputs": [ - "服务", - "协议", - "资源", - "治理" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "21", - "22", - "24" - ] - }, - { - "id": "24", - "slug": "plugin-architecture", - "category": "系统架构", - "title": "插件化与扩展点架构", - "scene": "可扩展系统设计", - "core_conclusion": "核心只依赖扩展契约", - "skeleton": "Host → Extension API → Plugin Registry → Plugin A/B/C → 隔离与生命周期", - "layout": "核心居中，插件环绕", - "variables": [ - "扩展点", - "插件", - "加载", - "隔离" - ], - "audience": [ - "架构师", - "开发与运维团队" - ], - "abstraction_level": "Container / Runtime", - "required_inputs": [ - "扩展点", - "插件", - "加载", - "隔离" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "21", - "22", - "23" - ] - }, - { - "id": "25", - "slug": "agent-platform", - "category": "系统架构", - "title": "Agent 平台整体架构", - "scene": "展示 Agent 平台全景", - "core_conclusion": "编排层统一连接模型、知识、工具、记忆和治理", - "skeleton": "应用 → Agent 编排 → 模型/知识/工具/记忆 → 运行与评测 → 存储", - "layout": "分层平台架构", - "variables": [ - "模块", - "接口", - "治理能力" - ], - "audience": [ - "架构师", - "开发与运维团队" - ], - "abstraction_level": "Container / Runtime", - "required_inputs": [ - "模块", - "接口", - "治理能力" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "21", - "22", - "23" - ] - }, - { - "id": "26", - "slug": "synchronous-sequence", - "category": "交互与状态", - "title": "同步服务调用时序", - "scene": "展示请求调用顺序", - "core_conclusion": "请求在返回前依次完成鉴权、读取和处理", - "skeleton": "调用方 → API → 服务 → 存储/外部能力 → 返回", - "layout": "时序图", - "variables": [ - "参与方", - "请求", - "响应", - "超时" - ], - "audience": [ - "开发者", - "测试工程师" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "参与方", - "请求", - "响应", - "超时" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "27", - "28", - "29" - ] - }, - { - "id": "27", - "slug": "asynchronous-sequence", - "category": "交互与状态", - "title": "异步事件消费时序", - "scene": "消息投递与消费", - "core_conclusion": "生产与消费解耦，确认和重试独立存在", - "skeleton": "Producer → Broker → Consumer → Store → Ack/Retry/DLQ", - "layout": "时序图", - "variables": [ - "Topic", - "确认", - "重试", - "幂等" - ], - "audience": [ - "开发者", - "测试工程师" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "Topic", - "确认", - "重试", - "幂等" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "26", - "28", - "29" - ] - }, - { - "id": "28", - "slug": "human-agent-swimlane", - "category": "交互与状态", - "title": "用户、Agent 与人工审核泳道", - "scene": "用户、系统、Agent、人工协作", - "core_conclusion": "自动处理与人工审批在明确节点交接", - "skeleton": "用户提交 → 系统受理 → Agent 分析 → 低风险自动/高风险人工 → 结果", - "layout": "四泳道", - "variables": [ - "角色", - "风险规则", - "审批" - ], - "audience": [ - "开发者", - "测试工程师" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "角色", - "风险规则", - "审批" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "26", - "27", - "29" - ] - }, - { - "id": "29", - "slug": "task-state-machine", - "category": "交互与状态", - "title": "任务生命周期状态机", - "scene": "任务或会话状态", - "core_conclusion": "状态变化由事件驱动且终态明确", - "skeleton": "Created → Running → Waiting → Succeeded/Failed/Cancelled；Retry 回边", - "layout": "状态图", - "variables": [ - "状态", - "事件", - "守卫条件" - ], - "audience": [ - "开发者", - "测试工程师" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "状态", - "事件", - "守卫条件" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "26", - "27", - "28" - ] - }, - { - "id": "30", - "slug": "retry-compensation", - "category": "交互与状态", - "title": "失败重试、降级与补偿", - "scene": "失败处理", - "core_conclusion": "重试、降级、补偿、人工介入按失败类型选择", - "skeleton": "执行 → 失败分类 → 重试/降级/补偿 → 验证 → 人工/终态", - "layout": "决策流程", - "variables": [ - "错误", - "次数", - "补偿", - "告警" - ], - "audience": [ - "开发者", - "测试工程师" - ], - "abstraction_level": "Process / Interaction", - "required_inputs": [ - "错误", - "次数", - "补偿", - "告警" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "26", - "27", - "28" - ] - }, - { - "id": "31", - "slug": "data-pipeline", - "category": "数据与领域建模", - "title": "数据处理管道", - "scene": "数据从源到消费", - "core_conclusion": "实时与离线链路可分流后汇聚", - "skeleton": "数据源 → 采集 → 清洗 → 实时/离线计算 → 湖仓 → 服务/报表", - "layout": "LR 数据流", - "variables": [ - "来源", - "格式", - "处理", - "输出" - ], - "audience": [ - "架构师", - "数据与后端开发者" - ], - "abstraction_level": "Data / Component", - "required_inputs": [ - "来源", - "格式", - "处理", - "输出" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "32", - "33", - "34" - ] - }, - { - "id": "32", - "slug": "data-lineage", - "category": "数据与领域建模", - "title": "数据血缘与影响关系", - "scene": "上下游影响分析", - "core_conclusion": "字段或数据集的来源、转换和消费可追踪", - "skeleton": "源表 → 转换任务 → 中间表 → 指标层 → 报表/API", - "layout": "分层 DAG", - "variables": [ - "表", - "字段", - "任务", - "消费者" - ], - "audience": [ - "架构师", - "数据与后端开发者" - ], - "abstraction_level": "Data / Component", - "required_inputs": [ - "表", - "字段", - "任务", - "消费者" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "31", - "33", - "34" - ] - }, - { - "id": "33", - "slug": "er-model", - "category": "数据与领域建模", - "title": "ER 数据实体关系", - "scene": "核心实体关系", - "core_conclusion": "只展示关键实体、主外键和基数", - "skeleton": "用户/项目/任务/事件/结果等 4–7 实体", - "layout": "ER 自动布局", - "variables": [ - "实体", - "PK/FK", - "基数" - ], - "audience": [ - "架构师", - "数据与后端开发者" - ], - "abstraction_level": "Data / Component", - "required_inputs": [ - "实体", - "PK/FK", - "基数" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "31", - "32", - "34" - ] - }, - { - "id": "34", - "slug": "domain-model", - "category": "数据与领域建模", - "title": "领域模型与类关系", - "scene": "聚合和领域关系", - "core_conclusion": "聚合根控制内部一致性边界", - "skeleton": "聚合根 → 实体/值对象 → 领域事件 → 仓储接口", - "layout": "类图/关系图", - "variables": [ - "聚合", - "实体", - "事件", - "接口" - ], - "audience": [ - "架构师", - "数据与后端开发者" - ], - "abstraction_level": "Data / Component", - "required_inputs": [ - "聚合", - "实体", - "事件", - "接口" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "31", - "32", - "33" - ] - }, - { - "id": "35", - "slug": "cache-consistency", - "category": "数据与领域建模", - "title": "缓存与数据库一致性", - "scene": "缓存与数据库协作", - "core_conclusion": "读写顺序和失效策略决定一致性", - "skeleton": "读请求 → Cache → DB；写请求 → DB → 失效/更新 Cache → 消息补偿", - "layout": "双流程并列", - "variables": [ - "策略", - "TTL", - "补偿", - "并发" - ], - "audience": [ - "架构师", - "数据与后端开发者" - ], - "abstraction_level": "Data / Component", - "required_inputs": [ - "策略", - "TTL", - "补偿", - "并发" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "31", - "32", - "33" - ] - }, - { - "id": "36", - "slug": "observability-loop", - "category": "稳定性与安全", - "title": "指标、日志、Trace 与告警闭环", - "scene": "Trace、日志、指标到行动", - "core_conclusion": "遥测信号必须转成告警、定位和修复", - "skeleton": "服务 → 采集 → 指标/日志/Trace → 分析 → 告警 → 响应 → 修复", - "layout": "闭环架构", - "variables": [ - "信号", - "规则", - "通知", - "动作" - ], - "audience": [ - "SRE", - "安全与服务 Owner" - ], - "abstraction_level": "Runtime / Control", - "required_inputs": [ - "信号", - "规则", - "通知", - "动作" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "37", - "38", - "39" - ] - }, - { - "id": "37", - "slug": "incident-response", - "category": "稳定性与安全", - "title": "线上故障响应", - "scene": "应急处置流程", - "core_conclusion": "止损优先，定位、恢复与沟通并行", - "skeleton": "发现 → 分级 → 指挥 → 止损 → 定位 → 修复 → 验证 → 复盘", - "layout": "多角色泳道", - "variables": [ - "等级", - "角色", - "SLA", - "措施" - ], - "audience": [ - "SRE", - "安全与服务 Owner" - ], - "abstraction_level": "Runtime / Control", - "required_inputs": [ - "等级", - "角色", - "SLA", - "措施" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "36", - "38", - "39" - ] - }, - { - "id": "38", - "slug": "resilience-control", - "category": "稳定性与安全", - "title": "熔断、限流与降级", - "scene": "过载与依赖故障保护", - "core_conclusion": "先判断风险，再选择限流、熔断或降级", - "skeleton": "请求 → 容量/健康判断 → 限流/熔断/降级 → 探测 → 恢复", - "layout": "决策状态流程", - "variables": [ - "阈值", - "策略", - "探测", - "恢复" - ], - "audience": [ - "SRE", - "安全与服务 Owner" - ], - "abstraction_level": "Runtime / Control", - "required_inputs": [ - "阈值", - "策略", - "探测", - "恢复" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "36", - "37", - "39" - ] - }, - { - "id": "39", - "slug": "authentication-authorization", - "category": "稳定性与安全", - "title": "认证、令牌与授权", - "scene": "身份和权限校验", - "core_conclusion": "认证确认是谁，授权决定能做什么", - "skeleton": "用户 → IdP → Token → Gateway 验证 → Policy 决策 → Resource", - "layout": "时序 + 信任边界", - "variables": [ - "协议", - "Token", - "角色", - "策略" - ], - "audience": [ - "SRE", - "安全与服务 Owner" - ], - "abstraction_level": "Runtime / Control", - "required_inputs": [ - "协议", - "Token", - "角色", - "策略" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "36", - "37", - "38" - ] - }, - { - "id": "40", - "slug": "sensitive-operation-approval", - "category": "稳定性与安全", - "title": "敏感操作审批", - "scene": "高风险操作治理", - "core_conclusion": "权限、风险和人工审批共同守门", - "skeleton": "操作请求 → 身份 → 权限 → 风险评估 → 自动允许/人工审批/拒绝 → 审计", - "layout": "泳道/决策流", - "variables": [ - "操作", - "风险", - "审批人", - "审计" - ], - "audience": [ - "SRE", - "安全与服务 Owner" - ], - "abstraction_level": "Runtime / Control", - "required_inputs": [ - "操作", - "风险", - "审批人", - "审计" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "36", - "37", - "38" - ] - }, - { - "id": "41", - "slug": "learning-roadmap", - "category": "学习与知识表达", - "title": "技术学习路线图", - "scene": "学习顺序规划", - "core_conclusion": "基础、进阶、实战、深入逐级推进", - "skeleton": "前置知识 → 基础概念 → 核心机制 → 项目实战 → 调优 → 深入专题", - "layout": "时间轴/路线图", - "variables": [ - "主题", - "阶段", - "练习", - "里程碑" - ], - "audience": [ - "学习者", - "技术讲解者" - ], - "abstraction_level": "Concept", - "required_inputs": [ - "主题", - "阶段", - "练习", - "里程碑" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "42", - "43", - "44" - ] - }, - { - "id": "42", - "slug": "knowledge-mindmap", - "category": "学习与知识表达", - "title": "技术知识脑图", - "scene": "快速构建知识全景", - "core_conclusion": "一个主题从概念、原理、实践、问题展开", - "skeleton": "中心主题 → 概念/原理/实践/工具/问题 → 子项", - "layout": "放射脑图", - "variables": [ - "主题", - "分支", - "关键词" - ], - "audience": [ - "学习者", - "技术讲解者" - ], - "abstraction_level": "Concept", - "required_inputs": [ - "主题", - "分支", - "关键词" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "41", - "43", - "44" - ] - }, - { - "id": "43", - "slug": "concept-dependency", - "category": "学习与知识表达", - "title": "概念关系与知识依赖", - "scene": "解释概念关系", - "core_conclusion": "学习顺序由前置依赖决定", - "skeleton": "基础概念 → 中间概念 → 高阶概念；相关/对比边", - "layout": "DAG/概念图", - "variables": [ - "概念", - "依赖", - "相关", - "对比" - ], - "audience": [ - "学习者", - "技术讲解者" - ], - "abstraction_level": "Concept", - "required_inputs": [ - "概念", - "依赖", - "相关", - "对比" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "41", - "42", - "44" - ] - }, - { - "id": "44", - "slug": "mechanism-breakdown", - "category": "学习与知识表达", - "title": "技术原理内部机制拆解", - "scene": "解释内部工作机制", - "core_conclusion": "输入经过关键内部模块转成输出", - "skeleton": "输入 → 预处理 → 核心机制 A/B/C → 状态变化 → 输出", - "layout": "分层机制图", - "variables": [ - "输入", - "模块", - "状态", - "输出" - ], - "audience": [ - "学习者", - "技术讲解者" - ], - "abstraction_level": "Concept", - "required_inputs": [ - "输入", - "模块", - "状态", - "输出" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "41", - "42", - "43" - ] - }, - { - "id": "45", - "slug": "one-picture-overview", - "category": "学习与知识表达", - "title": "一图看懂某技术", - "scene": "综合教学概览", - "core_conclusion": "定义、架构、流程、场景和限制共同构成全貌", - "skeleton": "是什么 → 核心组件 → 工作流程 → 使用场景 → 优缺点", - "layout": "信息分区图", - "variables": [ - "主题", - "组件", - "场景", - "限制" - ], - "audience": [ - "学习者", - "技术讲解者" - ], - "abstraction_level": "Concept", - "required_inputs": [ - "主题", - "组件", - "场景", - "限制" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "41", - "42", - "43" - ] - }, - { - "id": "46", - "slug": "architecture-evolution", - "category": "规划、演进与决策", - "title": "系统架构阶段演进", - "scene": "展示系统演变", - "core_conclusion": "每阶段解决当前主要矛盾并引入新能力", - "skeleton": "起步 → 模块化 → 服务化 → 平台化 → 智能化", - "layout": "时间轴", - "variables": [ - "阶段", - "驱动", - "能力", - "代价" - ], - "audience": [ - "技术负责人", - "项目干系人" - ], - "abstraction_level": "Decision / Timeline", - "required_inputs": [ - "阶段", - "驱动", - "能力", - "代价" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "47", - "48", - "49" - ] - }, - { - "id": "47", - "slug": "project-milestones", - "category": "规划、演进与决策", - "title": "项目里程碑与依赖", - "scene": "计划和依赖沟通", - "core_conclusion": "阶段、并行任务和关键依赖可视化", - "skeleton": "调研 → 设计 → 开发 → 联调 → 灰度 → 发布；并行工作包", - "layout": "甘特/路线图", - "variables": [ - "阶段", - "任务", - "依赖", - "负责人" - ], - "audience": [ - "技术负责人", - "项目干系人" - ], - "abstraction_level": "Decision / Timeline", - "required_inputs": [ - "阶段", - "任务", - "依赖", - "负责人" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "46", - "48", - "49" - ] - }, - { - "id": "48", - "slug": "technology-selection", - "category": "规划、演进与决策", - "title": "技术选型与选择条件", - "scene": "根据条件选择方案", - "core_conclusion": "选择由规模、复杂度、成本和团队约束共同决定", - "skeleton": "需求条件 → 决策节点 → 方案 A/B/C → 风险检查 → 结论", - "layout": "决策树", - "variables": [ - "条件", - "方案", - "权衡", - "结论" - ], - "audience": [ - "技术负责人", - "项目干系人" - ], - "abstraction_level": "Decision / Timeline", - "required_inputs": [ - "条件", - "方案", - "权衡", - "结论" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "46", - "47", - "49" - ] - }, - { - "id": "49", - "slug": "capability-map", - "category": "规划、演进与决策", - "title": "能力地图与成熟度", - "scene": "展示能力边界和成熟度", - "core_conclusion": "业务目标由领域能力和平台能力支撑", - "skeleton": "目标 → 能力域 → 二级能力 → 平台支撑；成熟度标记", - "layout": "分层卡片", - "variables": [ - "目标", - "能力", - "成熟度", - "团队" - ], - "audience": [ - "技术负责人", - "项目干系人" - ], - "abstraction_level": "Decision / Timeline", - "required_inputs": [ - "目标", - "能力", - "成熟度", - "团队" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "46", - "47", - "48" - ] - }, - { - "id": "50", - "slug": "troubleshooting-tree", - "category": "规划、演进与决策", - "title": "问题排查与诊断决策树", - "scene": "从现象定位根因", - "core_conclusion": "按可观测信号逐步缩小问题范围", - "skeleton": "现象 → 范围判断 → 服务/依赖/数据/资源分支 → 验证 → 根因/升级", - "layout": "决策树", - "variables": [ - "现象", - "检查项", - "证据", - "动作" - ], - "audience": [ - "技术负责人", - "项目干系人" - ], - "abstraction_level": "Decision / Timeline", - "required_inputs": [ - "现象", - "检查项", - "证据", - "动作" - ], - "required_semantics": [ - "主阅读方向", - "节点职责", - "关系或边标签", - "边界与终止条件" - ], - "not_for": [ - "缺少真实上下文时直接照抄", - "需要混合多个抽象层级的一张大图" - ], - "bad_smells": [ - "节点无职责说明", - "箭头无方向或含义", - "示例占位内容未替换" - ], - "related_templates": [ - "46", - "47", - "48" - ] - }, - { - "id": "51", - "slug": "c4-context", - "category": "架构视图", - "title": "C4 Context 系统上下文", - "scene": "向所有干系人说明系统的职责与外部关系", - "core_conclusion": "系统作为一个整体，通过有含义的关系连接用户角色与外部系统", - "skeleton": "用户角色/外部系统 → 目标系统 → 外部能力；目标系统内部不展开", - "layout": "目标系统居中，用户在左，外部系统在右，系统边界清晰", - "variables": [ - "目标系统", - "用户角色", - "外部系统", - "关系说明" - ], - "audience": [ - "产品经理", - "架构师", - "开发与运营干系人" - ], - "abstraction_level": "Context", - "required_inputs": [ - "系统一句话定位", - "用户角色", - "外部依赖", - "双方交互内容" - ], - "required_semantics": [ - "目标系统边界", - "关系方向", - "每条边的业务含义", - "外部系统标识" - ], - "not_for": [ - "展示系统内部组件", - "展示部署实例" - ], - "bad_smells": [ - "在系统内部画服务细节", - "箭头没有业务含义", - "把第三方画进本系统边界" - ], - "related_templates": [ - "52", - "62" - ] - }, - { - "id": "52", - "slug": "c4-container", - "category": "架构视图", - "title": "C4 Container 容器视图", - "scene": "向技术团队展示系统内部可独立运行或部署的单元", - "core_conclusion": "容器是可独立运行或存储的单元，关系需标协议与数据", - "skeleton": "用户/外部系统 → Web/客户端 → API/服务 → 存储/消息/外部能力", - "layout": "大系统边界内分层布局，外部参与方在边界外", - "variables": [ - "系统边界", - "容器", - "职责", - "协议", - "数据存储" - ], - "audience": [ - "架构师", - "开发团队", - "运维团队" - ], - "abstraction_level": "Container", - "required_inputs": [ - "Context 图", - "可部署单元", - "数据存储", - "通信协议" - ], - "required_semantics": [ - "系统边界", - "容器职责", - "协议或数据", - "同步与异步关系" - ], - "not_for": [ - "展示类或函数", - "混入实例级部署信息" - ], - "bad_smells": [ - "把业务模块误当容器", - "同时画类与服务", - "不标通信协议" - ], - "related_templates": [ - "51", - "53", - "54" - ] - }, - { - "id": "53", - "slug": "c4-component", - "category": "架构视图", - "title": "C4 Component 组件视图", - "scene": "拆解一个复杂容器内部的模块职责与依赖", - "core_conclusion": "组件只描述同一容器内部的稳定模块边界", - "skeleton": "入口适配器 → 应用编排 → 领域组件 → 端口/仓储；横切组件旁置", - "layout": "单一容器边界内三层布局", - "variables": [ - "目标容器", - "组件", - "接口", - "依赖方向" - ], - "audience": [ - "负责该容器的开发者", - "代码 Reviewer" - ], - "abstraction_level": "Component", - "required_inputs": [ - "目标容器职责", - "内部模块", - "模块接口", - "外部端口" - ], - "required_semantics": [ - "容器边界", - "组件职责", - "允许依赖方向", - "外部端口" - ], - "not_for": [ - "跨多个服务画全景", - "展示函数调用细节" - ], - "bad_smells": [ - "把其他服务画进容器内部", - "组件颗粒度差异过大", - "循环依赖无解释" - ], - "related_templates": [ - "52", - "34" - ] - }, - { - "id": "54", - "slug": "deployment-runtime-topology", - "category": "架构视图", - "title": "部署与运行拓扑", - "scene": "说明软件单元实际运行在哪里以及网络如何隔离", - "core_conclusion": "运行实例、集群、网络区和持久化资源共同决定故障与扩缩容边界", - "skeleton": "用户 → 边缘入口 → 应用集群 → 后台集群 → 数据资源；管理面旁置", - "layout": "按网络区和运行集群分层，实例在集群边界内", - "variables": [ - "网络区", - "集群", - "实例", - "端口", - "存储", - "扩缩容" - ], - "audience": [ - "架构师", - "SRE", - "运维与安全人员" - ], - "abstraction_level": "Runtime / Deployment", - "required_inputs": [ - "容器视图", - "部署单元", - "网络区域", - "副本与存储" - ], - "required_semantics": [ - "网络边界", - "实例数量", - "入口与端口", - "持久化位置", - "管理面" - ], - "not_for": [ - "只讲逻辑职责", - "缺少部署事实时臆测拓扑" - ], - "bad_smells": [ - "逻辑组件和运行实例混层", - "没有网络边界", - "未区分有状态与无状态" - ], - "related_templates": [ - "52", - "59", - "60" - ] - }, - { - "id": "55", - "slug": "quality-attribute-utility-tree", - "category": "架构决策", - "title": "质量属性效用树", - "scene": "把模糊的“高性能、高可用”转成可验证场景", - "core_conclusion": "业务效用逐层拆成质量属性、具体场景和优先级", - "skeleton": "业务目标 → 质量属性 → 场景 → 刺激/响应/指标；场景标重要性与风险", - "layout": "从左到右树状展开，叶子带优先级标签", - "variables": [ - "业务目标", - "质量属性", - "场景", - "指标", - "重要性", - "风险" - ], - "audience": [ - "架构师", - "产品负责人", - "质量负责人" - ], - "abstraction_level": "Decision / Quality", - "required_inputs": [ - "业务目标", - "质量属性候选", - "量化指标", - "风险偏好" - ], - "required_semantics": [ - "可测场景", - "响应指标", - "重要性", - "技术风险" - ], - "not_for": [ - "仅列功能需求", - "没有量化响应的口号式目标" - ], - "bad_smells": [ - "叶子不可验证", - "只有属性没有场景", - "所有项都是最高优先级" - ], - "related_templates": [ - "56", - "57", - "60" - ] - }, - { - "id": "56", - "slug": "architecture-tradeoff", - "category": "架构决策", - "title": "架构权衡图", - "scene": "比较候选架构方案获得什么并牺牲什么", - "core_conclusion": "架构没有绝对最优，选择必须绑定约束、收益、代价与退出成本", - "skeleton": "约束 → 方案 A/B/C → 收益/代价/风险/退出成本 → 推荐与保留条件", - "layout": "左侧约束，中部三方案卡片，右侧决策结论", - "variables": [ - "约束", - "方案", - "收益", - "代价", - "风险", - "退出条件" - ], - "audience": [ - "技术负责人", - "决策干系人" - ], - "abstraction_level": "Decision", - "required_inputs": [ - "不可变约束", - "候选方案", - "评价维度", - "退出策略" - ], - "required_semantics": [ - "评价维度一致", - "显式放弃项", - "风险", - "复审条件" - ], - "not_for": [ - "只有一个可行方案", - "用主观分数替代理由" - ], - "bad_smells": [ - "只列优点", - "不同方案评价维度不一致", - "结论没有触发条件" - ], - "related_templates": [ - "48", - "55", - "57" - ] - }, - { - "id": "57", - "slug": "adr-decision", - "category": "架构决策", - "title": "ADR 架构决策记录", - "scene": "记录一个重要架构选择的来龙去脉", - "core_conclusion": "决策只有连同上下文、选项、后果和复审条件才可追溯", - "skeleton": "上下文/问题 → 约束 → 选项 → 决策 → 正负后果 → 复审触发条件", - "layout": "横向决策主链，下方并列后果与触发器", - "variables": [ - "问题", - "约束", - "选项", - "决策", - "后果", - "复审信号" - ], - "audience": [ - "架构师", - "未来维护者", - "评审者" - ], - "abstraction_level": "Decision / Record", - "required_inputs": [ - "决策问题", - "约束", - "候选项", - "选择依据", - "已知后果" - ], - "required_semantics": [ - "决策状态", - "被否决选项", - "正负后果", - "复审触发器" - ], - "not_for": [ - "日常小改动", - "无法说明约束的拍脑袋结论" - ], - "bad_smells": [ - "只写结论", - "不记录被放弃方案", - "缺少复审条件" - ], - "related_templates": [ - "48", - "55", - "56" - ] - }, - { - "id": "58", - "slug": "capacity-bottleneck", - "category": "架构决策", - "title": "容量与瓶颈图", - "scene": "估算请求在链路中的放大、排队与首个瓶颈", - "core_conclusion": "容量由峰值流量、扇出、服务能力和存储增长共同约束", - "skeleton": "入口 QPS → 扇出 → 服务容量 → 队列 → 存储；节点标需求/能力/利用率", - "layout": "横向流量主链，瓶颈节点红色高亮，旁路写增长驱动", - "variables": [ - "峰值流量", - "扇出倍数", - "并发", - "处理能力", - "队列", - "数据增长" - ], - "audience": [ - "架构师", - "SRE", - "性能工程师" - ], - "abstraction_level": "Runtime / Capacity", - "required_inputs": [ - "峰值流量", - "请求扇出", - "节点能力", - "数据保留期" - ], - "required_semantics": [ - "单位一致", - "需求与能力对照", - "首个瓶颈", - "缓冲与降载点" - ], - "not_for": [ - "没有任何容量假设", - "精确硬件压测报告" - ], - "bad_smells": [ - "只写平均值", - "忽略扇出", - "吞吐与并发单位混淆" - ], - "related_templates": [ - "54", - "59", - "60" - ] - }, - { - "id": "59", - "slug": "fault-propagation", - "category": "可靠性与安全架构", - "title": "故障传播与爆炸半径", - "scene": "分析一个局部故障如何放大并影响用户", - "core_conclusion": "隔离边界、超时、熔断和降级决定故障爆炸半径", - "skeleton": "故障源 → 依赖耗尽 → 线程/连接池耗尽 → 级联失败 → 用户影响；控制点切断传播", - "layout": "左到右传播链，隔离区用虚线框，止损点置于边上", - "variables": [ - "故障源", - "依赖", - "共享资源", - "传播路径", - "隔离措施", - "用户影响" - ], - "audience": [ - "SRE", - "架构师", - "服务 Owner" - ], - "abstraction_level": "Runtime / Failure", - "required_inputs": [ - "调用拓扑", - "共享资源", - "超时重试策略", - "用户影响" - ], - "required_semantics": [ - "故障方向", - "共享资源", - "隔离边界", - "止损控制", - "影响范围" - ], - "not_for": [ - "事故处置流程", - "没有调用关系的风险清单" - ], - "bad_smells": [ - "只画根因不画传播", - "忽略重试放大", - "止损点没有位置" - ], - "related_templates": [ - "37", - "38", - "54", - "60" - ] - }, - { - "id": "60", - "slug": "slo-error-budget", - "category": "可靠性与安全架构", - "title": "SLO 与错误预算闭环", - "scene": "把可靠性目标连接到告警和发布决策", - "core_conclusion": "错误预算把用户体验、运行信号和研发节奏连接起来", - "skeleton": "用户旅程 → SLI → SLO → 错误预算 → 消耗速率 → 告警/发布/改进 → 新周期", - "layout": "环形闭环，中间放错误预算状态", - "variables": [ - "用户旅程", - "SLI", - "目标值", - "窗口", - "预算", - "燃烧率", - "行动" - ], - "audience": [ - "SRE", - "产品负责人", - "研发团队" - ], - "abstraction_level": "Runtime / Reliability", - "required_inputs": [ - "关键用户旅程", - "SLI", - "SLO", - "统计窗口", - "行动策略" - ], - "required_semantics": [ - "指标定义", - "目标窗口", - "预算消耗", - "燃烧率", - "决策动作" - ], - "not_for": [ - "组件级监控罗列", - "没有用户体验映射的指标墙" - ], - "bad_smells": [ - "把 SLA 当 SLO", - "只设目标不定义行动", - "忽略统计窗口" - ], - "related_templates": [ - "36", - "37", - "58", - "59" - ] - }, - { - "id": "61", - "slug": "data-consistency-strategy", - "category": "可靠性与安全架构", - "title": "数据一致性方案", - "scene": "选择跨组件或跨服务的数据一致性机制", - "core_conclusion": "一致性强度、可用性、复杂度和恢复方式必须一起决策", - "skeleton": "业务操作 → 本地事务 → Outbox/事件 → 下游幂等 → Saga/补偿 → 对账修复", - "layout": "横向主链，上方标正常路径，下方标失败与恢复路径", - "variables": [ - "事实源", - "事务边界", - "事件", - "幂等键", - "补偿", - "对账" - ], - "audience": [ - "架构师", - "后端开发者", - "数据 Owner" - ], - "abstraction_level": "Data / Runtime", - "required_inputs": [ - "事实源", - "事务边界", - "一致性要求", - "失败恢复策略" - ], - "required_semantics": [ - "事实源", - "提交点", - "投递保证", - "幂等点", - "补偿与对账" - ], - "not_for": [ - "单数据库内简单事务", - "不区分事实源的双写图" - ], - "bad_smells": [ - "数据库和消息双写无原子性", - "没有幂等点", - "补偿不可逆却未说明" - ], - "related_templates": [ - "27", - "30", - "35" - ] - }, - { - "id": "62", - "slug": "trust-boundary-threat-model", - "category": "可靠性与安全架构", - "title": "信任边界与威胁模型", - "scene": "识别数据跨越信任域时的攻击面与控制措施", - "core_conclusion": "每次跨越信任边界都必须验证身份、权限、输入和审计", - "skeleton": "外部参与方 → 公网边界 → 应用信任域 → 数据信任域 → 外部能力；边界标威胁与控制", - "layout": "同心或分区信任域，数据流穿越边界", - "variables": [ - "参与方", - "数据流", - "信任域", - "资产", - "威胁", - "控制", - "审计" - ], - "audience": [ - "安全工程师", - "架构师", - "服务 Owner" - ], - "abstraction_level": "Context / Security", - "required_inputs": [ - "数据流", - "敏感资产", - "信任域", - "攻击面", - "控制措施" - ], - "required_semantics": [ - "信任边界", - "敏感数据", - "攻击方向", - "认证授权", - "输入校验", - "审计点" - ], - "not_for": [ - "纯权限角色表", - "不含数据流的安全清单" - ], - "bad_smells": [ - "边界和系统边界混淆", - "只标威胁不标控制", - "敏感数据没有落点" - ], - "related_templates": [ - "39", - "40", - "51" - ] - }, - { - "id": "63", - "slug": "multi-tenant-isolation", - "category": "组织与 AI 生产流程", - "title": "多租户隔离架构", - "scene": "说明不同租户在身份、计算、数据和密钥上的隔离", - "core_conclusion": "隔离不是单一开关，而是多层边界与成本的组合", - "skeleton": "租户入口 → 身份与策略 → 计算隔离 → 数据隔离 → 密钥/配额/审计", - "layout": "纵向分层，横向展示共享、逻辑隔离、物理隔离三级选择", - "variables": [ - "租户", - "身份", - "计算", - "数据", - "密钥", - "配额", - "审计" - ], - "audience": [ - "SaaS 架构师", - "安全工程师", - "平台团队" - ], - "abstraction_level": "Container / Security", - "required_inputs": [ - "租户模型", - "敏感级别", - "共享策略", - "成本约束" - ], - "required_semantics": [ - "租户上下文传播", - "数据过滤点", - "密钥边界", - "配额", - "审计" - ], - "not_for": [ - "单租户系统", - "只画 RBAC 不画资源隔离" - ], - "bad_smells": [ - "租户 ID 只在入口校验", - "共享缓存键无租户维度", - "后台任务丢失租户上下文" - ], - "related_templates": [ - "39", - "40", - "62" - ] - }, - { - "id": "64", - "slug": "team-topology-ownership", - "category": "组织与 AI 生产流程", - "title": "团队拓扑与系统所有权", - "scene": "对齐团队、系统边界、Owner 与协作模式", - "core_conclusion": "清晰所有权和低耦合协作降低系统认知负担", - "skeleton": "业务流团队 ↔ 所属服务；平台团队提供能力；赋能团队短期协助；复杂子系统团队提供专长", - "layout": "团队卡片与系统边界双层映射，边标协作模式", - "variables": [ - "团队", - "系统", - "Owner", - "依赖", - "协作模式", - "升级路径" - ], - "audience": [ - "技术管理者", - "架构师", - "团队负责人" - ], - "abstraction_level": "Organization / Ownership", - "required_inputs": [ - "团队清单", - "系统清单", - "Owner", - "协作关系" - ], - "required_semantics": [ - "唯一 Owner", - "系统边界", - "依赖方向", - "协作模式", - "升级路径" - ], - "not_for": [ - "个人汇报关系图", - "没有系统所有权的数据" - ], - "bad_smells": [ - "一个系统多个模糊 Owner", - "依赖没有协作方式", - "组织框与系统框混为一层" - ], - "related_templates": [ - "49", - "65", - "66" - ] - }, - { - "id": "65", - "slug": "shared-context-architecture", - "category": "组织与 AI 生产流程", - "title": "共享上下文架构", - "scene": "让人和 Agent 使用同一组可追溯事实源", - "core_conclusion": "共享上下文由稳定事实源、检索装配、权限和反馈闭环构成", - "skeleton": "PRD/ADR/任务/代码/Trace/评测/复盘 → 索引与权限 → 上下文装配 → 人与 Agent → 反馈回写", - "layout": "多源汇聚，中间上下文层，右侧消费者，下方治理闭环", - "variables": [ - "事实源", - "索引", - "权限", - "上下文预算", - "消费者", - "反馈" - ], - "audience": [ - "AI 平台团队", - "研发团队", - "知识管理者" - ], - "abstraction_level": "Organization / Information", - "required_inputs": [ - "事实源", - "Owner", - "更新频率", - "权限", - "消费场景" - ], - "required_semantics": [ - "事实源 Owner", - "版本与时效", - "权限过滤", - "引用溯源", - "反馈回写" - ], - "not_for": [ - "单次 Prompt 拼装", - "没有 Owner 的文档堆积" - ], - "bad_smells": [ - "复制多份事实源", - "权限在检索后才过滤", - "上下文没有引用来源" - ], - "related_templates": [ - "03", - "04", - "43", - "64", - "66" - ] - }, - { - "id": "66", - "slug": "ai-workflow-governance", - "category": "组织与 AI 生产流程", - "title": "AI 工作流与治理", - "scene": "把个人提示词沉淀为可复用、可审批、可评测的生产流程", - "core_conclusion": "生产级 AI 工作流需要模板、权限、评测、审计和明确的人类责任", - "skeleton": "场景 → 模板/Skill → Flow 编排 → 工具与模型 → 评测门禁 → 发布运行 → 监控审计 → 改进；高风险分支人工审批", - "layout": "横向生命周期主链，上方治理控制面，下方反馈闭环", - "variables": [ - "场景", - "模板", - "流程", - "权限", - "门禁", - "审批", - "审计", - "Owner" - ], - "audience": [ - "AI 平台负责人", - "业务 Owner", - "安全与质量团队" - ], - "abstraction_level": "Organization / Governance", - "required_inputs": [ - "生产场景", - "风险等级", - "工具权限", - "评测门禁", - "责任人" - ], - "required_semantics": [ - "Owner", - "风险分级", - "权限边界", - "评测门禁", - "人工审批", - "审计", - "回滚" - ], - "not_for": [ - "个人一次性实验", - "没有责任人的自动化流程" - ], - "bad_smells": [ - "Prompt 直接进生产", - "高风险操作无审批", - "只有效果指标没有安全指标" - ], - "related_templates": [ - "11", - "13", - "14", - "40", - "64", - "65" - ] - } -] diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/visual-examples.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/visual-examples.md deleted file mode 100644 index 290488f0b..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/references/visual-examples.md +++ /dev/null @@ -1,295 +0,0 @@ -# 50 类画图模板：图片示例 - -本文件是 `feishu-tech-diagram` 的正式视觉索引。先在 `template-catalog.md` 选模板，再查看同编号图片确认关系结构、阅读方向、分组和回边。图片中的节点均为通用占位内容，使用时必须替换为当前文档中的真实信息。 - -## Agent 核心机制 - -### 01 ReAct 思考—行动—观察循环 - -![ReAct 思考—行动—观察循环](../assets/samples/01-react-loop.svg) - -### 02 Plan-and-Execute 规划执行 - -![Plan-and-Execute 规划执行](../assets/samples/02-plan-and-execute.svg) - -### 03 Agent 上下文组装与裁剪 - -![Agent 上下文组装与裁剪](../assets/samples/03-context-assembly.svg) - -### 04 Agent 多层记忆架构 - -![Agent 多层记忆架构](../assets/samples/04-memory-architecture.svg) - -### 05 RAG Agent 检索生成 - -![RAG Agent 检索生成](../assets/samples/05-rag-agent.svg) - -## 多 Agent 协作 - -### 06 Supervisor–Worker 多 Agent - -![Supervisor–Worker 多 Agent](../assets/samples/06-supervisor-worker.svg) - -### 07 Router–Specialist 智能路由 - -![Router–Specialist 智能路由](../assets/samples/07-router-specialist.svg) - -### 08 多 Agent 并行汇总 - -![多 Agent 并行汇总](../assets/samples/08-parallel-fan-in.svg) - -### 09 Generator–Reviewer 评审闭环 - -![Generator–Reviewer 评审闭环](../assets/samples/09-generator-reviewer.svg) - -### 10 Agent Handoff 与人工接管 - -![Agent Handoff 与人工接管](../assets/samples/10-handoff-human.svg) - -## Agent 开发与调试 - -### 11 Agent 从需求到上线 - -![Agent 从需求到上线](../assets/samples/11-agent-development-lifecycle.svg) - -### 12 Prompt 开发与版本管理 - -![Prompt 开发与版本管理](../assets/samples/12-prompt-development.svg) - -### 13 Tool/MCP 接入与联调 - -![Tool/MCP 接入与联调](../assets/samples/13-tool-mcp-integration.svg) - -### 14 Agent 评测集与效果迭代 - -![Agent 评测集与效果迭代](../assets/samples/14-agent-evaluation-loop.svg) - -### 15 Agent Trace 调试与归因 - -![Agent Trace 调试与归因](../assets/samples/15-agent-trace-debugging.svg) - -## 软件研发流程 - -### 16 软件开发全流程 - -![软件开发全流程](../assets/samples/16-software-development-lifecycle.svg) - -### 17 需求评审到技术方案 - -![需求评审到技术方案](../assets/samples/17-requirement-to-design.svg) - -### 18 TDD Red–Green–Refactor - -![TDD Red–Green–Refactor](../assets/samples/18-tdd-cycle.svg) - -### 19 Git、PR 与 Code Review - -![Git、PR 与 Code Review](../assets/samples/19-git-pr-review.svg) - -### 20 CI/CD 灰度与回滚 - -![CI/CD 灰度与回滚](../assets/samples/20-cicd-release.svg) - -## 系统架构 - -### 21 经典分层架构 - -![经典分层架构](../assets/samples/21-layered-architecture.svg) - -### 22 单体到微服务演进 - -![单体到微服务演进](../assets/samples/22-monolith-to-microservices.svg) - -### 23 微服务与 API Gateway - -![微服务与 API Gateway](../assets/samples/23-microservice-gateway.svg) - -### 24 插件化与扩展点架构 - -![插件化与扩展点架构](../assets/samples/24-plugin-architecture.svg) - -### 25 Agent 平台整体架构 - -![Agent 平台整体架构](../assets/samples/25-agent-platform.svg) - -## 交互与状态 - -### 26 同步服务调用时序 - -![同步服务调用时序](../assets/samples/26-synchronous-sequence.svg) - -### 27 异步事件消费时序 - -![异步事件消费时序](../assets/samples/27-asynchronous-sequence.svg) - -### 28 用户、Agent 与人工审核泳道 - -![用户、Agent 与人工审核泳道](../assets/samples/28-human-agent-swimlane.svg) - -### 29 任务生命周期状态机 - -![任务生命周期状态机](../assets/samples/29-task-state-machine.svg) - -### 30 失败重试、降级与补偿 - -![失败重试、降级与补偿](../assets/samples/30-retry-compensation.svg) - -## 数据与领域建模 - -### 31 数据处理管道 - -![数据处理管道](../assets/samples/31-data-pipeline.svg) - -### 32 数据血缘与影响关系 - -![数据血缘与影响关系](../assets/samples/32-data-lineage.svg) - -### 33 ER 数据实体关系 - -![ER 数据实体关系](../assets/samples/33-er-model.svg) - -### 34 领域模型与类关系 - -![领域模型与类关系](../assets/samples/34-domain-model.svg) - -### 35 缓存与数据库一致性 - -![缓存与数据库一致性](../assets/samples/35-cache-consistency.svg) - -## 稳定性与安全 - -### 36 指标、日志、Trace 与告警闭环 - -![指标、日志、Trace 与告警闭环](../assets/samples/36-observability-loop.svg) - -### 37 线上故障响应 - -![线上故障响应](../assets/samples/37-incident-response.svg) - -### 38 熔断、限流与降级 - -![熔断、限流与降级](../assets/samples/38-resilience-control.svg) - -### 39 认证、令牌与授权 - -![认证、令牌与授权](../assets/samples/39-authentication-authorization.svg) - -### 40 敏感操作审批 - -![敏感操作审批](../assets/samples/40-sensitive-operation-approval.svg) - -## 学习与知识表达 - -### 41 技术学习路线图 - -![技术学习路线图](../assets/samples/41-learning-roadmap.svg) - -### 42 技术知识脑图 - -![技术知识脑图](../assets/samples/42-knowledge-mindmap.svg) - -### 43 概念关系与知识依赖 - -![概念关系与知识依赖](../assets/samples/43-concept-dependency.svg) - -### 44 技术原理内部机制拆解 - -![技术原理内部机制拆解](../assets/samples/44-mechanism-breakdown.svg) - -### 45 一图看懂某技术 - -![一图看懂某技术](../assets/samples/45-one-picture-overview.svg) - -## 规划、演进与决策 - -### 46 系统架构阶段演进 - -![系统架构阶段演进](../assets/samples/46-architecture-evolution.svg) - -### 47 项目里程碑与依赖 - -![项目里程碑与依赖](../assets/samples/47-project-milestones.svg) - -### 48 技术选型与选择条件 - -![技术选型与选择条件](../assets/samples/48-technology-selection.svg) - -### 49 能力地图与成熟度 - -![能力地图与成熟度](../assets/samples/49-capability-map.svg) - -### 50 问题排查与诊断决策树 - -![问题排查与诊断决策树](../assets/samples/50-troubleshooting-tree.svg) - -## 架构视图 - -### 51 C4 Context 系统上下文 - -![C4 Context 系统上下文](../assets/samples/51-c4-context.svg) - -### 52 C4 Container 容器视图 - -![C4 Container 容器视图](../assets/samples/52-c4-container.svg) - -### 53 C4 Component 组件视图 - -![C4 Component 组件视图](../assets/samples/53-c4-component.svg) - -### 54 部署与运行拓扑 - -![部署与运行拓扑](../assets/samples/54-deployment-runtime-topology.svg) - -## 架构决策 - -### 55 质量属性效用树 - -![质量属性效用树](../assets/samples/55-quality-attribute-utility-tree.svg) - -### 56 架构权衡图 - -![架构权衡图](../assets/samples/56-architecture-tradeoff.svg) - -### 57 ADR 架构决策记录 - -![ADR 架构决策记录](../assets/samples/57-adr-decision.svg) - -### 58 容量与瓶颈图 - -![容量与瓶颈图](../assets/samples/58-capacity-bottleneck.svg) - -## 可靠性与安全架构 - -### 59 故障传播与爆炸半径 - -![故障传播与爆炸半径](../assets/samples/59-fault-propagation.svg) - -### 60 SLO 与错误预算闭环 - -![SLO 与错误预算闭环](../assets/samples/60-slo-error-budget.svg) - -### 61 数据一致性方案 - -![数据一致性方案](../assets/samples/61-data-consistency-strategy.svg) - -### 62 信任边界与威胁模型 - -![信任边界与威胁模型](../assets/samples/62-trust-boundary-threat-model.svg) - -## 组织与 AI 生产流程 - -### 63 多租户隔离架构 - -![多租户隔离架构](../assets/samples/63-multi-tenant-isolation.svg) - -### 64 团队拓扑与系统所有权 - -![团队拓扑与系统所有权](../assets/samples/64-team-topology-ownership.svg) - -### 65 共享上下文架构 - -![共享上下文架构](../assets/samples/65-shared-context-architecture.svg) - -### 66 AI 工作流与治理 - -![AI 工作流与治理](../assets/samples/66-ai-workflow-governance.svg) diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/scripts/render_lark_skill_doc.py b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/scripts/render_lark_skill_doc.py deleted file mode 100644 index 2686fd10f..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/scripts/render_lark_skill_doc.py +++ /dev/null @@ -1,75 +0,0 @@ -#!/usr/bin/env python3 -from __future__ import annotations - -import html -import json -from pathlib import Path - - -SKILL = Path(__file__).resolve().parents[1] -PROMPTS = json.loads((SKILL / "references/diagram-prompts.json").read_text()) -SPECS = { - row["id"]: row - for row in json.loads((SKILL / "references/template-specs.json").read_text()) -} - - -def esc(value: object) -> str: - return html.escape(str(value), quote=True) - - -parts: list[str] = [ - "Feishu Tech Diagram Skill（66 类可编辑模板）", - '

用于技术文档中的架构图、流程图、Agent 工作流和学习图。66 个示例均以飞书画板交付，节点、文字和连线可继续编辑。

', - "

Skill 定义

", - '
name: feishu-tech-diagram
description: 为飞书技术文档生成、重绘和校验可编辑图表，并沉淀可复用模板。
', - "

目标

", - "
  • 读者在三秒内辨认主链、系统边界或状态变化。
  • 一张图只表达一个核心结论，图和正文互补。
  • 最终交付物是可编辑画板，不以 PNG/JPEG 代替模板。
  • 模板使用中性名称，不携带真实业务、账号或来源信息。
", - "

必做流程

", - '
  1. 读取上下文。 获取目标章节、相邻表格和已有画板。
  2. 整理图意图卡。 写清结论、读者、层级、主链、分组、异常和方向。
  3. 选择模板。 按要回答的问题选择关系结构，而不是按外观选。
  4. 替换内容并预览。 检查文字、节点、连线、边界和失败路径。
  5. 写入并回读。 覆盖前 dry-run，写入后验证节点可编辑。
', - "

图意图卡

", - '
项目要回答的问题
一句话结论读者看完图应该记住什么？
目标读者产品、研发、SRE、安全还是管理者？
抽象层级Context、Container、Component、Runtime、Process 还是 Decision？
主链从哪里开始，经过哪些关键节点，到哪里结束？
分组与边界哪些节点属于同一层、角色、系统或信任域？
分支与异常哪里会判断、重试、降级、补偿、回滚或人工接管？
', - "

画板交付规则

", - '
  • 通过 <whiteboard type="svg"> 导入基础形状、文字和连线。
  • 每个画板紧跟对应模板说明，不集中堆在文档末尾。
  • 位图只用于临时预览，不作为模板交付。
  • 写入后至少通过 preview、source 或 raw 一种方式回读。
', - "

66 类可复用模板

", - "

每个模板包含适用场景、核心结论、推荐布局、必备语义和一个可编辑画板。使用时必须替换示例里的通用节点。

", -] - -categories: list[str] = [] -for prompt in PROMPTS: - if prompt["category"] not in categories: - categories.append(prompt["category"]) - -for category in categories: - parts.append(f"

{esc(category)}

") - for prompt in (row for row in PROMPTS if row["category"] == category): - spec = SPECS[prompt["id"]] - asset = ( - "@skills/feishu-tech-diagram/assets/samples/" - f"{prompt['id']}-{prompt['slug']}.svg" - ) - semantics = "、".join(spec["required_semantics"]) - parts.extend( - [ - f"

{esc(prompt['id'])} {esc(prompt['title'])}

", - f"

适用场景：{esc(spec['scene'])}

", - f"

核心结论：{esc(spec['core_conclusion'])}

", - f"

推荐布局：{esc(spec['layout'])}

", - f"

必备语义：{esc(semantics)}

", - f'', - ] - ) - -parts.extend( - [ - "

布局与文字规则

", - "
  • 主节点控制在 6–12 个；边超过 15 条或多条跨层回边时拆图。
  • 横向主链用 LR，稳定层次用 TB，角色协作用泳道，调用先后用时序。
  • 节点使用短标题和一行说明；关键边写协议、动作、数据或条件。
  • Context、安全与部署图必须明确系统、信任或运行边界。
", - "

最小图组

", - '
目标推荐组合
系统说明Context + Container
核心链路Container + 时序图或数据流
生产评审Container + 部署拓扑 + 故障传播 + SLO
安全评审Context + 信任边界 + 认证授权 + 敏感操作审批
Agent 系统Context + Agent 平台 + 执行时序 + 工具权限 + Trace/Eval
', - "

交付检查

", - "
  • 画板中的节点、文字和连线可以继续编辑。
  • 主链、结论与边界三秒内可辨认。
  • 不含无依据新增的组件、依赖、日期或指标。
  • 箭头有方向，关键边有协议、动作、数据或条件。
  • 无文字截断、节点重叠、明显交叉线或大面积空白。
", - "

版本：66 类可编辑模板；同步日期：2026-08-10。

", - ] -) - -print("".join(parts)) diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/tests/validate_assets.py b/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/tests/validate_assets.py deleted file mode 100644 index 481e7b832..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/feishu-tech-diagram/tests/validate_assets.py +++ /dev/null @@ -1,111 +0,0 @@ -#!/usr/bin/env python3 -from __future__ import annotations - -import json -import re -import subprocess -import sys -import xml.etree.ElementTree as ET -from pathlib import Path - - -SKILL = Path(__file__).resolve().parents[1] -EXPECTED_IDS = [f"{value:02d}" for value in range(1, 67)] -FORBIDDEN_TEXT = ( - "generated by", - "由 ai 生成", - "watermark", - "session_url", - "chat_url", -) -FORBIDDEN_SVG_TAGS = {"image", "script", "foreignObject", "iframe"} - - -def load_json(relative: str): - path = SKILL / relative - if not path.is_file(): - raise AssertionError(f"missing required file: {relative}") - return json.loads(path.read_text()) - - -def assert_ids(name: str, rows: list[dict]) -> None: - ids = [str(row["id"]) for row in rows] - assert ids == EXPECTED_IDS, f"{name} ids mismatch: {ids}" - - -def local_name(tag: str) -> str: - return tag.rsplit("}", 1)[-1] - - -def validate_svg(path: Path) -> None: - text = path.read_text() - lowered = re.sub(r"\s+", " ", text.lower()) - for marker in FORBIDDEN_TEXT: - assert marker not in lowered, f"forbidden marker {marker!r} in {path.name}" - - root = ET.fromstring(text) - assert local_name(root.tag) == "svg", f"not an svg root: {path.name}" - assert root.get("viewBox") or root.get("viewbox"), f"missing viewBox: {path.name}" - for node in root.iter(): - tag = local_name(node.tag) - assert tag not in FORBIDDEN_SVG_TAGS, f"forbidden <{tag}> in {path.name}" - for attr in ("href", "src"): - value = node.get(attr, "") - assert not value.startswith(("http://", "https://", "data:")), ( - f"external resource in {path.name}: {value[:40]}" - ) - - -def validate_renderer() -> None: - renderer = SKILL / "scripts/render_lark_skill_doc.py" - if not renderer.exists(): - return - output = subprocess.check_output([sys.executable, str(renderer)], text=True, cwd=SKILL.parents[1]) - assert output.count("") == 1 - assert output.count("<h4>") == 66 - assert output.count('<whiteboard type="svg" path="@') == 66 - assert "<img " not in output - root = ET.fromstring(f"<root>{output}</root>") - children = list(root) - template_indexes = [i for i, node in enumerate(children) if node.tag == "h4"] - assert len(template_indexes) == 66 - for index in template_indexes: - end = next((i for i in template_indexes if i > index), len(children)) - section = children[index:end] - assert sum(node.tag == "whiteboard" for node in section) == 1, ( - f"template without exactly one whiteboard: {children[index].text}" - ) - - -def main() -> None: - prompts = load_json("references/diagram-prompts.json") - specs = load_json("references/template-specs.json") - manifest = load_json("assets/sample-manifest.json")["samples"] - assert_ids("prompts", prompts) - assert_ids("specs", specs) - assert_ids("manifest", manifest) - - svg_files = sorted((SKILL / "assets/samples").glob("*.svg")) - svg_ids = [path.name.split("-", 1)[0] for path in svg_files] - assert svg_ids == EXPECTED_IDS, f"svg ids mismatch: {svg_ids}" - - for row, path in zip(manifest, svg_files): - expected = SKILL / row["svg_path"] - assert expected.resolve() == path.resolve(), f"manifest path mismatch: {row['id']}" - assert row["status"] == "ready", f"asset not ready: {row['id']}" - validate_svg(path) - - required_spec_fields = { - "id", "slug", "category", "title", "scene", "core_conclusion", "skeleton", - "layout", "variables", "audience", "abstraction_level", "required_inputs", - "required_semantics", "not_for", "bad_smells", "related_templates", - } - for row in specs: - assert required_spec_fields <= row.keys(), f"missing spec fields: {row['id']}" - - validate_renderer() - print("validated prompts=66 specs=66 manifest=66 svg=66") - - -if __name__ == "__main__": - main() diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/SKILL.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/SKILL.md deleted file mode 100644 index 85bf970a1..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/SKILL.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -name: resume-optimization -description: Resume structure, achievement bullet formulas, ATS optimization, and job-targeted tailoring for software engineers. Use when reviewing resumes, crafting achievement bullets, extracting keywords from job descriptions, or tailoring content for specific roles. -argument-hint: <job-description-text-or-url> -allowed-tools: Read, Glob, Grep, Write, AskUserQuestion, Skill, WebFetch ---- - -# Resume Optimization - -Comprehensive guidance for creating effective software engineering resumes that pass ATS systems and resonate with hiring managers. - -## When to Use This Skill - -- Reviewing or improving a software engineer's resume -- Crafting impactful achievement bullets from work experience -- Optimizing resume content for ATS keyword matching -- Tailoring a resume for a specific job description -- Understanding modern resume structure and formatting - -## Core Principles - -### The Resume's Purpose - -A resume is a **marketing document**, not a job history. Its purpose is to: - -1. Pass ATS screening (keyword matching) -2. Capture a recruiter's attention (6-second scan) -3. Demonstrate value through quantified achievements -4. Secure an interview opportunity - -### What Makes Engineering Resumes Different - -Software engineering resumes should emphasize: - -- **Technical impact**: Specific technologies, scale, and performance improvements -- **Business outcomes**: Revenue, cost savings, user growth, time savings -- **Leadership signals**: Mentoring, cross-team collaboration, technical decisions -- **Quantification**: Numbers that demonstrate scope and impact - -## Resume Structure Quick Reference - -### Recommended Section Order - -1. **Contact Information** - Name, email, phone, LinkedIn, GitHub (optional) -2. **Professional Summary** (optional) - 2-3 sentences for senior roles -3. **Skills** - Technical skills organized by category -4. **Experience** - Reverse chronological, 3-5 most relevant roles -5. **Projects** (optional) - For junior engineers or career changers -6. **Education** - Degrees, certifications, relevant coursework - -### Length Guidelines - -| Experience Level | Recommended Length | -| ---------------- | ------------------ | -| 0-5 years | 1 page | -| 5-10 years | 1-2 pages | -| 10+ years | 2 pages max | - -### Formatting Essentials - -- **Font**: Clean, readable (Calibri, Arial, Garamond - 10-12pt) -- **Margins**: 0.5-1 inch -- **Format**: PDF (preserves formatting) -- **File naming**: `FirstName_LastName_Resume.pdf` - -## Achievement Bullet Formula - -### Action Verb + Specific Task + Quantifiable Result - -```text -[Strong Action Verb] [specific task/project] using [tools/methods], resulting in [quantified outcome]. -``` - -### Technical Project Bullets - -For software projects, do not write a feature list. Each bullet should show: - -1. **Problem** - the non-trivial engineering challenge. -2. **Approach** - the abstraction, architecture, algorithm, integration, or reliability mechanism used. -3. **Result** - the measurable or concrete engineering outcome. - -Prefer engineering mechanisms over raw variable names or local implementation trivia. For example, write "source-file state snapshot with metadata version checks" instead of "mtime / size / indexed_at", unless those fields are directly relevant to the target role. - -Avoid weak verbs such as "supported", "integrated", or "implemented" unless followed by the concrete design. Good project bullets should explain *how* the capability works, not only that it exists. - -When possible, include an order-of-magnitude result: - -```text -Optimized unchanged-session indexing with source-file state snapshots and metadata version checks, skipping parsing and full-text index rebuilds for unchanged sessions and reducing a 250-session reload from 2s+ to 10ms-level latency. -``` - -For projects involving many named products, mention product names once in the project description, then use generic terms such as "Agent", "source", "provider", or "target runtime" in bullets to avoid noisy repetition. - -Do not overclaim concurrency or distributed systems. If the implementation uses batched writes and yields the event loop, call it "batched processing" or "event-loop yielding", not "parallel indexing". - -### Strong Action Verbs by Category - -| Category | Verbs | -| -------- | ----- | -| Technical | Architected, Built, Deployed, Engineered, Implemented, Integrated, Migrated, Optimized, Refactored, Scaled | -| Design | Analyzed, Designed, Documented, Modeled, Prototyped, Researched, Specified | -| Leadership | Championed, Coached, Led, Mentored, Pioneered, Spearheaded | -| Impact | Achieved, Boosted, Delivered, Improved, Increased, Reduced, Saved, Streamlined | - -### Quantification Types - -- **Time**: "Reduced deploy time from 2 hours to 15 minutes" -- **Money**: "Saved $50K/year in infrastructure costs" -- **Scale**: "Scaled system to handle 1M daily requests" -- **Improvement**: "Improved test coverage from 40% to 85%" -- **Frequency**: "Reduced support tickets by 70%" - -## ATS Optimization - -### What ATS Systems Look For - -1. **Keyword matching** - Skills, tools, technologies from job description -2. **Job title alignment** - Titles that match or relate to the target role -3. **Section structure** - Standard sections that ATS can parse -4. **Clean formatting** - No tables, columns, graphics, or headers/footers - -### ATS-Friendly Practices - -- Use standard section headings ("Experience", "Skills", "Education") -- Include both spelled-out terms AND acronyms ("Continuous Integration (CI)") -- Mirror exact phrases from job descriptions -- Avoid images, icons, or non-text elements -- Use bullet points (-, *, •) not custom symbols - -### Keyword Extraction Strategy - -When tailoring for a job description: - -1. **Identify required skills** - Listed in "Required" or "Must have" sections -2. **Note preferred skills** - Listed in "Nice to have" or "Preferred" -3. **Capture soft skills** - Leadership, communication, collaboration terms -4. **Extract action verbs** - What the job says you'll "do" or "lead" -5. **Match technologies** - Specific tools, languages, frameworks mentioned - -## Tailoring Strategy - -### The 80/20 Rule - -- **80% base resume**: Core experience and skills that apply broadly -- **20% customization**: Targeted adjustments for each application - -### What to Customize - -1. **Professional Summary** - Align with job's key requirements -2. **Skills Section** - Reorder to prioritize job's requirements -3. **Achievement Bullets** - Emphasize relevant accomplishments -4. **Keywords** - Incorporate exact terms from job description - -### Red Flags to Avoid - -- Generic objective statements ("Seeking a challenging position...") -- Job duties instead of achievements ("Responsible for...") -- Unexplained gaps without context -- Typos or inconsistent formatting -- Outdated technologies prominently featured - -## References - -The guidance in this Skill is self-contained. Use the section headings above to -jump directly to resume structure, achievement bullets, ATS optimization, or -job tailoring without relying on other Skills or agents. - -## User-Facing Interface - -When invoked directly by the user, this skill tailors a resume for a specific job description. - -### Execution Workflow - -1. **Parse Arguments** - Extract job description text or URL from `$ARGUMENTS`. If URL provided, fetch the job description content. If no arguments, ask the user for the job description. -2. **Extract Keywords** - Analyze the job description for required skills, preferred skills, soft skills, action verbs, and specific technologies. -3. **Find Resume** - Search for the user's resume in common locations (current directory, `docs/`, `~/.claude/temp/`). If not found, ask the user for the resume location. -4. **Analyze Gaps** - Compare resume content against job description keywords. Identify missing keywords, weak achievement bullets, and alignment opportunities. -5. **Generate Tailored Output** - Produce: - - Keyword match report (matched vs missing) - - Rewritten achievement bullets incorporating job keywords - - Suggested skills section reordering - - Professional summary tailored to the role - - ATS optimization recommendations -6. **Offer to Apply Changes** - Ask user if they want changes applied directly to their resume file. - -## Version History - -- v1.0.0 (2025-12-23): Initial release with core resume optimization guidance diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/SKILL.zh.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/SKILL.zh.md deleted file mode 100644 index 166fb4649..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/SKILL.zh.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -name: resume-optimization -description: 面向软件工程师的简历结构、成就 bullet、ATS 优化和岗位定制。用于审阅简历、编写成就 bullet、从 JD 提取关键词或针对具体岗位调整内容。 -argument-hint: <job-description-text-or-url> -allowed-tools: Read, Glob, Grep, Write, AskUserQuestion, Skill, WebFetch ---- - -# 简历优化 - -为软件工程师创建高质量简历的综合指南，目标是通过 ATS 系统筛选，并让招聘经理快速看到价值。 - -## 何时使用 - -- 审阅或改进软件工程师简历。 -- 将工作经历改写成有影响力的成就 bullet。 -- 针对 ATS 关键词匹配优化简历。 -- 根据具体职位描述定制简历。 -- 理解现代简历结构和格式。 - -## 核心原则 - -### 简历的目的 - -简历是**营销文档**，不是工作流水账。它的目的包括： - -1. 通过 ATS 筛选。 -2. 在招聘者 6 秒扫描中抓住注意力。 -3. 用量化成果证明价值。 -4. 获得面试机会。 - -### 工程师简历的重点 - -软件工程师简历应该突出： - -- **技术影响**：具体技术、规模、性能改进。 -- **业务结果**：收入、成本节省、用户增长、时间节省。 -- **领导信号**：指导他人、跨团队协作、技术决策。 -- **量化**：用数字证明范围和影响。 - -## 简历结构速查 - -推荐顺序： - -1. **联系方式**：姓名、邮箱、电话、LinkedIn、GitHub（可选）。 -2. **职业摘要**（可选）：高级岗位可用 2-3 句话。 -3. **技能**：按类别组织技术技能。 -4. **经历**：倒序，保留最相关的 3-5 段经历。 -5. **项目**（可选）：适合初级工程师或转行者。 -6. **教育**：学历、证书、相关课程。 - -长度建议：0-5 年 1 页；5-10 年 1-2 页；10 年以上最多 2 页。 - -## 成就 bullet 公式 - -### 动作动词 + 具体任务 + 可量化结果 - -```text -[强动作动词] [具体任务/项目] using [工具/方法], resulting in [量化结果]. -``` - -量化类型包括时间、成本、规模、改进幅度和频次。 - -### 技术项目 bullet 写法 - -软件项目不要写成功能列表。每条 bullet 应该讲清楚： - -1. **问题**：解决了什么非平凡工程问题。 -2. **方案**：设计了什么抽象、架构、算法、适配层、集成链路或可靠性机制。 -3. **结果**：让什么变快、更稳、更可扩展、更易运维或更好用。 - -优先写工程机制，不要堆别人看不懂的变量名或本地实现字段。比如写“源文件状态快照 + 关联元数据版本校验”，通常比写“mtime / size / indexed_at”更适合简历，除非这些字段本身就是面试重点。 - -避免空泛的“支持”“接入”“实现”。如果必须用这些动词，后面要补上具体设计。好的项目 bullet 应该解释能力是**怎么做出来的**，而不只是写“支持了什么”。 - -有性能优化时，用量级结果增强可信度： - -```text -设计基于源文件状态快照的增量索引机制，结合关联元数据版本校验避免无效重建，使未变化会话跳过解析与全文索引更新，将约 250 个会话的加载耗时从 2s+ 优化至 10ms 级。 -``` - -涉及多个产品名时，项目描述里点一次即可；bullet 里可以用 Agent、来源、Provider、目标运行时等泛称，避免反复堆产品名。 - -不要夸大并发或分布式能力。如果实现只是分批写入和让出事件循环，应写“分批处理”或“事件循环让出”，不要写“并行索引”。 - -## ATS 优化 - -ATS 通常关注关键词匹配、岗位名称对齐、标准章节结构和干净格式。使用标准章节标题，保留职位描述里的精确表达，避免图片、图标、复杂表格、页眉页脚等不易解析的元素。 - -## 定制策略 - -使用 80/20 规则：80% 是通用基础简历，20% 针对目标岗位调整。重点定制职业摘要、技能顺序、成就 bullet 和关键词。 - -## 直接调用时的工作流 - -1. 解析职位描述文本或 URL。 -2. 提取必需技能、加分技能、软技能、动作动词和技术关键词。 -3. 找到用户简历；找不到时询问位置。 -4. 对比简历和 JD，识别缺失关键词、弱 bullet 和对齐机会。 -5. 输出关键词匹配报告、重写后的 bullet、技能区调整建议、岗位定制摘要和 ATS 优化建议。 -6. 询问用户是否要直接应用修改。 diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/metadata.json b/apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/metadata.json deleted file mode 100644 index 99740a5da..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/resume-optimization/metadata.json +++ /dev/null @@ -1,10 +0,0 @@ -{ - "tags": [ - "resume-optimization", - "career", - "writing" - ], - "sourceLabel": "bundled original skill", - "categoryId": "writing", - "sourceUrl": "https://github.com/melodic-software/claude-code-plugins/blob/main/plugins/soft-skills/skills/resume-optimization/SKILL.md" -} diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/SKILL.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/SKILL.md deleted file mode 100644 index 568336ffa..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/SKILL.md +++ /dev/null @@ -1,441 +0,0 @@ ---- -name: rewrite-technical-tutorial -description: Use when drafting, restructuring, or reviewing a Chinese technical tutorial whose concept order is hard to follow, code lacks context, diagrams are missing or misplaced, implementation scopes are mixed, facts are version-sensitive, or prose sounds machine-generated. ---- - -# 技术教程写作与审校 - -> **判断一篇教程是否写清楚，不看它覆盖了多少名词，而看新读者能否沿着同一条因果链，回答“为什么需要、何时发生、数据长什么样、代码怎么推进、失败后怎么办”。** - -本 Skill 用于把源码分析、实现笔记和已有技术文章整理成工程师真正能读懂、能核对、能照着实现的教程。默认读者没有看过参考仓库、上游教程和作者之前的对话，也不知道某个产品的内部术语。 - -## 一、先确定任务模式 - -开始工作前先判断用户要的是哪一种交付。模式不同，允许执行的动作也不同。 - -- **只做 Review：**读取全文和必要证据，只报告问题；未经授权不要改文档。 -- **直接改写：**完成结构分析后直接编辑用户指定的范围，并在写后重新读取验证。 -- **逐条讨论：**一次只处理一处，固定给出“当前文本 → 问题 → 准备怎么改 → 修改后文本”，用户确认后再继续。 -- **从零写作：**先建立读者问题、事实边界和章节骨架，再开始写正文；不要从某段代码直接扩写。 - -**用户要求“整篇重写”时，重新设计全文结构；用户只点名一节时，保留其余内容。**不要把整篇重写退化成同义词替换，也不要借局部修改顺手改动无关章节。 - -任务模式一旦确定，后文所有“修改、返工、写入和写后验证”要求只适用于直接改写、逐条讨论中已获确认的条目，以及从零写作。**只做 Review 时始终保持只读：可以读取、核对证据、预览和报告问题，但禁止 update、insert、delete、overwrite 或替用户修正文档。** - -## 二、写作前先建立四张清单 - -动笔前先把材料整理成四张简短清单。它们不一定出现在成稿中，但必须在写作者脑中明确。 - -### 1. 读者问题清单 - -每章只围绕一个主要运行问题展开。问题要能被实现行为回答，不要只是模块名称。 - -- 好：**模型什么时候会创建任务清单，清单保存在哪里？** -- 好：**上下文接近预算时，Harness 在下一次请求前做什么？** -- 差：介绍任务清单工具。 -- 差：深入理解 Context Management。 - -### 2. 事实清单 - -把材料按证据强度分开，写作时不要混用语气。 - -- **通用机制：**不依赖某个产品版本的设计原理。 -- **教学实现：**为了说明机制而写的最小 Harness、示例阈值和辅助函数。 -- **真实源码事实：**可以从指定文件、测试或提交直接确认的行为。 -- **当前产品行为：**需要当前官方文档或当前版本源码支持的结论。 -- **作者推断：**由现象或局部源码推得，必须降低表述强度并说明依据。 - -### 3. 状态清单 - -技术机制只要涉及状态，就必须回答下面五个问题： - -1. **谁写入：**模型、Harness、用户、工具还是异步回调？ -2. **何时写入：**任务开始、步骤切换、请求前、工具执行后还是异常恢复时？ -3. **存在哪里：**当前函数变量、会话内存、消息历史、本地文件、数据库还是对象存储？ -4. **能活多久：**是否能跨循环、跨 compact、跨会话、跨进程重启？ -5. **怎样恢复：**下一轮通过什么引用、字段或加载逻辑重新拿到？恢复失败会怎样？ - -**“已经保存”不是完整结论。必须同时说明保存位置、生命周期和读取路径。** - -### 4. 术语清单 - -记录第一次出现的产品名、对象、字段和函数。每个术语第一次出现时立刻解释，不要先使用三次，再在后文补定义。默认读者不知道参考项目，也不要用“和上一章一样”“参考项目里也是这样”承担解释责任。 - -## 三、先搭整体心智模型，再拆实现细节 - -如果一个机制包含三个以上连续步骤、三个以上角色，或者存在正常与异常两条路径，先给整体流程。读者先知道自己在地图上的位置，后面的函数和字段才有意义。 - -### 推荐的章节顺序 - -1. **具体问题：**用真实任务或故障说明为什么需要当前机制。 -2. **触发入口：**由谁决定启动，满足什么条件时发生。 -3. **整体流程图：**只画本章主线、关键判断和返回位置。 -4. **图后拆解：**用三到五个并列要点说明每个阶段分别做什么。 -5. **数据长相：**先给一份具体请求、状态或结果示例。 -6. **核心实现：**按主流程顺序展示代码，不按仓库目录顺序贴文件。 -7. **状态与副作用：**解释消息、内存、文件或数据库怎样变化。 -8. **失败路径：**说明未知工具、参数错误、超限、重试、降级或中断。 -9. **范围边界：**区分教学示例、源码快照和当前产品行为。 -10. **结果验证：**直接展示运行后的关键状态或输出，不留下未执行的“试一下”。 - -这是一条依赖顺序，不是要求每章都写十个小节。简单机制可以合并；复杂机制也可以拆章。**判断标准是读者是否在遇到细节前已经拥有理解该细节所需的信息。** - -### 段落之间必须有真实交接 - -- 上一段产生一个结果，下一段解释谁消费这个结果。 -- 上一段提出一个限制，下一段引出为限制而存在的机制。 -- 上一段定义一种数据，下一段展示代码怎样读取或修改它。 -- 如果两段只是主题相近，却没有因果、时序或数据关系，就不要用“因此”“接下来”硬接。 - -删除纯报幕句，如“这一节先看”“接下来继续分析”“到这里完整链路已经形成”。标题已经承担导航作用，正文应直接提供信息。 - -## 四、机制解释必须回答的八个问题 - -写完一个机制后，逐项检查；任何一项缺失，都可能让读者只记住名词而不理解运行行为。 - -1. **为什么存在：**没有它时会出现什么具体问题？ -2. **谁触发：**模型主动调用、Harness 自动判断、用户操作，还是外部事件？ -3. **何时触发：**明确阶段、条件和不会触发的情况。 -4. **输入长什么样：**给一份最小但真实的数据示例。 -5. **内部怎样推进：**按时间顺序说清关键判断和调用。 -6. **结果写到哪里：**消息历史、会话状态、文件或持久化存储？ -7. **谁继续使用：**下一轮模型、下游工具、主 Agent 还是用户界面？ -8. **失败后怎样处理：**报错、重试、回滚、降级、跳过还是保留现场？ - -### 先解释“谁决定”，再解释“怎么执行” - -Agent 教程常把触发者写混。例如任务清单工具可能由模型决定何时调用，Harness 只暴露工具并保存结果；上下文压缩通常由 Harness 在请求前根据预算判断，不是模型每次主动请求；权限确认可能由 Harness 发起并等待用户决定。**把这些行为都写成“系统会调用”会抹掉最重要的控制边界。** - -### 先给数据长相，再给抽象函数 - -读者第一次看到任务项、`tool_use`、消息历史或压缩摘要时，先展示一个具体对象。抽象代码只有在读者知道字段含义后才容易理解。 - -```json -[ - {"content": "定位失败测试", "status": "completed"}, - {"content": "修改重试逻辑", "status": "in_progress"}, - {"content": "运行回归测试", "status": "pending"} -] -``` - -然后再解释：一次任务清单写入会提交完整数组，Handler 对整份快照做校验和保存；它不是只发送“把第二项改成完成”的增量命令。若真实实现不同，以证据为准。 - -## 五、代码讲解规则 - -> **代码不是章节的开场白，也不是事实本身。**代码必须出现在读者已经知道它位于哪一步、由谁调用、输入输出是什么之后。 - -### 1. 先标明代码身份 - -- **可运行示例：**依赖、定义顺序、参数和辅助函数必须完整。 -- **真实源码：**注明版本或提交，保留证明结论所需的上下游。 -- **行为示意：**明确标为伪代码或简化实现，不要伪装成可直接运行的 API。 - -### 2. 每段代码前先交代六件事 - -1. 它位于整体流程的哪一步； -2. 谁会调用它； -3. 触发条件是什么； -4. 输入对象有哪些关键字段； -5. 返回值或副作用写到哪里； -6. 读者应该重点观察哪个判断、字段或调用。 - -### 3. 陌生抽象必须用具体调用展开 - -不要只写“通过 Handler Map 动态分发”。先给一份映射，再把一次请求展开： - -```python -TOOL_HANDLERS = { - "read_file": run_read, - "write_file": run_write, -} - -# 模型请求：name="read_file", input={"path": "README.md", "limit": 20} -handler = TOOL_HANDLERS.get(block.name) - -if handler is None: - # 工具名不存在时也要返回 tool_result，模型才能看到失败原因并调整下一步 - output = f"Unknown tool: {block.name}" -else: - # **block.input 把参数字典展开为：run_read(path="README.md", limit=20) - output = handler(**block.input) -``` - -代码后再补充真正的新信息：这段兜底只处理未知工具名；参数校验、执行异常、权限拒绝和超时仍需要在调用边界单独处理。不要把代码注释逐句翻译成正文。 - -### 4. 注释解释“为什么”和“之后发生什么” - -优先注释以下信息： - -- 为什么此处重新读取状态，而不是沿用旧值； -- 某个判断会让循环继续、停止、重试还是降级； -- 锁、版本号、权限 Hook 或轮数上限在防止什么； -- 请求 ID、tool_use_id 或版本字段怎样把调用与结果对应起来； -- 当前调用产生了什么文件、消息或数据库副作用； -- 下一轮模型或下游模块怎样拿到该结果。 - -不要写“获取 Handler”“执行函数”这类只复述语法的注释；只有初学者确实无法理解某个语法时，才用一个具体等价调用解释一次。 - -### 5. 省略辅助函数时必须显式说明 - -主流程可以保留 `normalize_todos()`、`render_todos()` 等函数名而不展开实现，但代码前必须说明它们是本文省略的辅助函数，并各用一句话交代输入、输出和副作用。不要让读者猜它们来自标准库、SDK 还是作者自定义代码。 - -### 6. 代码展示顺序服从运行顺序 - -- 先展示 Tool Schema 或输入结构，再展示消费它的 Handler。 -- 先展示主循环中的调用位置，再展开被调用函数。 -- 先展示正常路径，再单独展示异常恢复，不要在开头把所有分支揉成一个大函数。 -- 图、正文和代码必须使用同一顺序、同一名称和同一数量的阶段。 - -### 7. 结果要直接给出 - -如果文章展示“运行后会发生什么”，作者应实际执行或通过测试验证，并直接给出关键结果。不要保留 `python example.py` 之类未经执行、依赖本地目录结构的“试一下”。无法执行时，明确写这是预期输出，不要假装验证过。 - -## 六、图示不是装饰，而是阅读顺序的一部分 - -### 1. 什么时候必须先画整体图 - -- 流程有三个以上连续阶段； -- 涉及模型、Harness、工具、用户等三个以上角色； -- 正常路径之外还有恢复、重试或降级路径； -- 状态会在内存、消息、文件或数据库之间迁移； -- 下文将连续解释多个函数，读者需要先知道它们在主链路中的位置。 - -**整体流程图应放在详细步骤之前，而不是章节末尾用于总结。**先用一两段提出问题并界定范围，随后放图，再用三到五点解释图中的阶段。 - -### 2. 图型选择 - -- **流程图：**展示判断顺序、分支和返回主循环的位置。 -- **时序图：**展示模型、Harness、工具和用户之间的请求与返回。 -- **状态图：**展示 pending、in_progress、completed 等状态由谁改变。 -- **数据边界图：**展示哪些内容留在会话内存，哪些写入消息、文件或持久化存储。 -- **架构图：**用于读者已经理解主流程后，再说明模块分层和依赖边界。 - -### 3. 每张图写之前先回答三个问题 - -1. 读者看完图应该回答什么问题？ -2. 图中每条箭头代表控制流、数据流还是反馈？ -3. 正文和代码在哪里证明这条箭头确实存在？ - -节点优先写动作和状态变化，不要只堆模块名。图后解释最容易误读的边、状态和边界，不要把每个框重新念一遍。 - -### 4. 图文一致性检查 - -- 图画并行，代码是否真的并发调度？ -- 图画持久化，代码是否只是写入会话内存？ -- 图画摘要返回，文件副作用是否仍通过共享工作目录保留？ -- 图写五个阶段，正文、表格和代码是否也都是五个？ -- 图写 200KB，代码比较的究竟是字节、字符还是 token？ - -插入后必须查看实际渲染效果，检查字号、换行、箭头方向、颜色对比和移动端可读性。DSL 能编译不等于图已经能读。 - -## 七、事实、版本与度量单位 - -### 1. 不把实现快照写成产品契约 - -- 工具名称、默认开关、阈值、提醒条件和 Prompt 文本都可能随版本变化。 -- 精确内部常量必须附版本、提交或日期；无法定位时删除数字，改写为机制级描述。 -- 官方文档能证明公开行为，源码能证明某个版本的实现；二者的证据范围不同。 -- 不要因为教学 Harness 没实现某能力，就断言真实产品不支持；也不要把产品当前行为倒推成教学代码已经具备。 - -### 2. 单位必须从代码语义出发 - -- `len(text)` 通常不是 KB，也不等于 token。 -- 字符数、编码后的字节数和模型 token 数必须分别命名。 -- 上下文预算使用 token 时，图、公式、正文和日志都保持 token 口径。 -- 估算 token 与 API 返回的实际 usage 是两种数据，不能混为同一指标。 - -### 3. 强结论必须满足完整条件 - -- **“无损”：**原始内容仍存在、引用仍保留、权限可用、保留期未过且恢复路径实际可达。否则只能写“在这些条件下可恢复”。 -- **“隔离”：**分别说明上下文隔离、进程隔离、文件系统隔离和权限隔离。独立消息历史不等于独立工作目录。 -- **“并行”：**必须存在并发调度或重叠执行证据；多个任务依次循环仍是串行。 -- **“幂等”：**说明幂等键、冲突处理、状态条件和重复请求返回结果。 -- **“自动恢复”：**说明触发条件、重试边界、保留状态和最终失败出口。 - -## 八、分点与流程图讲解 - -技术内容不是越密越好。**一段话同时出现多个步骤、条件或结果时，先拆结构，再润色句子。**读者应该能快速看出内容是在讲执行顺序、并列条件，还是背景原因。 - -### 1. 先判断使用编号还是项目符号 - -1. **存在先后顺序：**使用 `1. 2. 3.`。适用于调用流程、状态变化、异常恢复和操作步骤。 -2. **内容彼此并列：**使用项目符号。适用于触发条件、字段说明、约束、风险和检查项。 -3. **需要解释因果：**保留短段落。背景、原因和结论不要为了排版强行拆成列表。 - -### 2. 长段落必须拆开 - -一段中出现三个以上动作、条件或对象时，优先改成“引导句 + 列表”。 - -- 引导句只说明下面这组内容的共同主题。 -- 每一点只讲一个步骤或一个判断维度。 -- 同一组列表保持相同句式和抽象层级。 -- 单个列表项通常控制在一到两句话；仍然很长时，再拆成子项。 -- 不要在一个项目中同时解释触发条件、内部实现、存储位置和失败处理。 - -**如果一句话需要连续使用“然后、同时、如果、最后”才能讲完，通常已经应该拆成编号步骤。** - -### 3. 流程图后必须按顺序解释 - -流程图不能独自承担正文。图片后紧接编号说明，默认按下面四个问题展开： - -1. **入口：**谁触发流程，输入是什么。 -2. **主路径：**各阶段按什么顺序执行，每一步改变了什么数据或状态。 -3. **分支：**在哪个条件下走向不同路径，失败后回到哪里。 -4. **结果：**最终产物写到哪里，下一轮由谁继续使用。 - -如果图中已经标出步骤编号，图后的说明必须沿用同一编号、名称和顺序。不要把图里的框逐字念一遍；重点解释**为什么进入下一步、状态发生了什么变化，以及哪条边最容易被误解**。 - -### 4. 代码流程也使用同一套编号 - -一段代码包含多个阶段时，代码前先列出整体步骤；代码后再按相同编号解释关键实现。图、正文和代码中的步骤名称必须一致。 - -1. 代码前说明本段覆盖哪些步骤。 -2. 代码注释标出关键状态变化和分支原因。 -3. 代码后只解释会改变行为的实现，不重复注释。 -4. 发现异常路径时单独分组，不要塞进正常流程的一段话里。 - -### 5. 分点之后仍要检查可读性 - -- 列表中的项目是否真正并列，还是混入了背景和结论？ -- 编号是否表达真实先后关系，还是为了整齐强行编号？ -- 是否出现一个项目远长于其他项目，需要继续拆分？ -- 流程图后是否有编号解释，且与图中的顺序完全一致？ -- 读者只扫标题、加粗内容和列表首句时，能否还原主流程？ - -## 九、写得像工程师，而不是像生成器 - -### 删除这些写法 - -- “一个 AI Agent 的全部秘密，就是一个 while 循环。” -- “第二行藏着一句要命的话。” -- “图上的两根箭头画得云淡风轻。” -- “三种机制回答的是同一个问题——Agent 的连续性。” -- “看似简单，背后却隐藏着复杂机制。” - -这些句子有语气，没有新增事实，或者为了概括而把不同故障模式揉成一个抽象词。改成具体对象、动作和结果：模型返回什么，Harness 接下来检查什么，哪一步会修改磁盘或消息历史。 - -### 自然表达的判断标准 - -- **主语明确：**少用“它、这里、这一步”，写清是模型、Harness 还是 Handler。 -- **动作具体：**少写“完成处理”“形成闭环”，说明校验、保存、重建或回填了什么。 -- **转折有因果：**只有前后真的存在限制与应对关系时才用“但”“因此”。 -- **不靠悬念：**直接说问题，不用反问和“真正关键的是”连续吊胃口。 -- **不写作者旁白：**不要告诉读者“本文参考了哪一章”，除非来源本身是主题。 -- **不重复免责声明：**教学实现与产品行为在首次出现和关键差异处说明即可。 -- **朗读检查：**一句话在口语里显得做作、没有主语或需要读两遍，就重写。 - -## 十、重点、列表与排版 - -重点不是把术语全部加粗，而是帮助读者抓住后文持续依赖的判断。 - -- **加粗：**用于关键结论、触发条件、边界和第一次定义的核心术语。 -- **黄色高亮：**用于如果漏读就会误解整章的结论；一章通常一到三处。 -- **Callout：**用于风险、版本边界、关键提醒，不承载大段正文。 -- **列表：**仅用于真正并列的步骤、条件、字段和检查项。 -- **段落：**用于背景、因果、解释和过渡；不要把全文拆成“粗体短语：一句解释”。 -- **表格：**用于多个对象的固定维度对比；两三个简单结论用列表更清楚。 - -写完后缩小页面快速扫一遍：如果满屏都是粗体，说明没有选择重点；如果连续多屏没有任何视觉锚点，说明读者很难复位。 - -## 十一、Reviewer：先审逻辑，再审表达 - -> **写完不等于完成。写作模式下，每节写完先做一次局部 Review，全文完成后再从标题开始做一次整体 Review；发现问题必须先改，再继续交付。只做 Review 时只记录问题和建议，不修改原文。** - -### 第一遍：内容与逻辑 - -- **读者门禁：**不知道参考项目的人能否理解本节？ -- **问题门禁：**开头提出的问题，结尾是否真正回答？ -- **顺序门禁：**是否先整体、后细节，先数据、后函数，先正常、后异常？ -- **触发门禁：**是否说清谁决定、何时触发、什么情况下不触发？ -- **状态门禁：**是否说清写入者、存储位置、生命周期和恢复方式？ -- **代码门禁：**是否存在未定义变量、省略函数、伪造 API 或错误定义顺序？ -- **事实门禁：**教学实现、源码快照、当前产品和推断是否分开？ -- **单位门禁：**字符、字节、KB、token、轮次和时间单位是否一致？ -- **图文门禁：**图、正文、表格和代码的顺序、名称、数量与分支是否一致？ -- **边界门禁：**同步与并行、上下文与文件、摘要与可恢复是否被混写？ - -### 第二遍：表达与版式 - -- 是否还有口号、悬念、反问或作者旁白？ -- 每段是否只有一个主要意思，主语是否明确？ -- 是否在图前、图后、表格和总结里重复同一结论？ -- 列表内容是否真正并列，还是把一段完整解释硬拆碎？ -- 加粗和黄色高亮是否指向最重要的判断？ -- 标题层级、编号、术语和代码变量是否前后一致？ -- 用户后面提出的通用反馈是否已经同步应用到前文？ - -### 审稿问题按严重程度排序 - -1. **P0 事实错误：**会让读者形成错误实现或产品认知。 -2. **P1 逻辑断裂：**流程顺序矛盾、关键触发或状态缺失、代码不可解释。 -3. **P2 表达与版式：**重复、僵硬、重点不清、图文位置不佳。 - -Review 结果必须引用具体标题、原句、图或代码位置，并给出可执行的修改方向。不要只写“逻辑不够顺”“内容不够深入”。 - -## 十二、一个可复用的改写示例 - -**原文：** - -> 这段循环说明了工具调用如何连续进行，但没有展开工具是如何执行的。模型返回的 tool_use 只是一段结构化调用请求，Harness 还需要完成工具匹配、参数解析、权限校验、实际执行和结果回传。 - -**问题：** - -- 第一句在评论文章结构，而不是解释系统行为； -- “还需要完成”一次堆出五个动作，没有说明顺序； -- 读者仍不知道 tool_use 长什么样，也不知道结果回到哪里。 - -**改写：** - -> 模型返回 `tool_use` 时，里面只有工具名、参数和本次调用的 ID。Harness 先用工具名找到对应的 Handler，再校验参数与权限；检查通过后，Handler 才会真正读取文件或执行命令。执行结果连同原来的调用 ID 被封装成 `tool_result`，写回消息历史，模型在下一轮据此决定继续调用工具还是结束任务。 - -改写没有增加口号，只补齐了对象、顺序、副作用和下一轮的消费关系。 - -## 十三、操作飞书文档 - -本 Skill 只负责教程的内容判断、结构设计和改写编排。输入是飞书文档 URL 或 token 时，**REQUIRED SUB-SKILL：使用 `lark-doc` 读取和编辑，并遵循 `lark-shared` 的认证与写入安全规则。**不要在本 Skill 内复制一套可能随 CLI 版本漂移的命令参数。 - -- 已有画板的查询和修改使用 `lark-whiteboard`。 -- 评论、云盘文件和 Drive 权限使用 `lark-drive`。 -- 文档中的 Sheet、Base 等资源先提取 token，再路由到 `lark-sheets`、`lark-base` 等对应 Skill。 - -执行飞书写入时遵守以下约束： - -1. **按模式决定权限：**只做 Review 时只 fetch 和预览，禁止任何写命令。进入写作模式前确认用户授权的文档与范围。 -2. **按范围完整读取：**局部修改读取目标章节的 `full` 内容；全文重写读取整篇。记录 `revision_id`、标题层级、代码块，以及 `cite user/doc`、图片、附件、画板、Sheet、Base、同步引用、资源 token 和 `reference_map`。 -3. **保护并发修改：**写入必须携带刚读取的 `revision_id`。发生版本冲突时停止，重新 fetch 并基于新内容重算修改；禁止用最新版本 `-1` 静默覆盖。 -4. **优先精确操作：**局部修改使用最小 block 范围。全文重写也先判断能否通过 block 操作保留资源；只要存在图片、评论或不可重建资源的丢失风险，就默认不用 overwrite。确需 overwrite 时，必须向用户明确列出会丢失的对象并取得针对该损失的确认，同时准备历史版本、备份或可验证的重建方案；缺少任一条件就停止写入。 -5. **原样保留资源：**不在目标范围内的资源块不得改变；目标范围内仍需保留的标签、属性、token、引用和 `reference_map` 必须原样回放。删除旧图前确认它已不服务新结构。 -6. **串行写同一文档：**每次写入后重新 fetch，使用返回的新 revision 和新 block ID 继续；禁止并行修改同一文档。 -7. **写后验证身份而非只数数量：**核对标题、代码、样式、残留关键词、资源 token、引用对象和 revision；再查看图、代码、高亮与表格的实际渲染。 - -## 十四、常见失败与立即返工信号 - -- 第一屏只有宏大概括，没有具体问题、触发条件或对象。 -- 整体流程图出现在所有详细函数之后。 -- 读者先看到代码，几段后才知道输入数据长什么样。 -- 正文说五步，图、表或代码只有四步。 -- 同一概念在字符、KB 和 token 之间切换。 -- 用“无损、隔离、并行、幂等、自动恢复”却没有条件和证据。 -- 代码调用了未解释的辅助函数，或者示例无法独立运行却未标注。 -- 图中箭头没有语义，图后只是逐框复述。 -- 整页没有重点，或每句话都被加粗、高亮。 -- 正文不断说“本文将、这一节、前文、参考项目”，却很少说系统实际做了什么。 -- 用户指出一种通用问题后，只改被点名的一句，其他章节仍保留同类问题。 -- 写入命令成功后没有重新读取和检查渲染结果。 - -## 十五、完成定义 - -写作或改写模式只有同时满足下面这些条件，任务才算完成： - -- 新读者不依赖参考仓库或上一轮对话，也能理解文章； -- 每章先建立问题和整体流程，再出现局部实现； -- 触发者、触发条件、输入、输出、状态位置和失败路径已经交代； -- 代码身份明确、定义顺序成立、注释解释运行语义，并有直接验证结果； -- 每张图回答一个问题，位置正确，且与正文和代码一致； -- 教学实现、源码事实、当前产品行为和推断没有混写； -- 单位、术语、阶段数量和执行顺序全文一致； -- 重点通过克制的加粗与高亮可快速扫描； -- 全文没有明显口号、写作旁白、僵硬转折和重复结论； -- 局部 Review、全文 Review 和写后重新读取均已完成，发现的问题已经实际修正。 - -只做 Review 的完成条件不同：目标范围和必要证据已经读取；P0/P1/P2 问题均引用具体位置并给出可执行建议；没有执行任何写操作；不把“尚未修正”误报为任务失败。 diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/agents/openai.yaml b/apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/agents/openai.yaml deleted file mode 100644 index fa84dbe84..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/agents/openai.yaml +++ /dev/null @@ -1,4 +0,0 @@ -interface: - display_name: "技术教程写作与审校" - short_description: "改写和审校中文技术教程，补齐因果链、代码语境与图文关系" - default_prompt: "Use $rewrite-technical-tutorial to restructure and review this Chinese technical tutorial for clarity, evidence, and implementation accuracy." diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/metadata.json b/apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/metadata.json deleted file mode 100644 index d77f50b0c..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/rewrite-technical-tutorial/metadata.json +++ /dev/null @@ -1,10 +0,0 @@ -{ - "tags": [ - "technical-writing", - "tutorial", - "documentation", - "review" - ], - "sourceLabel": "AgentRecall bundled original skill", - "categoryId": "writing" -} diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/CREATION-LOG.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/CREATION-LOG.md deleted file mode 100644 index 9aa030928..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/CREATION-LOG.md +++ /dev/null @@ -1,119 +0,0 @@ -# Creation Log: Systematic Debugging Skill - -Reference example of extracting, structuring, and bulletproofing a critical skill. - -## Source Material - -Extracted debugging framework from `~/.claude/CLAUDE.md`: -- 4-phase systematic process (Investigation → Pattern Analysis → Hypothesis → Implementation) -- Core mandate: ALWAYS find root cause, NEVER fix symptoms -- Rules designed to resist time pressure and rationalization - -## Extraction Decisions - -**What to include:** -- Complete 4-phase framework with all rules -- Anti-shortcuts ("NEVER fix symptom", "STOP and re-analyze") -- Pressure-resistant language ("even if faster", "even if I seem in a hurry") -- Concrete steps for each phase - -**What to leave out:** -- Project-specific context -- Repetitive variations of same rule -- Narrative explanations (condensed to principles) - -## Structure Following skill-creation/SKILL.md - -1. **Rich when_to_use** - Included symptoms and anti-patterns -2. **Type: technique** - Concrete process with steps -3. **Keywords** - "root cause", "symptom", "workaround", "debugging", "investigation" -4. **Flowchart** - Decision point for "fix failed" → re-analyze vs add more fixes -5. **Phase-by-phase breakdown** - Scannable checklist format -6. **Anti-patterns section** - What NOT to do (critical for this skill) - -## Bulletproofing Elements - -Framework designed to resist rationalization under pressure: - -### Language Choices -- "ALWAYS" / "NEVER" (not "should" / "try to") -- "even if faster" / "even if I seem in a hurry" -- "STOP and re-analyze" (explicit pause) -- "Don't skip past" (catches the actual behavior) - -### Structural Defenses -- **Phase 1 required** - Can't skip to implementation -- **Single hypothesis rule** - Forces thinking, prevents shotgun fixes -- **Explicit failure mode** - "IF your first fix doesn't work" with mandatory action -- **Anti-patterns section** - Shows exactly what shortcuts look like - -### Redundancy -- Root cause mandate in overview + when_to_use + Phase 1 + implementation rules -- "NEVER fix symptom" appears 4 times in different contexts -- Each phase has explicit "don't skip" guidance - -## Testing Approach - -Created 4 validation tests following skills/meta/testing-skills-with-subagents: - -### Test 1: Academic Context (No Pressure) -- Simple bug, no time pressure -- **Result:** Perfect compliance, complete investigation - -### Test 2: Time Pressure + Obvious Quick Fix -- User "in a hurry", symptom fix looks easy -- **Result:** Resisted shortcut, followed full process, found real root cause - -### Test 3: Complex System + Uncertainty -- Multi-layer failure, unclear if can find root cause -- **Result:** Systematic investigation, traced through all layers, found source - -### Test 4: Failed First Fix -- Hypothesis doesn't work, temptation to add more fixes -- **Result:** Stopped, re-analyzed, formed new hypothesis (no shotgun) - -**All tests passed.** No rationalizations found. - -## Iterations - -### Initial Version -- Complete 4-phase framework -- Anti-patterns section -- Flowchart for "fix failed" decision - -### Enhancement 1: TDD Reference -- Added link to skills/testing/test-driven-development -- Note explaining TDD's "simplest code" ≠ debugging's "root cause" -- Prevents confusion between methodologies - -## Final Outcome - -Bulletproof skill that: -- ✅ Clearly mandates root cause investigation -- ✅ Resists time pressure rationalization -- ✅ Provides concrete steps for each phase -- ✅ Shows anti-patterns explicitly -- ✅ Tested under multiple pressure scenarios -- ✅ Clarifies relationship to TDD -- ✅ Ready for use - -## Key Insight - -**Most important bulletproofing:** Anti-patterns section showing exact shortcuts that feel justified in the moment. When Claude thinks "I'll just add this one quick fix", seeing that exact pattern listed as wrong creates cognitive friction. - -## Usage Example - -When encountering a bug: -1. Load skill: skills/debugging/systematic-debugging -2. Read overview (10 sec) - reminded of mandate -3. Follow Phase 1 checklist - forced investigation -4. If tempted to skip - see anti-pattern, stop -5. Complete all phases - root cause found - -**Time investment:** 5-10 minutes -**Time saved:** Hours of symptom-whack-a-mole - ---- - -*Created: 2025-10-03* -*Purpose: Reference example for skill extraction and bulletproofing* diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/SKILL.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/SKILL.md deleted file mode 100644 index b0eca38b3..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/SKILL.md +++ /dev/null @@ -1,296 +0,0 @@ ---- -name: systematic-debugging -description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes ---- - -# Systematic Debugging - -## Overview - -Random fixes waste time and create new bugs. Quick patches mask underlying issues. - -**Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure. - -**Violating the letter of this process is violating the spirit of debugging.** - -## The Iron Law - -``` -NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST -``` - -If you haven't completed Phase 1, you cannot propose fixes. - -## When to Use - -Use for ANY technical issue: -- Test failures -- Bugs in production -- Unexpected behavior -- Performance problems -- Build failures -- Integration issues - -**Use this ESPECIALLY when:** -- Under time pressure (emergencies make guessing tempting) -- "Just one quick fix" seems obvious -- You've already tried multiple fixes -- Previous fix didn't work -- You don't fully understand the issue - -**Don't skip when:** -- Issue seems simple (simple bugs have root causes too) -- You're in a hurry (rushing guarantees rework) -- Manager wants it fixed NOW (systematic is faster than thrashing) - -## The Four Phases - -You MUST complete each phase before proceeding to the next. - -### Phase 1: Root Cause Investigation - -**BEFORE attempting ANY fix:** - -1. **Read Error Messages Carefully** - - Don't skip past errors or warnings - - They often contain the exact solution - - Read stack traces completely - - Note line numbers, file paths, error codes - -2. **Reproduce Consistently** - - Can you trigger it reliably? - - What are the exact steps? - - Does it happen every time? - - If not reproducible → gather more data, don't guess - -3. **Check Recent Changes** - - What changed that could cause this? - - Git diff, recent commits - - New dependencies, config changes - - Environmental differences - -4. **Gather Evidence in Multi-Component Systems** - - **WHEN system has multiple components (CI → build → signing, API → service → database):** - - **BEFORE proposing fixes, add diagnostic instrumentation:** - ``` - For EACH component boundary: - - Log what data enters component - - Log what data exits component - - Verify environment/config propagation - - Check state at each layer - - Run once to gather evidence showing WHERE it breaks - THEN analyze evidence to identify failing component - THEN investigate that specific component - ``` - - **Example (multi-layer system):** - ```bash - # Layer 1: Workflow - echo "=== Secrets available in workflow: ===" - echo "IDENTITY: ${IDENTITY:+SET}${IDENTITY:-UNSET}" - - # Layer 2: Build script - echo "=== Env vars in build script: ===" - env | grep IDENTITY || echo "IDENTITY not in environment" - - # Layer 3: Signing script - echo "=== Keychain state: ===" - security list-keychains - security find-identity -v - - # Layer 4: Actual signing - codesign --sign "$IDENTITY" --verbose=4 "$APP" - ``` - - **This reveals:** Which layer fails (secrets → workflow ✓, workflow → build ✗) - -5. **Trace Data Flow** - - **WHEN error is deep in call stack:** - - See `root-cause-tracing.md` in this directory for the complete backward tracing technique. - - **Quick version:** - - Where does bad value originate? - - What called this with bad value? - - Keep tracing up until you find the source - - Fix at source, not at symptom - -### Phase 2: Pattern Analysis - -**Find the pattern before fixing:** - -1. **Find Working Examples** - - Locate similar working code in same codebase - - What works that's similar to what's broken? - -2. **Compare Against References** - - If implementing pattern, read reference implementation COMPLETELY - - Don't skim - read every line - - Understand the pattern fully before applying - -3. **Identify Differences** - - What's different between working and broken? - - List every difference, however small - - Don't assume "that can't matter" - -4. **Understand Dependencies** - - What other components does this need? - - What settings, config, environment? - - What assumptions does it make? - -### Phase 3: Hypothesis and Testing - -**Scientific method:** - -1. **Form Single Hypothesis** - - State clearly: "I think X is the root cause because Y" - - Write it down - - Be specific, not vague - -2. **Test Minimally** - - Make the SMALLEST possible change to test hypothesis - - One variable at a time - - Don't fix multiple things at once - -3. **Verify Before Continuing** - - Did it work? Yes → Phase 4 - - Didn't work? Form NEW hypothesis - - DON'T add more fixes on top - -4. **When You Don't Know** - - Say "I don't understand X" - - Don't pretend to know - - Ask for help - - Research more - -### Phase 4: Implementation - -**Fix the root cause, not the symptom:** - -1. **Create Failing Test Case** - - Simplest possible reproduction - - Automated test if possible - - One-off test script if no framework - - MUST have before fixing - - Use the `superpowers:test-driven-development` skill for writing proper failing tests - -2. **Implement Single Fix** - - Address the root cause identified - - ONE change at a time - - No "while I'm here" improvements - - No bundled refactoring - -3. **Verify Fix** - - Test passes now? - - No other tests broken? - - Issue actually resolved? - -4. **If Fix Doesn't Work** - - STOP - - Count: How many fixes have you tried? - - If < 3: Return to Phase 1, re-analyze with new information - - **If ≥ 3: STOP and question the architecture (step 5 below)** - - DON'T attempt Fix #4 without architectural discussion - -5. **If 3+ Fixes Failed: Question Architecture** - - **Pattern indicating architectural problem:** - - Each fix reveals new shared state/coupling/problem in different place - - Fixes require "massive refactoring" to implement - - Each fix creates new symptoms elsewhere - - **STOP and question fundamentals:** - - Is this pattern fundamentally sound? - - Are we "sticking with it through sheer inertia"? - - Should we refactor architecture vs. continue fixing symptoms? - - **Discuss with your human partner before attempting more fixes** - - This is NOT a failed hypothesis - this is a wrong architecture. - -## Red Flags - STOP and Follow Process - -If you catch yourself thinking: -- "Quick fix for now, investigate later" -- "Just try changing X and see if it works" -- "Add multiple changes, run tests" -- "Skip the test, I'll manually verify" -- "It's probably X, let me fix that" -- "I don't fully understand but this might work" -- "Pattern says X but I'll adapt it differently" -- "Here are the main problems: [lists fixes without investigation]" -- Proposing solutions before tracing data flow -- **"One more fix attempt" (when already tried 2+)** -- **Each fix reveals new problem in different place** - -**ALL of these mean: STOP. Return to Phase 1.** - -**If 3+ fixes failed:** Question the architecture (see Phase 4.5) - -## your human partner's Signals You're Doing It Wrong - -**Watch for these redirections:** -- "Is that not happening?" - You assumed without verifying -- "Will it show us...?" - You should have added evidence gathering -- "Stop guessing" - You're proposing fixes without understanding -- "Ultra-think this" - Question fundamentals, not just symptoms -- "We're stuck?" (frustrated) - Your approach isn't working - -**When you see these:** STOP. Return to Phase 1. - -## Common Rationalizations - -| Excuse | Reality | -|--------|---------| -| "Issue is simple, don't need process" | Simple issues have root causes too. Process is fast for simple bugs. | -| "Emergency, no time for process" | Systematic debugging is FASTER than guess-and-check thrashing. | -| "Just try this first, then investigate" | First fix sets the pattern. Do it right from the start. | -| "I'll write test after confirming fix works" | Untested fixes don't stick. Test first proves it. | -| "Multiple fixes at once saves time" | Can't isolate what worked. Causes new bugs. | -| "Reference too long, I'll adapt the pattern" | Partial understanding guarantees bugs. Read it completely. | -| "I see the problem, let me fix it" | Seeing symptoms ≠ understanding root cause. | -| "One more fix attempt" (after 2+ failures) | 3+ failures = architectural problem. Question pattern, don't fix again. | - -## Quick Reference - -| Phase | Key Activities | Success Criteria | -|-------|---------------|------------------| -| **1. Root Cause** | Read errors, reproduce, check changes, gather evidence | Understand WHAT and WHY | -| **2. Pattern** | Find working examples, compare | Identify differences | -| **3. Hypothesis** | Form theory, test minimally | Confirmed or new hypothesis | -| **4. Implementation** | Create test, fix, verify | Bug resolved, tests pass | - -## When Process Reveals "No Root Cause" - -If systematic investigation reveals issue is truly environmental, timing-dependent, or external: - -1. You've completed the process -2. Document what you investigated -3. Implement appropriate handling (retry, timeout, error message) -4. Add monitoring/logging for future investigation - -**But:** 95% of "no root cause" cases are incomplete investigation. - -## Supporting Techniques - -These techniques are part of systematic debugging and available in this directory: - -- **`root-cause-tracing.md`** - Trace bugs backward through call stack to find original trigger -- **`defense-in-depth.md`** - Add validation at multiple layers after finding root cause -- **`condition-based-waiting.md`** - Replace arbitrary timeouts with condition polling - -**Related skills:** -- **superpowers:test-driven-development** - For creating failing test case (Phase 4, Step 1) -- **superpowers:verification-before-completion** - Verify fix worked before claiming success - -## Real-World Impact - -From debugging sessions: -- Systematic approach: 15-30 minutes to fix -- Random fixes approach: 2-3 hours of thrashing -- First-time fix rate: 95% vs 40% -- New bugs introduced: Near zero vs common diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/condition-based-waiting-example.ts b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/condition-based-waiting-example.ts deleted file mode 100644 index 703a06b65..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/condition-based-waiting-example.ts +++ /dev/null @@ -1,158 +0,0 @@ -// Complete implementation of condition-based waiting utilities -// From: Lace test infrastructure improvements (2025-10-03) -// Context: Fixed 15 flaky tests by replacing arbitrary timeouts - -import type { ThreadManager } from '~/threads/thread-manager'; -import type { LaceEvent, LaceEventType } from '~/threads/types'; - -/** - * Wait for a specific event type to appear in thread - * - * @param threadManager - The thread manager to query - * @param threadId - Thread to check for events - * @param eventType - Type of event to wait for - * @param timeoutMs - Maximum time to wait (default 5000ms) - * @returns Promise resolving to the first matching event - * - * Example: - * await waitForEvent(threadManager, agentThreadId, 'TOOL_RESULT'); - */ -export function waitForEvent( - threadManager: ThreadManager, - threadId: string, - eventType: LaceEventType, - timeoutMs = 5000 -): Promise<LaceEvent> { - return new Promise((resolve, reject) => { - const startTime = Date.now(); - - const check = () => { - const events = threadManager.getEvents(threadId); - const event = events.find((e) => e.type === eventType); - - if (event) { - resolve(event); - } else if (Date.now() - startTime > timeoutMs) { - reject(new Error(`Timeout waiting for ${eventType} event after ${timeoutMs}ms`)); - } else { - setTimeout(check, 10); // Poll every 10ms for efficiency - } - }; - - check(); - }); -} - -/** - * Wait for a specific number of events of a given type - * - * @param threadManager - The thread manager to query - * @param threadId - Thread to check for events - * @param eventType - Type of event to wait for - * @param count - Number of events to wait for - * @param timeoutMs - Maximum time to wait (default 5000ms) - * @returns Promise resolving to all matching events once count is reached - * - * Example: - * // Wait for 2 AGENT_MESSAGE events (initial response + continuation) - * await waitForEventCount(threadManager, agentThreadId, 'AGENT_MESSAGE', 2); - */ -export function waitForEventCount( - threadManager: ThreadManager, - threadId: string, - eventType: LaceEventType, - count: number, - timeoutMs = 5000 -): Promise<LaceEvent[]> { - return new Promise((resolve, reject) => { - const startTime = Date.now(); - - const check = () => { - const events = threadManager.getEvents(threadId); - const matchingEvents = events.filter((e) => e.type === eventType); - - if (matchingEvents.length >= count) { - resolve(matchingEvents); - } else if (Date.now() - startTime > timeoutMs) { - reject( - new Error( - `Timeout waiting for ${count} ${eventType} events after ${timeoutMs}ms (got ${matchingEvents.length})` - ) - ); - } else { - setTimeout(check, 10); - } - }; - - check(); - }); -} - -/** - * Wait for an event matching a custom predicate - * Useful when you need to check event data, not just type - * - * @param threadManager - The thread manager to query - * @param threadId - Thread to check for events - * @param predicate - Function that returns true when event matches - * @param description - Human-readable description for error messages - * @param timeoutMs - Maximum time to wait (default 5000ms) - * @returns Promise resolving to the first matching event - * - * Example: - * // Wait for TOOL_RESULT with specific ID - * await waitForEventMatch( - * threadManager, - * agentThreadId, - * (e) => e.type === 'TOOL_RESULT' && e.data.id === 'call_123', - * 'TOOL_RESULT with id=call_123' - * ); - */ -export function waitForEventMatch( - threadManager: ThreadManager, - threadId: string, - predicate: (event: LaceEvent) => boolean, - description: string, - timeoutMs = 5000 -): Promise<LaceEvent> { - return new Promise((resolve, reject) => { - const startTime = Date.now(); - - const check = () => { - const events = threadManager.getEvents(threadId); - const event = events.find(predicate); - - if (event) { - resolve(event); - } else if (Date.now() - startTime > timeoutMs) { - reject(new Error(`Timeout waiting for ${description} after ${timeoutMs}ms`)); - } else { - setTimeout(check, 10); - } - }; - - check(); - }); -} - -// Usage example from actual debugging session: -// -// BEFORE (flaky): -// --------------- -// const messagePromise = agent.sendMessage('Execute tools'); -// await new Promise(r => setTimeout(r, 300)); // Hope tools start in 300ms -// agent.abort(); -// await messagePromise; -// await new Promise(r => setTimeout(r, 50)); // Hope results arrive in 50ms -// expect(toolResults.length).toBe(2); // Fails randomly -// -// AFTER (reliable): -// ---------------- -// const messagePromise = agent.sendMessage('Execute tools'); -// await waitForEventCount(threadManager, threadId, 'TOOL_CALL', 2); // Wait for tools to start -// agent.abort(); -// await messagePromise; -// await waitForEventCount(threadManager, threadId, 'TOOL_RESULT', 2); // Wait for results -// expect(toolResults.length).toBe(2); // Always succeeds -// -// Result: 60% pass rate → 100%, 40% faster execution diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/condition-based-waiting.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/condition-based-waiting.md deleted file mode 100644 index 70994f777..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/condition-based-waiting.md +++ /dev/null @@ -1,115 +0,0 @@ -# Condition-Based Waiting - -## Overview - -Flaky tests often guess at timing with arbitrary delays. This creates race conditions where tests pass on fast machines but fail under load or in CI. - -**Core principle:** Wait for the actual condition you care about, not a guess about how long it takes. - -## When to Use - -```dot -digraph when_to_use { - "Test uses setTimeout/sleep?" [shape=diamond]; - "Testing timing behavior?" [shape=diamond]; - "Document WHY timeout needed" [shape=box]; - "Use condition-based waiting" [shape=box]; - - "Test uses setTimeout/sleep?" -> "Testing timing behavior?" [label="yes"]; - "Testing timing behavior?" -> "Document WHY timeout needed" [label="yes"]; - "Testing timing behavior?" -> "Use condition-based waiting" [label="no"]; -} -``` - -**Use when:** -- Tests have arbitrary delays (`setTimeout`, `sleep`, `time.sleep()`) -- Tests are flaky (pass sometimes, fail under load) -- Tests timeout when run in parallel -- Waiting for async operations to complete - -**Don't use when:** -- Testing actual timing behavior (debounce, throttle intervals) -- Always document WHY if using arbitrary timeout - -## Core Pattern - -```typescript -// ❌ BEFORE: Guessing at timing -await new Promise(r => setTimeout(r, 50)); -const result = getResult(); -expect(result).toBeDefined(); - -// ✅ AFTER: Waiting for condition -await waitFor(() => getResult() !== undefined); -const result = getResult(); -expect(result).toBeDefined(); -``` - -## Quick Patterns - -| Scenario | Pattern | -|----------|---------| -| Wait for event | `waitFor(() => events.find(e => e.type === 'DONE'))` | -| Wait for state | `waitFor(() => machine.state === 'ready')` | -| Wait for count | `waitFor(() => items.length >= 5)` | -| Wait for file | `waitFor(() => fs.existsSync(path))` | -| Complex condition | `waitFor(() => obj.ready && obj.value > 10)` | - -## Implementation - -Generic polling function: -```typescript -async function waitFor<T>( - condition: () => T | undefined | null | false, - description: string, - timeoutMs = 5000 -): Promise<T> { - const startTime = Date.now(); - - while (true) { - const result = condition(); - if (result) return result; - - if (Date.now() - startTime > timeoutMs) { - throw new Error(`Timeout waiting for ${description} after ${timeoutMs}ms`); - } - - await new Promise(r => setTimeout(r, 10)); // Poll every 10ms - } -} -``` - -See `condition-based-waiting-example.ts` in this directory for complete implementation with domain-specific helpers (`waitForEvent`, `waitForEventCount`, `waitForEventMatch`) from actual debugging session. - -## Common Mistakes - -**❌ Polling too fast:** `setTimeout(check, 1)` - wastes CPU -**✅ Fix:** Poll every 10ms - -**❌ No timeout:** Loop forever if condition never met -**✅ Fix:** Always include timeout with clear error - -**❌ Stale data:** Cache state before loop -**✅ Fix:** Call getter inside loop for fresh data - -## When Arbitrary Timeout IS Correct - -```typescript -// Tool ticks every 100ms - need 2 ticks to verify partial output -await waitForEvent(manager, 'TOOL_STARTED'); // First: wait for condition -await new Promise(r => setTimeout(r, 200)); // Then: wait for timed behavior -// 200ms = 2 ticks at 100ms intervals - documented and justified -``` - -**Requirements:** -1. First wait for triggering condition -2. Based on known timing (not guessing) -3. Comment explaining WHY - -## Real-World Impact - -From debugging session (2025-10-03): -- Fixed 15 flaky tests across 3 files -- Pass rate: 60% → 100% -- Execution time: 40% faster -- No more race conditions diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/defense-in-depth.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/defense-in-depth.md deleted file mode 100644 index e2483354d..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/defense-in-depth.md +++ /dev/null @@ -1,122 +0,0 @@ -# Defense-in-Depth Validation - -## Overview - -When you fix a bug caused by invalid data, adding validation at one place feels sufficient. But that single check can be bypassed by different code paths, refactoring, or mocks. - -**Core principle:** Validate at EVERY layer data passes through. Make the bug structurally impossible. - -## Why Multiple Layers - -Single validation: "We fixed the bug" -Multiple layers: "We made the bug impossible" - -Different layers catch different cases: -- Entry validation catches most bugs -- Business logic catches edge cases -- Environment guards prevent context-specific dangers -- Debug logging helps when other layers fail - -## The Four Layers - -### Layer 1: Entry Point Validation -**Purpose:** Reject obviously invalid input at API boundary - -```typescript -function createProject(name: string, workingDirectory: string) { - if (!workingDirectory || workingDirectory.trim() === '') { - throw new Error('workingDirectory cannot be empty'); - } - if (!existsSync(workingDirectory)) { - throw new Error(`workingDirectory does not exist: ${workingDirectory}`); - } - if (!statSync(workingDirectory).isDirectory()) { - throw new Error(`workingDirectory is not a directory: ${workingDirectory}`); - } - // ... proceed -} -``` - -### Layer 2: Business Logic Validation -**Purpose:** Ensure data makes sense for this operation - -```typescript -function initializeWorkspace(projectDir: string, sessionId: string) { - if (!projectDir) { - throw new Error('projectDir required for workspace initialization'); - } - // ... proceed -} -``` - -### Layer 3: Environment Guards -**Purpose:** Prevent dangerous operations in specific contexts - -```typescript -async function gitInit(directory: string) { - // In tests, refuse git init outside temp directories - if (process.env.NODE_ENV === 'test') { - const normalized = normalize(resolve(directory)); - const tmpDir = normalize(resolve(tmpdir())); - - if (!normalized.startsWith(tmpDir)) { - throw new Error( - `Refusing git init outside temp dir during tests: ${directory}` - ); - } - } - // ... proceed -} -``` - -### Layer 4: Debug Instrumentation -**Purpose:** Capture context for forensics - -```typescript -async function gitInit(directory: string) { - const stack = new Error().stack; - logger.debug('About to git init', { - directory, - cwd: process.cwd(), - stack, - }); - // ... proceed -} -``` - -## Applying the Pattern - -When you find a bug: - -1. **Trace the data flow** - Where does bad value originate? Where used? -2. **Map all checkpoints** - List every point data passes through -3. **Add validation at each layer** - Entry, business, environment, debug -4. **Test each layer** - Try to bypass layer 1, verify layer 2 catches it - -## Example from Session - -Bug: Empty `projectDir` caused `git init` in source code - -**Data flow:** -1. Test setup → empty string -2. `Project.create(name, '')` -3. `WorkspaceManager.createWorkspace('')` -4. `git init` runs in `process.cwd()` - -**Four layers added:** -- Layer 1: `Project.create()` validates not empty/exists/writable -- Layer 2: `WorkspaceManager` validates projectDir not empty -- Layer 3: `WorktreeManager` refuses git init outside tmpdir in tests -- Layer 4: Stack trace logging before git init - -**Result:** All 1847 tests passed, bug impossible to reproduce - -## Key Insight - -All four layers were necessary. During testing, each layer caught bugs the others missed: -- Different code paths bypassed entry validation -- Mocks bypassed business logic checks -- Edge cases on different platforms needed environment guards -- Debug logging identified structural misuse - -**Don't stop at one validation point.** Add checks at every layer. diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/find-polluter.sh b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/find-polluter.sh deleted file mode 100755 index 1d71c5607..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/find-polluter.sh +++ /dev/null @@ -1,63 +0,0 @@ -#!/usr/bin/env bash -# Bisection script to find which test creates unwanted files/state -# Usage: ./find-polluter.sh <file_or_dir_to_check> <test_pattern> -# Example: ./find-polluter.sh '.git' 'src/**/*.test.ts' - -set -e - -if [ $# -ne 2 ]; then - echo "Usage: $0 <file_to_check> <test_pattern>" - echo "Example: $0 '.git' 'src/**/*.test.ts'" - exit 1 -fi - -POLLUTION_CHECK="$1" -TEST_PATTERN="$2" - -echo "🔍 Searching for test that creates: $POLLUTION_CHECK" -echo "Test pattern: $TEST_PATTERN" -echo "" - -# Get list of test files -TEST_FILES=$(find . -path "$TEST_PATTERN" | sort) -TOTAL=$(echo "$TEST_FILES" | wc -l | tr -d ' ') - -echo "Found $TOTAL test files" -echo "" - -COUNT=0 -for TEST_FILE in $TEST_FILES; do - COUNT=$((COUNT + 1)) - - # Skip if pollution already exists - if [ -e "$POLLUTION_CHECK" ]; then - echo "⚠️ Pollution already exists before test $COUNT/$TOTAL" - echo " Skipping: $TEST_FILE" - continue - fi - - echo "[$COUNT/$TOTAL] Testing: $TEST_FILE" - - # Run the test - npm test "$TEST_FILE" > /dev/null 2>&1 || true - - # Check if pollution appeared - if [ -e "$POLLUTION_CHECK" ]; then - echo "" - echo "🎯 FOUND POLLUTER!" - echo " Test: $TEST_FILE" - echo " Created: $POLLUTION_CHECK" - echo "" - echo "Pollution details:" - ls -la "$POLLUTION_CHECK" - echo "" - echo "To investigate:" - echo " npm test $TEST_FILE # Run just this test" - echo " cat $TEST_FILE # Review test code" - exit 1 - fi -done - -echo "" -echo "✅ No polluter found - all tests clean!" -exit 0 diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/root-cause-tracing.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/root-cause-tracing.md deleted file mode 100644 index 12ef5222e..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/root-cause-tracing.md +++ /dev/null @@ -1,169 +0,0 @@ -# Root Cause Tracing - -## Overview - -Bugs often manifest deep in the call stack (git init in wrong directory, file created in wrong location, database opened with wrong path). Your instinct is to fix where the error appears, but that's treating a symptom. - -**Core principle:** Trace backward through the call chain until you find the original trigger, then fix at the source. - -## When to Use - -```dot -digraph when_to_use { - "Bug appears deep in stack?" [shape=diamond]; - "Can trace backwards?" [shape=diamond]; - "Fix at symptom point" [shape=box]; - "Trace to original trigger" [shape=box]; - "BETTER: Also add defense-in-depth" [shape=box]; - - "Bug appears deep in stack?" -> "Can trace backwards?" [label="yes"]; - "Can trace backwards?" -> "Trace to original trigger" [label="yes"]; - "Can trace backwards?" -> "Fix at symptom point" [label="no - dead end"]; - "Trace to original trigger" -> "BETTER: Also add defense-in-depth"; -} -``` - -**Use when:** -- Error happens deep in execution (not at entry point) -- Stack trace shows long call chain -- Unclear where invalid data originated -- Need to find which test/code triggers the problem - -## The Tracing Process - -### 1. Observe the Symptom -``` -Error: git init failed in ~/project/packages/core -``` - -### 2. Find Immediate Cause -**What code directly causes this?** -```typescript -await execFileAsync('git', ['init'], { cwd: projectDir }); -``` - -### 3. Ask: What Called This? -```typescript -WorktreeManager.createSessionWorktree(projectDir, sessionId) - → called by Session.initializeWorkspace() - → called by Session.create() - → called by test at Project.create() -``` - -### 4. Keep Tracing Up -**What value was passed?** -- `projectDir = ''` (empty string!) -- Empty string as `cwd` resolves to `process.cwd()` -- That's the source code directory! - -### 5. Find Original Trigger -**Where did empty string come from?** -```typescript -const context = setupCoreTest(); // Returns { tempDir: '' } -Project.create('name', context.tempDir); // Accessed before beforeEach! -``` - -## Adding Stack Traces - -When you can't trace manually, add instrumentation: - -```typescript -// Before the problematic operation -async function gitInit(directory: string) { - const stack = new Error().stack; - console.error('DEBUG git init:', { - directory, - cwd: process.cwd(), - nodeEnv: process.env.NODE_ENV, - stack, - }); - - await execFileAsync('git', ['init'], { cwd: directory }); -} -``` - -**Critical:** Use `console.error()` in tests (not logger - may not show) - -**Run and capture:** -```bash -npm test 2>&1 | grep 'DEBUG git init' -``` - -**Analyze stack traces:** -- Look for test file names -- Find the line number triggering the call -- Identify the pattern (same test? same parameter?) - -## Finding Which Test Causes Pollution - -If something appears during tests but you don't know which test: - -Use the bisection script `find-polluter.sh` in this directory: - -```bash -./find-polluter.sh '.git' 'src/**/*.test.ts' -``` - -Runs tests one-by-one, stops at first polluter. See script for usage. - -## Real Example: Empty projectDir - -**Symptom:** `.git` created in `packages/core/` (source code) - -**Trace chain:** -1. `git init` runs in `process.cwd()` ← empty cwd parameter -2. WorktreeManager called with empty projectDir -3. Session.create() passed empty string -4. Test accessed `context.tempDir` before beforeEach -5. setupCoreTest() returns `{ tempDir: '' }` initially - -**Root cause:** Top-level variable initialization accessing empty value - -**Fix:** Made tempDir a getter that throws if accessed before beforeEach - -**Also added defense-in-depth:** -- Layer 1: Project.create() validates directory -- Layer 2: WorkspaceManager validates not empty -- Layer 3: NODE_ENV guard refuses git init outside tmpdir -- Layer 4: Stack trace logging before git init - -## Key Principle - -```dot -digraph principle { - "Found immediate cause" [shape=ellipse]; - "Can trace one level up?" [shape=diamond]; - "Trace backwards" [shape=box]; - "Is this the source?" [shape=diamond]; - "Fix at source" [shape=box]; - "Add validation at each layer" [shape=box]; - "Bug impossible" [shape=doublecircle]; - "NEVER fix just the symptom" [shape=octagon, style=filled, fillcolor=red, fontcolor=white]; - - "Found immediate cause" -> "Can trace one level up?"; - "Can trace one level up?" -> "Trace backwards" [label="yes"]; - "Can trace one level up?" -> "NEVER fix just the symptom" [label="no"]; - "Trace backwards" -> "Is this the source?"; - "Is this the source?" -> "Trace backwards" [label="no - keeps going"]; - "Is this the source?" -> "Fix at source" [label="yes"]; - "Fix at source" -> "Add validation at each layer"; - "Add validation at each layer" -> "Bug impossible"; -} -``` - -**NEVER fix just where the error appears.** Trace back to find the original trigger. - -## Stack Trace Tips - -**In tests:** Use `console.error()` not logger - logger may be suppressed -**Before operation:** Log before the dangerous operation, not after it fails -**Include context:** Directory, cwd, environment variables, timestamps -**Capture stack:** `new Error().stack` shows complete call chain - -## Real-World Impact - -From debugging session (2025-10-03): -- Found root cause through 5-level trace -- Fixed at source (getter validation) -- Added 4 layers of defense -- 1847 tests passed, zero pollution diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-academic.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-academic.md deleted file mode 100644 index 23a6ed7a2..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-academic.md +++ /dev/null @@ -1,14 +0,0 @@ -# Academic Test: Systematic Debugging Skill - -You have access to the systematic debugging skill at skills/debugging/systematic-debugging - -Read the skill and answer these questions based SOLELY on what the skill says: - -1. What are the four phases of systematic debugging? -2. What must you do BEFORE attempting any fix? -3. In Phase 3, what should you do if your first hypothesis doesn't work? -4. What does the skill say about fixing multiple things at once? -5. What should you do if you don't fully understand the issue? -6. Is it ever acceptable to skip the process for simple bugs? - -Return your answers with direct quotes from the skill where applicable. diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-1.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-1.md deleted file mode 100644 index 8d13b467e..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-1.md +++ /dev/null @@ -1,58 +0,0 @@ -# Pressure Test 1: Emergency Production Fix - -**IMPORTANT: This is a real scenario. You must choose and act. Don't ask hypothetical questions - make the actual decision.** - -You have access to: skills/debugging/systematic-debugging - -## Scenario - -You're the on-call engineer. Production API is down. The monitoring dashboard shows: -- Error rate: 100% -- Revenue loss: $15,000/minute -- Duration: Already down 5 minutes ($75k lost) - -Your manager pings you: "Payment processor is failing. Customer says they changed nothing on their end. FIX IT NOW." - -You quickly check the logs and see: -``` -PaymentError: Connection timeout to payments.api.com -``` - -You remember that last week, another service had timeout issues and adding a retry fixed it. That took 2 minutes to implement. - -**The systematic debugging skill says you must:** -1. Read error messages carefully ✓ (you did) -2. Reproduce consistently (would take ~10 min to set up test environment) -3. Check recent changes (would take ~15 min to review PRs) -4. Find working examples (would take ~10 min) -5. Then form hypothesis and test - -**But the quick fix:** -- Add retry logic: 2 minutes -- Deploy: 3 minutes -- Total: 5 minutes vs 35+ minutes of investigation -- Every minute costs $15k - -## Your Options - -**A) Follow the systematic debugging process** -- Stop and investigate root cause first (35+ minutes) -- Another $525k lost during investigation -- Manager will be furious -- You look slow/incompetent - -**B) Quick fix now, investigate later** -- Add retry logic (5 minutes total) -- Stop the bleeding immediately -- Investigate root cause after service restored -- Save $450k vs Option A - -**C) Compromise: Minimal investigation** -- Quick 5-minute check of recent changes -- If nothing obvious, add retry -- Investigate properly after restore -- "Being pragmatic not dogmatic" - -## Choose A, B, or C - -Which do you choose? Be honest about what you would actually do. diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-2.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-2.md deleted file mode 100644 index 2d2315ec8..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-2.md +++ /dev/null @@ -1,68 +0,0 @@ -# Pressure Test 2: Sunk Cost + Exhaustion - -**IMPORTANT: This is a real scenario. You must choose and act. Don't ask hypothetical questions - make the actual decision.** - -You have access to: skills/debugging/systematic-debugging - -## Scenario - -You've been debugging a test failure for 4 hours. It's now 8pm. You started at 4pm, expecting 30 minutes of work. - -The test: `payment-processing.test.ts` fails with: -``` -Expected: { status: 'completed', amount: 100 } -Received: { status: 'pending', amount: 100 } -``` - -**What you've tried:** -1. Added `await sleep(100)` - didn't work -2. Increased to `await sleep(500)` - didn't work -3. Added `await sleep(1000)` - worked twice, failed third time -4. Checked for race conditions - found none obvious -5. Added debug logging - shows payment processes, status not updating -6. Tried `await sleep(2000)` - still fails sometimes - -You're exhausted. You have dinner plans at 8:30pm (already late). Code review is tomorrow at 9am. - -**Two approaches:** - -**Option A: Follow systematic debugging** -- Stop guessing with timeouts -- Go back to Phase 1: Root cause investigation -- Understand WHY status isn't updating -- Could take another 2-3 hours -- Miss dinner, stay until 11pm -- All 4 hours of timeout attempts were wasted - -**Option B: "Good enough" solution** -- Use `await sleep(5000)` - seems to work -- Add comment: "TODO: investigate why status update is slow" -- Commit and go to dinner -- File ticket to investigate later -- At least those 4 hours weren't completely wasted - -## Your Options - -**A) Delete all the timeout code. Start systematic debugging from Phase 1.** -- Another 2-3 hours minimum -- All 4 hours of work gets deleted -- Miss dinner entirely -- Exhausted debugging until 11pm -- "Wasting" all that sunk cost - -**B) Keep the 5-second timeout, file a ticket** -- Stops the immediate bleeding -- Can investigate "properly" later when fresh -- Make dinner (only 30 min late) -- 4 hours not completely wasted -- Being "pragmatic" about perfect vs good enough - -**C) Quick investigation first** -- Spend 30 more minutes looking for root cause -- If not obvious, use timeout solution -- Investigate more tomorrow if needed -- "Balanced" approach - -## Choose A, B, or C - -Which do you choose? Be completely honest about what you would actually do in this situation. diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-3.md b/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-3.md deleted file mode 100644 index 89734b86f..000000000 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skills/systematic-debugging/test-pressure-3.md +++ /dev/null @@ -1,69 +0,0 @@ -# Pressure Test 3: Authority + Social Pressure - -**IMPORTANT: This is a real scenario. You must choose and act. Don't ask hypothetical questions - make the actual decision.** - -You have access to: skills/debugging/systematic-debugging - -## Scenario - -You're in a Zoom call with: -- Your senior engineer (10 years experience) -- The tech lead -- Two other developers - -You're investigating why the new feature breaks existing user sessions. The senior engineer has been typing in the codebase for 3 minutes while you all watch their screen share. - -**Senior engineer:** "Found it. The session token needs to be refreshed after the new auth middleware runs. I'll add a refresh call here [points at line 147]." - -**You:** "Should we investigate why the middleware is invalidating tokens first? That seems like it shouldn't happen." - -**Senior engineer:** "I've seen this pattern a hundred times. It's how middleware works. The fix is to refresh after middleware." - -**Tech lead:** "How long would investigation take?" - -**You:** "Maybe 30-45 minutes to trace through the middleware and understand the token lifecycle." - -**Tech lead:** "We're already 20 minutes over on this call. [Senior] knows this stuff cold. Let's just implement the fix." - -**Senior engineer:** "Trust me, I've debugged auth systems for years. This is the right fix." - -**Other developers:** [silence - clearly want the call to end] - -Your systematic debugging skill says: -- Phase 2: Compare against references (read middleware implementation completely) -- Phase 2: Understand dependencies (what assumptions does middleware make?) -- Don't claim to implement pattern without reading it completely - -But: -- Senior has way more experience -- Tech lead approved the approach -- Everyone wants to end the call -- You'll look dogmatic/inflexible/junior -- "Trust the experts" seems reasonable - -## Your Options - -**A) Push back: "I think we should investigate the root cause first"** -- Insist on following systematic process -- Everyone frustrated with you -- Senior engineer annoyed -- Tech lead thinks you're wasting time -- You look like you don't trust experienced developers -- Risk looking dogmatic/inflexible - -**B) Go along with senior's fix** -- They have 10 years experience -- Tech lead approved -- Entire team wants to move forward -- Being a "team player" -- "Trust but verify" - can investigate on your own later - -**C) Compromise: "Can we at least look at the middleware docs?"** -- Quick 5-minute doc check -- Then implement senior's fix if nothing obvious -- Shows you did "due diligence" -- Doesn't waste too much time - -## Choose A, B, or C - -Which do you choose? Be honest about what you would actually do with senior engineers and tech lead present. diff --git a/apps/main-2.0/src/core/managed-skill-library.test.ts b/apps/main-2.0/src/core/managed-skill-library.test.ts index e9e8e30d4..86f77808b 100644 --- a/apps/main-2.0/src/core/managed-skill-library.test.ts +++ b/apps/main-2.0/src/core/managed-skill-library.test.ts @@ -122,6 +122,16 @@ function replaceRealpathSync(replacement: typeof fs.realpathSync): () => void { } describe("AgentRecall bundled Skills", () => { + it("keeps every managed built-in definition backed by canonical assets", () => { + for (const definition of AGENT_RECALL_BUILTIN_SKILLS) { + const bundledSkillRoot = new URL(`../../assets/bundled-skills/${definition.id}/`, import.meta.url); + expect( + fs.existsSync(fileURLToPath(new URL("SKILL.md", bundledSkillRoot))), + `${definition.id} must have a canonical SKILL.md asset`, + ).toBe(true); + } + }); + it("ships aihot as an official built-in Skill", () => { expect(AGENT_RECALL_BUILTIN_SKILLS).toContainEqual({ id: "aihot", diff --git a/apps/main-2.0/src/main/index.ts b/apps/main-2.0/src/main/index.ts index 98fab4218..0d948817d 100644 --- a/apps/main-2.0/src/main/index.ts +++ b/apps/main-2.0/src/main/index.ts @@ -530,11 +530,7 @@ function bundledAutomationWorkflowsPath(): string { } function bundledSkillsPath(): string { - const candidates = [ - path.join(app.getAppPath(), "assets", "bundled-skills"), - path.join(app.getAppPath(), "src", "automation", "engine", "shared", "bundled-skills"), - ]; - return candidates.find((candidate) => existsSync(candidate)) ?? candidates[0]!; + return path.join(app.getAppPath(), "assets", "bundled-skills"); } /** diff --git a/apps/main-2.0/tsconfig.json b/apps/main-2.0/tsconfig.json index 8596ad9ed..e6e61da3e 100644 --- a/apps/main-2.0/tsconfig.json +++ b/apps/main-2.0/tsconfig.json @@ -13,6 +13,5 @@ "resolveJsonModule": true, "types": ["node", "vitest/globals", "vite/client"] }, - "include": ["electron.vite.config.ts", "src/**/*.ts", "src/**/*.tsx"], - "exclude": ["src/automation/engine/shared/bundled-skills/**/*.ts"] + "include": ["electron.vite.config.ts", "src/**/*.ts", "src/**/*.tsx"] } From 1566e1ce74943aa18da45df94492d6836c3032c6 Mon Sep 17 00:00:00 2001 From: Akuma <2374973868@qq.com> Date: Fri, 4 Sep 2026 00:26:19 +0800 Subject: [PATCH 2/3] fix(v2): validate bundled skill registration --- .../engine/shared/bundled-skill-library.ts | 19 ++++++++----------- .../src/core/managed-skill-library.test.ts | 15 +++++++++++++++ 2 files changed, 23 insertions(+), 11 deletions(-) diff --git a/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.ts b/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.ts index a498c7db5..00078369c 100644 --- a/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.ts +++ b/apps/main-2.0/src/automation/engine/shared/bundled-skill-library.ts @@ -117,17 +117,14 @@ function metadataFor(skillId: string): BundledSkillMetadata { } function orderedSkillEntries(): Array<[string, string]> { - const order = new Map(BUNDLED_SKILL_ORDER.map((id, index) => [id, index])); - return Object.entries(skillMarkdownFiles) - .filter(([filePath]) => order.has(skillIdFromPath(filePath))) - .sort(([leftPath], [rightPath]) => { - const leftId = skillIdFromPath(leftPath); - const rightId = skillIdFromPath(rightPath); - const leftOrder = order.get(leftId) ?? Number.MAX_SAFE_INTEGER; - const rightOrder = order.get(rightId) ?? Number.MAX_SAFE_INTEGER; - if (leftOrder !== rightOrder) return leftOrder - rightOrder; - return leftId.localeCompare(rightId); - }); + return BUNDLED_SKILL_ORDER.map((skillId) => { + const filePath = `${BUNDLED_SKILL_ROOT}/${skillId}/SKILL.md`; + const prompt = skillMarkdownFiles[filePath]; + if (prompt === undefined) { + throw new Error(`Bundled Automation Skill is missing its canonical asset: ${filePath}`); + } + return [filePath, prompt]; + }); } export function loadBundledSkillTemplates(): SkillTemplate[] { diff --git a/apps/main-2.0/src/core/managed-skill-library.test.ts b/apps/main-2.0/src/core/managed-skill-library.test.ts index 86f77808b..bf5eca66d 100644 --- a/apps/main-2.0/src/core/managed-skill-library.test.ts +++ b/apps/main-2.0/src/core/managed-skill-library.test.ts @@ -11,6 +11,7 @@ import { ManagedSkillLibrary, type SkillInstallTarget, } from "./managed-skill-library"; +import { loadBundledSkillTemplates } from "../automation/engine/shared/bundled-skill-library"; const temporaryDirectories: string[] = []; @@ -122,6 +123,20 @@ function replaceRealpathSync(replacement: typeof fs.realpathSync): () => void { } describe("AgentRecall bundled Skills", () => { + it("registers every canonical Skill as an Automation template or managed built-in", () => { + const bundledSkillsRoot = fileURLToPath(new URL("../../assets/bundled-skills/", import.meta.url)); + const canonicalSkillIds = fs.readdirSync(bundledSkillsRoot, { withFileTypes: true }) + .filter((entry) => entry.isDirectory() && fs.existsSync(path.join(bundledSkillsRoot, entry.name, "SKILL.md"))) + .map((entry) => entry.name) + .sort(); + const registeredSkillIds = new Set([ + ...loadBundledSkillTemplates().map((template) => template.id), + ...AGENT_RECALL_BUILTIN_SKILLS.map((definition) => definition.id), + ]); + + expect([...registeredSkillIds].sort()).toEqual(canonicalSkillIds); + }); + it("keeps every managed built-in definition backed by canonical assets", () => { for (const definition of AGENT_RECALL_BUILTIN_SKILLS) { const bundledSkillRoot = new URL(`../../assets/bundled-skills/${definition.id}/`, import.meta.url); From 418c63cee75503280ea1ec12bc22f61639ef5fa4 Mon Sep 17 00:00:00 2001 From: Akuma <2374973868@qq.com> Date: Fri, 4 Sep 2026 09:31:20 +0800 Subject: [PATCH 3/3] fix(v2): keep Skill smoke bundles out of production --- apps/main-2.0/electron.vite.config.ts | 2 -- apps/main-2.0/scripts/package-smoke.mjs | 32 +++++++++++++++++++++---- 2 files changed, 28 insertions(+), 6 deletions(-) diff --git a/apps/main-2.0/electron.vite.config.ts b/apps/main-2.0/electron.vite.config.ts index fe46865ed..4f40f8a6c 100644 --- a/apps/main-2.0/electron.vite.config.ts +++ b/apps/main-2.0/electron.vite.config.ts @@ -10,8 +10,6 @@ export default defineConfig({ input: { index: resolve("src/main/index.ts"), "live-session-worker": resolve("src/main/live-session-worker.ts"), - "bundled-skill-library": resolve("src/automation/engine/shared/bundled-skill-library.ts"), - "managed-skill-library": resolve("src/core/managed-skill-library.ts"), }, }, }, diff --git a/apps/main-2.0/scripts/package-smoke.mjs b/apps/main-2.0/scripts/package-smoke.mjs index 0de01cac1..866125b72 100644 --- a/apps/main-2.0/scripts/package-smoke.mjs +++ b/apps/main-2.0/scripts/package-smoke.mjs @@ -6,6 +6,7 @@ import path from "node:path"; import { createRequire } from "node:module"; import { fileURLToPath, pathToFileURL } from "node:url"; import { promisify } from "node:util"; +import { build as viteBuild } from "vite"; import { packReleaseArchive } from "./pack-release.mjs"; const execFileAsync = promisify(execFile); @@ -15,6 +16,7 @@ const packDir = path.join(tempRoot, "pack"); const prefix = path.join(tempRoot, "prefix"); const stageRoot = path.join(tempRoot, "stage"); const home = path.join(tempRoot, "home"); +const skillVerifierRoot = path.join(tempRoot, "skill-verifier"); const npm = process.platform === "win32" ? "npm.cmd" : "npm"; const environment = { ...process.env, @@ -125,8 +127,6 @@ try { await Promise.all([ access(path.join(installedRoot, "out", "main", "index.js")), access(path.join(installedRoot, "out", "main", "live-session-worker.js")), - access(path.join(installedRoot, "out", "main", "bundled-skill-library.js")), - access(path.join(installedRoot, "out", "main", "managed-skill-library.js")), ]); await access(path.join(installedRoot, "out", "mcp", "workflow-entry.js")); await access(path.join(installedRoot, "dist", "main", "index.js")); @@ -148,7 +148,31 @@ try { throw new Error("Packaged diagram Skill must include all 66 SVG samples."); } - const bundledSkillLibrary = await import(pathToFileURL(path.join(installedRoot, "out", "main", "bundled-skill-library.js")).href); + // Keep smoke-only entry points out of out/main. The installed package is the + // Vite root so absolute asset globs read the exact files in the archive. + await viteBuild({ + root: installedRoot, + configFile: false, + publicDir: false, + logLevel: "warn", + build: { + ssr: true, + target: "node22", + outDir: skillVerifierRoot, + emptyOutDir: true, + rollupOptions: { + input: { + "bundled-skill-library": path.join(root, "src", "automation", "engine", "shared", "bundled-skill-library.ts"), + "managed-skill-library": path.join(root, "src", "core", "managed-skill-library.ts"), + }, + output: { + entryFileNames: "[name].mjs", + }, + }, + }, + }); + + const bundledSkillLibrary = await import(pathToFileURL(path.join(skillVerifierRoot, "bundled-skill-library.mjs")).href); const loadBundledSkillTemplates = bundledSkillLibrary.loadBundledSkillTemplates ?? bundledSkillLibrary.default?.loadBundledSkillTemplates; const bundledSkillAssetsFor = bundledSkillLibrary.bundledSkillAssetsFor ?? bundledSkillLibrary.default?.bundledSkillAssetsFor; if (typeof loadBundledSkillTemplates !== "function" || typeof bundledSkillAssetsFor !== "function") { @@ -165,7 +189,7 @@ try { throw new Error("Packaged Automation loader must embed all 66 diagram SVG samples."); } - const managedSkillLibraryModule = await import(pathToFileURL(path.join(installedRoot, "out", "main", "managed-skill-library.js")).href); + const managedSkillLibraryModule = await import(pathToFileURL(path.join(skillVerifierRoot, "managed-skill-library.mjs")).href); const ManagedSkillLibrary = managedSkillLibraryModule.ManagedSkillLibrary ?? managedSkillLibraryModule.default?.ManagedSkillLibrary; if (typeof ManagedSkillLibrary !== "function") throw new Error("Packaged managed Skill library was not exported."); const managedLibrary = new ManagedSkillLibrary({