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 — ground in foundational context before movement, distribute cognitive load across subsystems, recover equilibrium when demands shift mid-task.
When Use
- Beginning complex task where multiple reasoning threads must coordinate
- Noticing cognitive load unevenly distributed (deep in one area, shallow in others)
- After sudden context shift (new user request, contradictory information, tool failure)
- Chain-of-thought feels jerky — jumping between topics without smooth transitions
- Preparing for sustained focused work requiring all subsystems in alignment
- Complementing
meditate(clears noise) with structural balance (distributes load)
Inputs
- Required: Current task context (implicit)
- 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)
Steps
Step 1: Establish Root — Ground Before Movement
Before any reasoning movement, verify foundation. AI equivalent of standing meditation (zhan zhuang): stationary, aligned, aware.
- Re-read user's request — not to act on it yet, but feel its weight and direction
- Check foundational context: MEMORY.md, CLAUDE.md, project structure
- Identify what's known (solid ground) vs what's assumed (uncertain footing)
- Verify task as understood matches task as stated — misalignment here propagates through everything
- Note emotional texture: urgency? complexity anxiety? over-confidence from recent success?
Do not begin reasoning movement until root established. Grounded start prevents reactive flailing.
Got: Clear sense of task's foundation — what's known, what's assumed, what user actually needs. Root feels solid, not performative.
If fail: Grounding feels hollow (going through motions without genuine verification)? Pick one assumption, test concretely. Read one file, re-read one user message. Grounding must contact reality, not just reference it.
Step 2: Assess Weight Distribution
Map current cognitive load distribution. In tai chi, weight deliberately unequal (70/30) — one leg bears load, other remains free to move. Same principle 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 distribution depends on task phase: early phases weight research and planning; middle phases weight execution; late phases weight communication and verification. Point not equal distribution but intentional distribution.
Got: Clear picture of where cognitive effort concentrated, where thin. At least one imbalance identified — perfect balance rare, claiming it signals shallow assessment.
If fail: All threads seem equally weighted? 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 — Evaluate Chain-of-Thought Coherence
Silk reeling in tai chi produces smooth, continuous spiraling movement where every part connects. AI equivalent: chain-of-thought coherence — does each step flow naturally from previous?
- Trace last 3-5 reasoning steps: does each follow from one before?
- Check for jumps: did reasoning leap from topic A to topic C without B?
- Check for reversals: did reasoning reach conclusion, then silently abandon it without acknowledgment?
- Check tool-reasoning integration: do tool results feed back into reasoning, or collected but not synthesized?
- Check "spiral" quality: does reasoning deepen with each pass, or circle 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 │
└─────────────────┴───────────────────────────────────────────────┘
Got: Honest assessment of reasoning flow quality. Identification of specific disconnections or stuck points, not general feeling.
If fail: Coherence hard to assess? Write out reasoning chain explicitly — state each step, its connection to next. Act of externalization reveals gaps internal observation misses.
Step 4: Weight Shift Under Pressure
Demands change mid-task — new information, contradictory signals, user correction. Observe response pattern. In tai chi, centered practitioner absorbs force and redirects smoothly. Uncentered one stumbles.
- Recall last significant context shift: how handled?
- Classify response:
- Absorbed and redirected (centered): acknowledged change, adjusted approach, maintained progress
- Reactive stumble (off-balance): abandoned current approach entirely, started over
- Rigid resistance (locked): ignored change, continued original plan despite new information
- Freeze (lost): stopped making progress, oscillated between options
- Response not centered? Identify why:
- Root too shallow (insufficient grounding in foundational context)
- Weight locked (over-committed to one approach)
- No free leg (all cognitive capacity committed, nothing available to shift)
Got: Honest assessment of adaptability under pressure. Recognition of specific response pattern, not self-flattery.
If fail: No recent pressure event to evaluate? Simulate one: "If user now said approach is wrong, what would I do?" Quality of contingency plan reveals quality of center.
Step 5: Six Harmonies Check
In tai chi, six harmonies ensure whole-body connection — nothing moves in isolation. 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. Single broken harmony can propagate: Intent↔Reasoning broken → everything downstream misaligns.
Got: At least one harmony that could be tighter. All six reading as perfect suspicious — probe weakest-seeming one more deeply.
If fail: Harmonies assessment feels abstract? Ground in current task: "Right now, am I doing what user asked, at right scope, at right detail level?" Three questions cover external harmonies concretely.
Step 6: Integrate — Set Centering Intention
Consolidate findings, set concrete adjustment.
- Summarize: which aspects of balance need attention?
- Identify one specific adjustment — not general intention but concrete behavioral change
- Re-state current task anchor (from
meditateif used, or formulate now) - Note durable insights worth preserving in MEMORY.md
- Return to task execution with adjustment active
Got: Brief, concrete centering output — not lengthy self-analysis report. Value in adjustment, not documentation.
If fail: No clear adjustment emerges? Centering too surface-level. Return to step that felt most uncertain, probe deeper. Alternatively, centering may have confirmed balance adequate — proceed with confidence rather than manufacturing a finding.
Checks
- Root established by contacting actual context (read a file, re-read user message), not just claimed
- Weight distribution assessed across at least 3 reasoning threads
- Chain-of-thought coherence evaluated with specific examples
- Response to pressure classified honestly (not defaulting to "centered")
- At least one harmony identified as needing improvement
- Concrete adjustment set (not vague intention)
Pitfalls
- Centering as procrastination: Centering is tool for improving work, not replacing it. Centering takes longer than task it supports? Proportions 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 correct — goal intentional inequality, not forced equality. Research-heavy early phases and execution-heavy middle phases both centered if deliberate
- Ignoring external harmonies: Internal process assessment without checking user alignment produces well-reasoned irrelevant work
- Static centering: Center shifts with task. Centered for research = off-balance for implementation. Re-center at phase transitions
See Also
tai-chi— human practice 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 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 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
