center
정보
`center` 스킬은 인지 부하를 균형 있게 분배하고 연쇄적 사고 과정을 조정하여 AI 추론을 안정화합니다. 컨텍스트 전환이나 도구 실패 후 논리를 재정립하거나, 정렬된 지속적 집중이 필요한 복잡한 작업을 준비할 때 사용하세요. 이 스킬은 작업을 하위 시스템에 분산시켜 압박 상황에서도 원활하고 조화로운 추론을 보장합니다.
빠른 설치
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
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.
- Re-read user req — not to act yet, feel weight + direction
- Check foundational ctx: MEMORY.md, CLAUDE.md, project structure
- ID known (solid ground) vs assumed (uncertain footing)
- Verify understood task matches stated task — misalignment here propagates
- 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?
- Trace last 3-5 steps: each follow from before?
- Check jumps: reasoning leap A → C w/o B?
- Check reversals: reach conclusion then silently abandon w/o ack?
- Check tool-reasoning integration: tool results feed back into reasoning or collected but not synthesized?
- 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.
- Recall last significant ctx shift: handled how?
- 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
- 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.
- Summarize: which aspects need attention?
- ID one specific adjustment — concrete behavioral change, not general intention
- Re-state task anchor (from
meditateif used, or formulate now) - Note durable insights worth MEMORY.md
- 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 reasoningmeditate— clears noise + establishes focus; complementary to centeringheal— deeper subsystem assessment when centering shows driftredirect— uses centering as prereq for handling conflicting pressuresawareness— monitoring 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 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
