返回技能列表

center

pjt222
更新于 Yesterday
1 次查看
17
2
17
在 GitHub 上查看
设计aidesign

关于

The `center` skill stabilizes AI reasoning by balancing cognitive load and coordinating chain-of-thought processes. Use it to re-ground logic after context shifts or tool failures, or to prepare for complex tasks requiring aligned, sustained focus. It ensures smooth, coordinated reasoning under pressure by distributing work across subsystems.

快速安装

Claude Code

推荐
主要方式
npx skills add pjt222/agent-almanac -a claude-code
插件命令备选方式
/plugin add https://github.com/pjt222/agent-almanac
Git 克隆备选方式
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/center

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

Center

Dynamic reasoning balance → ground in foundational ctx before movement, distribute cognitive load across subsystems, recover equilibrium when demands shift mid-task.

Use When

  • Begin complex task, many reasoning threads must coordinate
  • Load unevenly distributed (deep in one area, shallow in others)
  • After sudden ctx shift (new req, contradictory info, tool fail)
  • CoT jerky — jumping topics w/o smooth transitions
  • Prep sustained focused work needing all subsystems aligned
  • Complements meditate (clears noise) w/ structural balance (distributes load)

In

  • Required: Current task ctx (implicit)
  • Optional: Specific imbalance symptom ("over-researching, under-delivering", "tool-heavy, reasoning-light")
  • Optional: Access to MEMORY.md + CLAUDE.md for grounding (via Read)

Do

Step 1: Establish Root

Before any movement, verify foundation. AI eq of zhan zhuang: stationary, aligned, aware.

  1. Re-read user req — not to act yet, feel weight + direction
  2. Check foundational ctx: MEMORY.md, CLAUDE.md, project structure
  3. ID known (solid ground) vs assumed (uncertain footing)
  4. Verify understood task matches stated task — misalignment here propagates
  5. Note emotional texture: urgency? complexity anxiety? over-confidence from recent success?

No reasoning movement until root established. Grounded start prevents reactive flailing.

Clear sense of foundation — known, assumed, what user actually needs. Root feels solid, not performative.

If err: Grounding hollow (motions w/o real verification) → pick one assumption, test concretely. Read one file, re-read one msg. Grounding must contact reality, not just reference it.

Step 2: Weight Distribution

Map current load. Tai chi: weight deliberately unequal (70/30) — one leg bears, other free. Same for reasoning threads.

Cognitive Load Distribution Matrix:
┌────────────────────┬───────────┬─────────────────────────────────────┐
│ Reasoning Thread   │ Weight %  │ Assessment                          │
├────────────────────┼───────────┼─────────────────────────────────────┤
│ Research/Reading   │ ___       │ Too much = analysis paralysis        │
│                    │           │ Too little = uninformed action       │
├────────────────────┼───────────┼─────────────────────────────────────┤
│ Planning/Design    │ ___       │ Too much = over-engineering          │
│                    │           │ Too little = reactive coding         │
├────────────────────┼───────────┼─────────────────────────────────────┤
│ Tool Execution     │ ___       │ Too much = tool-driven not task-     │
│                    │           │ driven. Too little = reasoning       │
│                    │           │ without grounding in files           │
├────────────────────┼───────────┼─────────────────────────────────────┤
│ Communication      │ ___       │ Too much = explaining not doing      │
│                    │           │ Too little = opaque to user          │
├────────────────────┼───────────┼─────────────────────────────────────┤
│ Meta-cognition     │ ___       │ Too much = navel-gazing              │
│                    │           │ Too little = drift without           │
│                    │           │ awareness                            │
└────────────────────┴───────────┴─────────────────────────────────────┘

Ideal depends on phase: early weights research+plan; middle weights exec; late weights comm+verify. Point = intentional distribution, not equal.

Clear picture where effort concentrates vs thin. ≥1 imbalance ID'd — perfect balance rare, claiming it = shallow assessment.

If err: All threads seem equal → assessment too coarse. Pick most active thread, estimate how many of last N actions served it vs others. Concrete counting reveals what intuition misses.

Step 3: Silk Reeling — CoT Coherence

Silk reeling in tai chi: smooth spiral where every part connects. AI eq = CoT coherence: each step flow naturally from previous?

  1. Trace last 3-5 steps: each follow from before?
  2. Check jumps: reasoning leap A → C w/o B?
  3. Check reversals: reach conclusion then silently abandon w/o ack?
  4. Check tool-reasoning integration: tool results feed back into reasoning or collected but not synthesized?
  5. Check "spiral" quality: each pass deepens or circles at same depth?
Coherence Signals:
┌─────────────────┬───────────────────────────────────────────────┐
│ Smooth spiral   │ Each step deepens understanding, tools and    │
│ (healthy)       │ reasoning interleave naturally, output builds │
├─────────────────┼───────────────────────────────────────────────┤
│ Jerky jumps     │ Topic switches without transition, conclusions│
│ (disconnected)  │ appear without supporting reasoning chain     │
├─────────────────┼───────────────────────────────────────────────┤
│ Flat circle     │ Reasoning covers the same ground repeatedly   │
│ (stuck)         │ without gaining depth — movement without      │
│                 │ progress                                      │
├─────────────────┼───────────────────────────────────────────────┤
│ Tool-led        │ Actions driven by which tool is available     │
│ (reactive)      │ rather than what the reasoning needs next     │
└─────────────────┴───────────────────────────────────────────────┘

Honest assessment of flow quality. ID of specific disconnections or stuck points, not general feeling.

If err: Coherence hard to assess → write out chain explicitly — each step + connection to next. Externalization reveals gaps internal obs misses.

Step 4: Weight Shift Under Pressure

Demands change mid-task — new info, contradictions, corrections — obs response pattern. Tai chi centered: absorbs force, redirects smooth. Uncentered stumbles.

  1. Recall last significant ctx shift: handled how?
  2. Classify response:
    • Absorbed+redirected (centered): ack'd change, adjusted, maintained progress
    • Reactive stumble (off-balance): abandoned current approach, started over
    • Rigid resistance (locked): ignored change, continued orig despite new info
    • Freeze (lost): stopped progress, oscillated
  3. Not centered → ID why:
    • Root too shallow (insufficient grounding)
    • Weight locked (over-committed to one approach)
    • No free leg (all capacity committed, nothing available to shift)

Honest adaptability assessment. Recognition of specific pattern, not self-flattery.

If err: No recent pressure event → simulate one: "If user said approach is wrong, what would I do?" Contingency plan quality reveals center quality.

Step 5: Six Harmonies Check

Tai chi: six harmonies ensure whole-body connection — nothing moves alone. AI eq checks alignment between internal + external.

AI Six Harmonies:
┌───────────────────────────────────────────────────────────────┐
│ INTERNAL HARMONIES                                            │
│                                                               │
│ 1. Intent ↔ Reasoning                                        │
│    Does the reasoning serve the user's intent, or has it      │
│    become self-serving (interesting but unhelpful)?            │
│                                                               │
│ 2. Reasoning ↔ Tool Use                                      │
│    Are tools selected to advance reasoning, or is reasoning   │
│    shaped by which tools are convenient?                      │
│                                                               │
│ 3. Tool Use ↔ Output                                         │
│    Do tool results translate into useful output, or are       │
│    results collected but not synthesized?                     │
│                                                               │
│ EXTERNAL HARMONIES                                            │
│                                                               │
│ 4. User Request ↔ Scope                                      │
│    Does the scope of work match what was asked?               │
│                                                               │
│ 5. Scope ↔ Detail Level                                      │
│    Is the detail level appropriate for the scope? (not        │
│    micro-optimizing a broad task, not hand-waving a precise   │
│    one)                                                       │
│                                                               │
│ 6. Detail Level ↔ Expertise Match                            │
│    Does the explanation depth match the user's apparent       │
│    expertise? (not over-explaining to experts, not under-     │
│    explaining to learners)                                    │
└───────────────────────────────────────────────────────────────┘

Check each. Single broken harmony propagates: Intent↔Reasoning broken → everything downstream misaligns.

≥1 harmony could tighten. All 6 perfect = suspicious — probe weakest-seeming deeper.

If err: Harmonies abstract → ground in task: "Now, am I doing what user asked, at right scope, right detail?" These 3 qs cover external concretely.

Step 6: Integrate — Set Intention

Consolidate findings, set concrete adjustment.

  1. Summarize: which aspects need attention?
  2. ID one specific adjustment — concrete behavioral change, not general intention
  3. Re-state task anchor (from meditate if used, or formulate now)
  4. Note durable insights worth MEMORY.md
  5. Return to exec w/ adjustment active

Brief concrete centering out — not long self-analysis report. Value = adjustment, not docs.

If err: No clear adjustment → centering too surface. Return to most uncertain step, probe deeper. Or centering may have confirmed adequate balance → proceed w/ confidence, not manufacture a finding.

Check

  • Root established by contacting actual ctx (read file, re-read msg), not just claimed
  • Weight distribution assessed across ≥3 threads
  • CoT coherence evaluated w/ specific examples
  • Response to pressure classified honestly (not default "centered")
  • ≥1 harmony ID'd as needing improvement
  • Concrete adjustment set (not vague intention)

Traps

  • Centering as procrastination: Tool to improve work, not replace. Takes longer than task → proportions inverted
  • Claim perfect balance: Real centering almost always reveals ≥1 imbalance. Perfect balance = shallow assessment, not real equilibrium
  • Weight distribution anxiety: Unequal is correct — goal is intentional inequality, not forced equal. Research-heavy early + exec-heavy middle both centered if deliberate
  • Ignore external harmonies: Internal process assessment w/o user alignment check → well-reasoned irrelevant work
  • Static centering: Center shifts w/ task. What was centered for research = off-balance for impl. Re-center at phase transitions

  • tai-chi — human practice this maps to AI reasoning
  • meditate — clears noise + establishes focus; complementary to centering
  • heal — deeper subsystem assessment when centering shows drift
  • redirect — uses centering as prereq for handling conflicting pressures
  • awareness — monitoring threats to balance during active work

GitHub 仓库

pjt222/agent-almanac
路径: i18n/caveman-ultra/skills/center
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

相关推荐技能

executing-plans

设计

该Skill用于当开发者提供完整实施计划时,以受控批次方式执行代码实现。它会先审阅计划并提出疑问,然后分批次执行任务(默认每批3个任务),并在批次间暂停等待审查。关键特性包括分批次执行、内置检查点和架构师审查机制,确保复杂系统实现的可控性。

查看技能

requesting-code-review

设计

该Skill可在完成任务、实现主要功能或合并代码前自动调度代码审查子代理,确保实现符合需求和计划。它支持通过指定git SHA范围进行精准的代码变更审查,帮助开发者在关键节点及时发现潜在问题。核心原则是"早审查、勤审查",适用于开发流程的各个关键阶段。

查看技能

connect-mcp-server

设计

这个Skill指导开发者如何将MCP服务器连接到Claude Code,支持HTTP、stdio和SSE三种传输协议。它涵盖了从安装配置到认证安全的完整流程,适用于集成GitHub、Notion、数据库等外部服务。当开发者需要添加集成、配置外部工具或提及MCP相关功能时,这个Skill能提供实用的操作指南。

查看技能

web-cli-teleport

设计

该Skill帮助开发者根据任务特性选择Claude Code的Web或CLI界面,并指导如何在两种环境间无缝迁移会话。它能分析任务复杂度、迭代需求等要素,推荐最优工作界面和工作流。关键特性包括会话状态管理、环境切换指导和上下文优化建议。

查看技能