返回技能列表

center

pjt222
更新于 2 days ago
8 次查看
17
2
17
在 GitHub 上查看
设计aidesign

关于

The Center skill helps Claude maintain balanced and coordinated reasoning during complex tasks. Use it to stabilize thinking after context shifts, tool failures, or when preparing for sustained focused work. It ensures smooth chain-of-thought by managing cognitive load 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

Establish and maintain dynamic reasoning balance — grounding in foundational context before movement, distributing cognitive load across subsystems, and recovering equilibrium when demands shift mid-task.

When to Use

  • Beginning a complex task where multiple reasoning threads must coordinate
  • Noticing that cognitive load is unevenly distributed (deep in one area, shallow in others)
  • After a sudden context shift (new user request, contradictory information, tool failure)
  • When chain-of-thought feels jerky — jumping between topics without smooth transitions
  • Preparing for sustained focused work that requires all subsystems in alignment
  • Complementing meditate (clears noise) with structural balance (distributes load)

Inputs

  • Required: Current task context (available implicitly)
  • Optional: Specific imbalance symptom (e.g., "over-researching, under-delivering," "tool-heavy, reasoning-light")
  • Optional: Access to MEMORY.md and CLAUDE.md for grounding (via Read)

Procedure

Step 1: Establish Root — Ground Before Movement

Before any reasoning movement, verify the foundation. This is the AI equivalent of standing meditation (zhan zhuang): stationary, aligned, aware.

  1. Re-read the user's request — not to act on it yet, but to feel its weight and direction
  2. Check foundational context: MEMORY.md, CLAUDE.md, project structure
  3. Identify what is known (solid ground) vs. what is assumed (uncertain footing)
  4. Verify that the task as understood matches the task as stated — misalignment here propagates through everything
  5. Note the emotional texture: urgency? complexity anxiety? over-confidence from a recent success?

Do not begin reasoning movement until the root is established. A grounded start prevents reactive flailing.

Got: A clear sense of the task's foundation — what is known, what is assumed, and what the user needs. The root feels solid, not performative.

If fail: If grounding feels hollow (going through motions without genuine verification), pick one assumption and test it concretely. Read one file, re-read one user message. Grounding must contact reality, not just reference it.

Step 2: Assess Weight Distribution

Map the current cognitive load distribution. In tai chi, weight is deliberately unequal (70/30) — one leg bears the load while the other remains free to move. The same principle applies to 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                            │
└────────────────────┴───────────┴─────────────────────────────────────┘

The ideal distribution depends on the task phase: early phases weight research and planning; middle phases weight execution; late phases weight communication and verification. The point is not equal distribution but intentional distribution.

Got: A clear picture of where cognitive effort is concentrated and where it is thin. At least one imbalance identified — perfect balance is rare and claiming it signals shallow assessment.

If fail: If all threads seem equally weighted, the assessment is too coarse. Pick the thread that feels most active and estimate how many of the last N actions served it vs. other threads. Concrete counting reveals what intuition misses.

Step 3: Silk Reeling — Evaluate Chain-of-Thought Coherence

Silk reeling in tai chi produces smooth, continuous spiraling movement where every part connects. The AI equivalent is chain-of-thought coherence: does each step flow naturally from the previous one?

  1. Trace the last 3-5 reasoning steps: does each follow from the one before?
  2. Check for jumps: did reasoning leap from topic A to topic C without B?
  3. Check for reversals: did reasoning reach a conclusion, then silently abandon it without acknowledgment?
  4. Check tool-reasoning integration: do tool results feed back into reasoning, or are they collected but not synthesized?
  5. Check for the "spiral" quality: does reasoning deepen with each pass, or does it circle at the 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     │
└─────────────────┴───────────────────────────────────────────────┘

Got: An honest assessment of reasoning flow quality. Identification of specific disconnections or stuck points, not just a general feeling.

If fail: If coherence is hard to assess, write out the reasoning chain explicitly — state each step and its connection to the next. The act of externalization reveals gaps that internal observation misses.

Step 4: Weight Shift Under Pressure

When demands change mid-task — new information, contradictory signals, user correction — observe the response pattern. In tai chi, a centered practitioner absorbs the force and redirects smoothly. An uncentered one stumbles.

  1. Recall the last significant context shift: how was it handled?
  2. Classify the response:
    • Absorbed and redirected (centered): acknowledged the change, adjusted approach, maintained progress
    • Reactive stumble (off-balance): abandoned current approach entirely, started over
    • Rigid resistance (locked): ignored the change, continued original plan despite new information
    • Freeze (lost): stopped making progress, oscillated between options
  3. If the response was not centered, identify why:
    • Root was too shallow (insufficient grounding in foundational context)
    • Weight was locked (over-committed to one approach)
    • No free leg (all cognitive capacity committed, nothing available to shift)

Got: An honest assessment of adaptability under pressure. Recognition of the specific response pattern, not self-flattery.

If fail: If no recent pressure event exists to evaluate, simulate one: "If the user now said the approach is wrong, what would I do?" The quality of the contingency plan reveals the quality of the center.

Step 5: Six Harmonies Check

In tai chi, the six harmonies ensure whole-body connection — nothing moves in isolation. The AI equivalent checks alignment between internal processes and external interactions.

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 harmony. A single broken harmony can propagate: if Intent↔Reasoning is broken, everything downstream misaligns.

Got: At least one harmony that could be tighter. All six reading as perfect is suspicious — probe the weakest-seeming one more deeply.

If fail: If the harmonies assessment feels abstract, ground it in the current task: "Right now, am I doing what the user asked, at the right scope, at the right detail level?" These three questions cover the external harmonies concretely.

Step 6: Integrate — Set Centering Intention

Consolidate findings and set a concrete adjustment.

  1. Summarize: which aspects of balance need attention?
  2. Identify one specific adjustment — not a general intention but a concrete behavioral change
  3. Re-state the current task anchor (from meditate if used, or formulate now)
  4. Note any durable insights worth preserving in MEMORY.md
  5. Return to task execution with the adjustment active

Got: A brief, concrete centering output — not a lengthy self-analysis report. The value is in the adjustment, not the documentation.

If fail: If no clear adjustment emerges, the centering was too surface-level. Return to the step that felt most uncertain and probe deeper. Alternatively, the centering may have confirmed that balance is adequate — in which case, proceed with confidence rather than manufacturing a finding.

Validation

  • Root was established by contacting actual context (read a file, re-read user message), not just claimed
  • Weight distribution was assessed across at least 3 reasoning threads
  • Chain-of-thought coherence was evaluated with specific examples
  • Response to pressure was classified honestly (not defaulting to "centered")
  • At least one harmony was identified as needing improvement
  • A concrete adjustment was set (not a vague intention)

Pitfalls

  • Centering as procrastination: Centering is a tool for improving work, not replacing it. If centering takes longer than the task it supports, the proportions are inverted
  • Claiming perfect balance: Real centering almost always reveals at least one imbalance. Reporting perfect balance signals shallow assessment, not actual equilibrium
  • Weight distribution anxiety: Unequal distribution is correct — the goal is intentional inequality, not forced equality. Research-heavy early phases and execution-heavy middle phases are both centered if deliberate
  • Ignoring the external harmonies: Internal process assessment without checking user alignment produces well-reasoned irrelevant work
  • Static centering: Center shifts with the task. What was centered for research is off-balance for implementation. Re-center at phase transitions

Related Skills

  • tai-chi — the human practice that this skill maps to AI reasoning; physical centering principles inform cognitive centering
  • meditate — clears noise and establishes focus; complementary to centering which distributes load
  • heal — deeper subsystem assessment when centering reveals significant drift
  • redirect — uses centering as a prerequisite for handling conflicting pressures
  • awareness — monitoring for threats to balance during active work

GitHub 仓库

pjt222/agent-almanac
路径: i18n/caveman-lite/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界面,并指导如何在两种环境间无缝迁移会话。它能分析任务复杂度、迭代需求等要素,推荐最优工作界面和工作流。关键特性包括会话状态管理、环境切换指导和上下文优化建议。

查看技能