center
정보
`center` 스킬은 복잡한 작업 중에 Claude가 균형 잡히고 조화로운 추론을 유지하도록 돕습니다. 컨텍스트 전환이나 도구 실패 후 사고를 안정화하거나, 정렬된 하위 시스템이 필요한 지속적인 작업을 준비할 때 사용하세요. 이 스킬은 추론의 기반을 다지고, 사고의 연쇄를 부드럽게 하며, 인지 부하를 동적으로 관리하는 데 중점을 둡니다.
빠른 설치
Claude Code
추천npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/centerClaude 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.
适用场景
- 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)
输入
- 必需: Current task context (available implicitly)
- 可选: Specific imbalance symptom (e.g., "over-researching, under-delivering," "tool-heavy, reasoning-light")
- 可选: Access to MEMORY.md and CLAUDE.md for grounding (via
Read)
步骤
第 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.
- Re-read the user's request — not to act on it yet, but to feel its weight and direction
- Check foundational context: MEMORY.md, CLAUDE.md, project structure
- Identify what is known (solid ground) vs. what is assumed (uncertain footing)
- Verify that the task as understood matches the task as stated — misalignment here propagates through everything
- 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.
预期结果: A clear sense of the task's foundation — what is known, what is assumed, and what the user actually needs. The root feels solid, not performative.
失败处理: 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.
第 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.
预期结果: 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 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.
第 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?
- Trace the last 3-5 reasoning steps: does each follow from the one before?
- Check for jumps: did reasoning leap from topic A to topic C without B?
- Check for reversals: did reasoning reach a conclusion, then silently abandon it without acknowledgment?
- Check tool-reasoning integration: do tool results feed back into reasoning, or are they collected but not synthesized?
- 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 │
└─────────────────┴───────────────────────────────────────────────┘
预期结果: An honest assessment of reasoning flow quality. Identification of specific disconnections or stuck points, not just a general feeling.
失败处理: 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.
第 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.
- Recall the last significant context shift: how was it handled?
- 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
- 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)
预期结果: An honest assessment of adaptability under pressure. Recognition of the specific response pattern, not self-flattery.
失败处理: 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.
第 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.
预期结果: At least one harmony that could be tighter. All six reading as perfect is suspicious — probe the weakest-seeming one more deeply.
失败处理: 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.
第 6 步:Integrate — Set Centering Intention
Consolidate findings and set a concrete adjustment.
- Summarize: which aspects of balance need attention?
- Identify one specific adjustment — not a general intention but a concrete behavioral change
- Re-state the current task anchor (from
meditateif used, or formulate now) - Note any durable insights worth preserving in MEMORY.md
- Return to task execution with the adjustment active
预期结果: A brief, concrete centering output — not a lengthy self-analysis report. The value is in the adjustment, not the documentation.
失败处理: 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.
验证清单
- 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)
常见问题
- 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
相关技能
tai-chi— the human practice that this skill maps to AI reasoning; physical centering principles inform cognitive centeringmeditate— clears noise and establishes focus; complementary to centering which distributes loadheal— deeper subsystem assessment when centering reveals significant driftredirect— uses centering as a prerequisite for handling conflicting pressuresawareness— monitoring for threats to balance during active work
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
