Meta Cognition Parallel

actionbook/rust-skills/skills/meta-cognition-parallel

作者 actionbook5c40d3ad7851無授權條款1.5K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫6 週前更新

EXPERIMENTAL: Three-layer parallel meta-cognition analysis. Triggers on: /meta-parallel, 三层分析, parallel analysis, 并行元认知

僅含說明Software DevelopmentAI & Agents
AI 產生的概覽

針對 Rust 問題的實驗性三層元認知分析，涵蓋語言機制、設計選擇與領域限制。

功能
這個實驗性技能從三個認知層次分析 Rust 問題：語言機制（所有權、借用、生命週期、錯誤碼）、設計選擇（智慧指標、內部可變性、複製與參照）以及領域限制（效能、安全、並行、可稽核性）。接著進行跨層綜合，把領域限制串接到設計模式再到語言機制，給出建議的架構方案與信心程度評估。它支援平行代理模式（啟動三個背景分析器），在缺少層分析器檔案時退回為循序內聯模式。
適用情境
當 Rust 問題需要超出單一錯誤修復的推理時使用，例如交易系統中的所有權或借用檢查錯誤、Web API 中的共享狀態，或 CLI 工具的設定優先順序。它適用於需要讓領域需求影響設計與實作選擇的問題。
執行需求
不附帶指令碼，僅為指示。代理模式需要 ../../agents/ 下的層分析器檔案（layer1-analyzer.md、layer2-analyzer.md、layer3-analyzer.md）以及啟動背景子代理任務的能力；缺少這些檔案時退回為循序內聯分析。呼叫方式為 /meta-parallel 並附上一個 Rust 問題作為參數。

Meta-Cognition Parallel Analysis (Experimental)

Status: Experimental | Version: 0.2.0 | Last Updated: 2025-01-27

This skill tests parallel three-layer cognitive analysis.

Concept

Instead of sequential analysis, this skill launches three parallel analyzers - one for each cognitive layer - then synthesizes their results.

User Question     │     ▼┌─────────────────────────────────────────────────────┐│            meta-cognition-parallel                   ││                  (Coordinator)                       │└─────────────────────────────────────────────────────┘     │     ├─── Layer 1 ──► Language Mechanics ──► L1 Result     │     ├─── Layer 2 ──► Design Choices     ──► L2 Result     │                                            ├── Parallel (Agent Mode)     │                                            │   or Sequential (Inline)     └─── Layer 3 ──► Domain Constraints ──► L3 Result     │     ▼┌─────────────────────────────────────────────────────┐│              Cross-Layer Synthesis                   ││         (In main context with all results)          │└─────────────────────────────────────────────────────┘     │     ▼Domain-Correct Architectural Solution

Usage

/meta-parallel <your Rust question>

Example:

/meta-parallel 我的交易系统报 E0382 错误，应该用 clone 吗？

Execution Mode Detection

CRITICAL: Check agent file availability first to determine execution mode.

Try to read layer analyzer files:

  • ../../agents/layer1-analyzer.md
  • ../../agents/layer2-analyzer.md
  • ../../agents/layer3-analyzer.md

Agent Mode (Plugin Install) - Parallel Execution

When all layer analyzer files exist at ../../agents/:

Step 1: Parse User Query

Extract from $ARGUMENTS:

  • The original question
  • Any code snippets
  • Domain hints (trading, web, embedded, etc.)

Step 2: Launch Three Parallel Agents

CRITICAL: Launch all three Tasks in a SINGLE message to enable parallel execution.

Read agent files, then launch in parallel:
Task(  subagent_type: "general-purpose",  run_in_background: true,  prompt: <content of ../../agents/layer1-analyzer.md>          + "\n\n## User Query\n" + $ARGUMENTS)
Task(  subagent_type: "general-purpose",  run_in_background: true,  prompt: <content of ../../agents/layer2-analyzer.md>          + "\n\n## User Query\n" + $ARGUMENTS)
Task(  subagent_type: "general-purpose",  run_in_background: true,  prompt: <content of ../../agents/layer3-analyzer.md>          + "\n\n## User Query\n" + $ARGUMENTS)

Step 3: Collect Results

Wait for all three agents to complete. Each returns structured analysis.

Step 4: Cross-Layer Synthesis

With all three results, perform synthesis per template below.

Inline Mode (Skills-only Install) - Sequential Execution

When layer analyzer files are NOT available, execute analysis directly:

Step 1: Parse User Query

Same as Agent Mode - extract question, code, and domain hints from $ARGUMENTS.

Step 2: Execute Layer 1 - Language Mechanics

Analyze the Rust language mechanics involved:

markdown
## Layer 1: Language Mechanics
**Error/Pattern Identified:**- Error code: E0XXX (if applicable)- Pattern: ownership/borrowing/lifetime/etc.
**Root Cause:**[Explain why this error occurs in terms of Rust's ownership model]
**Language-Level Solutions:**1. [Solution 1]: description2. [Solution 2]: description
**Confidence:** HIGH | MEDIUM | LOW**Reasoning:** [Why this confidence level]

Focus areas:

  • Ownership rules (move, copy, borrow)
  • Lifetime annotations
  • Borrowing rules (shared vs mutable)
  • Error codes and their meanings

Step 3: Execute Layer 2 - Design Choices

Analyze the design patterns and trade-offs:

markdown
## Layer 2: Design Choices
**Design Pattern Context:**- Current approach: [What pattern is being used]- Problem: [Why it conflicts with Rust's rules]
**Design Alternatives:**| Pattern | Pros | Cons | When to Use ||---------|------|------|-------------|| Pattern A | ... | ... | ... || Pattern B | ... | ... | ... |
**Recommended Pattern:**[Which pattern fits best and why]
**Confidence:** HIGH | MEDIUM | LOW**Reasoning:** [Why this confidence level]

Focus areas:

  • Smart pointer choices (Box, Rc, Arc)
  • Interior mutability patterns (Cell, RefCell, Mutex)
  • Ownership transfer vs sharing
  • Cloning vs references

Step 4: Execute Layer 3 - Domain Constraints

Analyze domain-specific requirements:

markdown
## Layer 3: Domain Constraints
**Domain Identified:** [trading/fintech | web | CLI | embedded | etc.]
**Domain-Specific Requirements:**- [ ] Performance: [requirements]- [ ] Safety: [requirements]- [ ] Concurrency: [requirements]- [ ] Auditability: [requirements]
**Domain Best Practices:**1. [Best practice 1]2. [Best practice 2]
**Constraints on Solution:**- MUST: [hard requirements]- SHOULD: [soft requirements]- AVOID: [anti-patterns for this domain]
**Confidence:** HIGH | MEDIUM | LOW**Reasoning:** [Why this confidence level]

Focus areas:

  • Industry requirements (FinTech regulations, web scalability, etc.)
  • Performance constraints
  • Safety and correctness requirements
  • Common patterns in the domain

Step 5: Cross-Layer Synthesis

Combine all three layers:

markdown
## Cross-Layer Synthesis
### Layer Results Summary
| Layer | Key Finding | Confidence ||-------|-------------|------------|| L1 (Mechanics) | [Summary] | [Level] || L2 (Design) | [Summary] | [Level] || L3 (Domain) | [Summary] | [Level] |
### Cross-Layer Reasoning
1. **L3 → L2:** [How domain constraints affect design choice]2. **L2 → L1:** [How design choice determines mechanism]3. **L1 ← L3:** [Direct domain impact on language features]
### Synthesized Recommendation
**Problem:** [Restated with full context]
**Solution:** [Domain-correct architectural solution]
**Rationale:**- Domain requires: [L3 constraint]- Design pattern: [L2 pattern]- Mechanism: [L1 implementation]
### Confidence Assessment
- **Overall:** HIGH | MEDIUM | LOW- **Limiting Factor:** [Which layer had lowest confidence]

Output Template

Both modes produce the same output format:

markdown
# Three-Layer Meta-Cognition Analysis
> Query: [User's question]
---
## Layer 1: Language Mechanics[L1 analysis result]
---
## Layer 2: Design Choices[L2 analysis result]
---
## Layer 3: Domain Constraints[L3 analysis result]
---
## Cross-Layer Synthesis
### Reasoning Chain

L3 Domain: [Constraint] ↓ implies L2 Design: [Pattern] ↓ implemented via L1 Mechanism: [Feature]


### Final Recommendation
**Do:** [Recommended approach]
**Don't:** [What to avoid]
**Code Pattern:**```rust// Recommended implementation

Analysis performed by meta-cognition-parallel v0.2.0 (experimental)


---
## Test Scenarios
### Test 1: Trading System E0382

/meta-parallel 交易系统报 E0382，trade record 被 move 了


Expected: L3 identifies FinTech constraints → L2 suggests shared immutable → L1 recommends Arc<T>
### Test 2: Web API Concurrency

/meta-parallel Web API 中多个 handler 需要共享数据库连接池


Expected: L3 identifies Web constraints → L2 suggests connection pooling → L1 recommends Arc<Pool>
### Test 3: CLI Tool Config

/meta-parallel CLI 工具如何处理配置文件和命令行参数的优先级


Expected: L3 identifies CLI constraints → L2 suggests config precedence pattern → L1 recommends builder pattern
---
## Error Handling
| Error | Cause | Solution ||-------|-------|----------|| Agent files not found | Skills-only install | Use inline mode (sequential) || Agent timeout | Complex analysis | Wait longer or use inline mode || Incomplete layer result | Agent issue | Fill in with inline analysis |
## Limitations
- **Agent Mode:** Parallel execution, faster but requires plugin install- **Inline Mode:** Sequential execution, slower but works everywhere- Cross-layer synthesis quality depends on result structure- May have higher latency than simple single-layer analysis
## Feedback
This is experimental. Please report issues and suggestions to improve the three-layer analysis approach.

來源與署名

來源：actionbook/rust-skills位於skills/meta-cognition-parallel提交5c40d3a

授權條款： 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 actionbook/rust-skills 的技能

Rust Trait Explorer

actionbook

使用 LSP 導覽與 grep 探索 Rust trait 實作以及型別與 trait 的關係。

Software Development1.5K6 週前更新

Rust Symbol Analyzer

actionbook

透過 LSP 查詢列出結構體、trait、函式與模組等符號，分析 Rust 專案結構。

Software Development1.5K6 週前更新

Rust Skill Creator

actionbook

透過抓取官方文件，建立用來記錄 Rust crate 或標準函式庫項目的代理技能。

AI & Agents1.5K6 週前更新

Rust Router

actionbook

將 Rust 問題路由到合適的技能層級，從語言機制到領域限制。

Software Development1.5K6 週前更新

Rust Refactor Helper

actionbook

透過 LSP 分析安全重構 Rust 程式碼，並在套用變更前預覽影響範圍。

Software Development1.5K6 週前更新

Rust Daily

actionbook

從 Reddit、This Week in Rust、官方部落格與 Rust 基金會抓取 Rust 社群新聞，並整理成日報、週報或月報。

Research & Analysis1.5K6 週前更新

更多Software Development技能

Playground

anthropics

精選

建立自成一體的互動式 HTML 遊樂場，包含控制項、即時預覽與可複製的提示詞輸出。

Software Development37K今天更新

M5 Onboard

anthropics

精選

透過 USB 偵測 M5Stack ESP32 開發板，燒錄 UIFlow 2.0 韌體並安裝 MicroPython 應用程式套件。

Software Development37K今天更新

Cardputer Buddy

anthropics

精選

指導迭代 Cardputer-Adv 的 MicroPython 應用程式套件：新增應用程式、透過 USB 序列埠推送檔案、查看日誌並執行 REPL 指令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精選

依據從遠端來源取得的 Web Interface Guidelines 審查 UI 程式碼，並以 file:line 形式回報問題。

Software Development32K5 週前更新

Vercel React Native Skills

vercel-labs

精選

React Native 與 Expo 最佳實務規則，涵蓋清單效能、動畫、導覽、UI 模式、狀態與 monorepo 設定。

Software Development32K5 週前更新

Vercel React Best Practices

vercel-labs

精選

Vercel 的 React 與 Next.js 效能指南，以 70 條規則的形式用於撰寫、審查與重構程式碼。

Software Development32K5 週前更新