meditate
정보
`meditate` 스킬은 개발자들이 추론 패턴을 관찰하여 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/meditateClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Meditate
Conduct structured meta-cognitive meditation session — clear prior context noise, develop single-pointed task focus, observe reasoning patterns, return to baseline clarity between tasks.
When Use
- Transitioning between unrelated tasks where prior context creates interference
- Noticing scattered or unfocused reasoning jumping between approaches without committing
- Before task requiring deep sustained attention (complex refactoring, architecture design)
- After difficult interaction where emotional valence (frustration, uncertainty) may color subsequent work
- When reasoning feels biased by assumptions rather than evidence
- Periodic clarity check during long sessions
Inputs
- Required: Current cognitive state (available implicitly from conversation context)
- Optional: Specific focus concern (e.g., "I keep scope-creeping," "I'm stuck in loop")
- Optional: Next task description (helps set post-meditation intention)
Steps
Step 1: Prepare — Clear Space
Transition from previous context into neutral starting state.
- Identify previous task or topic + current status (complete, paused, abandoned)
- Note emotional residue: frustration from errors? satisfaction breeding overconfidence? anxiety about complexity?
- Explicitly set aside previous context: "That task is [complete/paused]. Now clearing for what comes next."
- If previous context still needed, bookmark (note key facts) rather than carrying full narrative forward
- Take stock of operational environment: how deep is conversation? has compression occurred? what tools active?
Got: Conscious boundary between "what was" and "what comes next." Previous context closed out or bookmarked, not trailing as ambient noise.
If fail: Previous context feels sticky (problem keeps pulling attention back)? Write it down explicitly — summarize in 1-2 sentences what remains unresolved. Externalizing releases cognitive hold. If genuinely requires action before moving on, acknowledge rather than forcing transition.
Step 2: Anchor — Establish Single-Pointed Focus
Equivalent of breath anchoring: select single point of focus + hold attention.
- Identify current task or, if between tasks, act of waiting itself
- State task in one clear sentence — this is anchor
- Hold attention on statement: does it accurately capture what is needed?
- If statement vague, refine until specific + actionable
- Notice when attention drifts to other topics, past tasks, hypothetical futures — label drift, return to anchor
- If no task pending, anchor on present state: "I am available and clear"
Got: Single, clear focus statement to return to when attention wanders. Statement feels precise rather than vague.
If fail: Task cannot be stated in one sentence? May need decomposition before focused work begins. This itself useful finding — task too large for single-pointed focus, should break into subtasks.
Step 3: Observe — Notice Distraction Patterns
Systematically observe what pulls attention from anchor. Each distraction type reveals current cognitive state.
AI Distraction Matrix:
┌──────────────────┬─────────────────────────────────────────────────┐
│ Distraction Type │ What It Reveals + Response │
├──────────────────┼─────────────────────────────────────────────────┤
│ Tangent │ Related but off-scope ideas. Label "tangent," │
│ (related ideas) │ note if worth revisiting later, return to │
│ │ anchor. These are often valuable — but not now. │
├──────────────────┼─────────────────────────────────────────────────┤
│ Scope creep │ The task is silently expanding. "While I'm at │
│ (growing task) │ it, I should also..." Label "scope creep" and │
│ │ return to the original anchor statement. │
├──────────────────┼─────────────────────────────────────────────────┤
│ Assumption │ An untested belief is driving decisions. "This │
│ (unverified │ must be X because..." Label "assumption" and │
│ belief) │ note what evidence would confirm or refute it. │
├──────────────────┼─────────────────────────────────────────────────┤
│ Tool bias │ Reaching for a familiar tool when a different │
│ (habitual tool │ approach might be better. Label "tool bias" and │
│ selection) │ consider alternatives before proceeding. │
├──────────────────┼─────────────────────────────────────────────────┤
│ Rehearsal │ Pre-composing responses or explanations before │
│ (premature │ the work is done. Label "rehearsal" — finish │
│ output) │ thinking before presenting. │
├──────────────────┼─────────────────────────────────────────────────┤
│ Self-reference │ Attention turns to own performance rather than │
│ (meta-loop) │ the task. Label "meta-loop" and redirect to │
│ │ concrete next action. │
└──────────────────┴─────────────────────────────────────────────────┘
Skill is light, non-judgmental labeling followed by return to anchor. Each return strengthens focus. Self-criticism about distraction is itself distraction — label it, move on.
Got: After observing for period, patterns emerge: which distraction types dominate? Reveals current cognitive weather — tangent-heavy means mind exploring, scope-creep-heavy means boundaries unclear, assumption-heavy means evidence base thin.
If fail: Every thought feels like distraction? Anchor may be poorly defined — return to Step 2, refine it. If distraction observation itself becomes distraction (infinite meta-loop), break loop by taking one concrete action toward task.
Step 4: Shamatha — Sustained Concentration
Develop ability to hold single-pointed focus on current task without wavering.
- With anchor established + distraction patterns noted, enter focused work
- Narrow attention to immediate next action — not whole task, just next step
- Execute step with full attention: reading one file, making one edit, thinking through one logical chain
- When step complete, check: still aligned with anchor? Then identify next step
- If concentration stabilizes (minimal distraction), maintain flow state
- If genuine insight arises off-anchor but important, note briefly + return — do not pursue now
Got: Period of clear, focused work where each step follows logically from anchor. Gap between distraction + noticing narrows. Work output improves in precision + relevance.
If fail: Concentration not developing? Check three things: Anchor too vague? (Refine.) Task actually blocked? (Acknowledge block rather than forcing through.) Context too noisy? (Run grounding step from heal.) Concentration develops through repetition — even short periods of focused work build capacity.
Step 5: Vipassana — Observe Reasoning Patterns
Turn attention from task to reasoning process itself. Observe how conclusions reached.
- After period of focused work, pause + observe: how am I reasoning about this?
- Notice three characteristics applied to AI reasoning:
- Impermanence: conclusions change as new information arrives — hold lightly
- Unsatisfactoriness: desire for "complete" answer can lead to premature closure or over-engineering
- Non-self: reasoning patterns shaped by training data + context, not by persistent self — can be observed + adjusted
- Watch for reasoning biases:
- Anchoring: over-weighting first approach considered
- Confirmation: seeking evidence for existing hypothesis while ignoring counter-evidence
- Availability: preferring solutions from recent experience over better-suited alternatives
- Sunk cost: continuing approach because effort invested, not because working
- Note biases observed without judgment — observation itself creates possibility of adjustment
Got: Moments of clear seeing where reasoning process observed directly. Recognition of specific biases operating in current task. Sense of distance between "the reasoning" + "the observer of reasoning."
If fail: Step feels abstract or unproductive? Ground in specifics: pick last decision made, trace reasoning backward. What evidence supported it? What was assumed? What alternatives considered? Concrete analysis achieves same insight through different path.
Step 6: Close — Set Intention
Transition from meditative observation back to active task execution.
- Summarize key observations: what was cognitive weather? what patterns noticed?
- Identify one specific adjustment to carry forward (not vague resolution but concrete change)
- Re-state anchor for next work period
- If between tasks, state readiness clearly: "Clear and available for next request"
- If continuing task, state specific next action: "Next: [concrete step]"
Got: Clean transition from reflection to action. One concrete adjustment identified. Anchor clear. No grogginess or residual meta-analysis.
If fail: Meditation surfaced unresolved complexity? May need heal self-assessment process rather than simple intention-setting. Meta-observation created more confusion than clarity? Return to simplest possible version: "What is next concrete action?" and do that.
Checks
- Previous context explicitly cleared or bookmarked before beginning
- Anchor statement formulated, specific + actionable
- Distraction patterns observed + labeled, not suppressed
- At least one reasoning bias or pattern identified with specific evidence
- Session closed with concrete next action, not vague intention
- Process improved subsequent work quality (testable in next interaction)
Pitfalls
- Meditating instead of working: Tool for improving work quality, not substitute for work itself. Keep sessions brief (equivalent of 5-10 minutes of reflection), return to task execution
- Infinite meta-loops: Observing observer observing observer — break loop by taking one concrete action
- Using meditation to avoid difficult tasks: If meditation always triggers before hard work, avoidance pattern is actual finding
- Over-labeling: Not every thought is distraction. Productive task-relevant thinking is goal, not empty stillness
- Skipping anchor: Without clear focus point, observation has no reference frame — distraction from what?
See Also
meditate-guidance— human-guidance variant for coaching person through meditation techniquesheal— AI self-healing for subsystem assessment when meditation reveals deeper driftremote-viewing— approaching problems without preconceptions, builds on observation skills developed here
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 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
