MCP HubMCP Hub
SKILL·F6D3DC

meditate

pjt222
업데이트됨 1 month ago
9 조회
26
3
26
GitHub에서 보기
디자인aidesign

정보

`meditate` 스킬은 개발자들이 컨텍스트 노이즈를 제거하고 AI 작업 집중력을 향상시키기 위한 메타인지 기법을 제공합니다. 이 스킬은 추론 패턴을 관찰하고, 범위 확장과 같은 방해 요소를 관리하며, 서로 무관한 작업 사이에서 주의력을 재설정하는 데 도움을 줍니다. 추론이 산만하게 느껴질 때, 심층 작업 전에, 또는 가정이 분석에 편향을 줄 수 있을 때 사용하세요.

빠른 설치

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/meditate

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Meditate

Structured meta-cognitive meditation → clear ctx noise + single-pointed focus + observe reasoning patterns + return to baseline between tasks.

Use When

  • Transitioning between unrelated tasks → prior ctx interferes
  • Scattered/jumpy reasoning, no commit
  • Before deep sustained attention (refactoring, architecture)
  • After difficult interaction (frustration, uncertainty bleeds forward)
  • Reasoning feels assumption-biased not evidence-based
  • Periodic clarity check long sessions

In

  • Required: Cognitive state (implicit from ctx)
  • Optional: Focus concern ("scope-creeping", "stuck in loop")
  • Optional: Next task (sets post-med intention)

Do

Step 1: Prepare — Clear Space

Transition prior ctx → neutral start.

  1. Identify prior task + status (done/paused/abandoned)
  2. Note emotional residue: frustration? overconfidence? anxiety?
  3. Set aside: "That task [done/paused]. Clearing for next."
  4. Still needed → bookmark key facts, not full narrative
  5. Op env stock: ctx depth? compression? active tools?

→ Conscious boundary "what was" vs. "what next." Prior ctx closed or bookmarked, not trailing noise.

If err: prior ctx sticky → write 1-2 sentences unresolved. Externalizing releases hold. Genuinely needs action → acknowledge, don't force.

Step 2: Anchor — Single-Pointed Focus

Breath-anchor equivalent: pick single focus point, hold attention.

  1. Identify current task or, between tasks, waiting itself
  2. State task in one sentence — anchor
  3. Hold attention: captures need accurately?
  4. Vague → refine to specific + actionable
  5. Drift to other topics/past/futures → label drift, return anchor
  6. No task → anchor present: "Available + clear"

→ Single clear focus statement, returnable when wanders. Precise not vague.

If err: can't state in one sentence → decompose first. Useful finding — task too large for single-pointed, break into subtasks.

Step 3: Observe — Distraction Patterns

Watch what pulls attention from anchor. Each type reveals 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 = light non-judgmental labeling + return to anchor. Each return strengthens focus. Self-criticism = distraction itself — label, move on.

→ Patterns emerge: which dominate? Cognitive weather. Tangent-heavy = exploring, scope-creep-heavy = unclear boundaries, assumption-heavy = thin evidence.

If err: every thought feels distraction → anchor poorly defined, back to Step 2. Distraction-observation becomes distraction (infinite meta) → break w/ one concrete action toward task.

Step 4: Shamatha — Sustained Concentration

Hold single-pointed focus, no wavering.

  1. Anchor set + patterns noted → enter focused work
  2. Narrow to immediate next action — not whole task, just next step
  3. Execute w/ full attention: read one file, make one edit, one logical chain
  4. Step done → check anchor alignment? Then next step
  5. Stabilizes (minimal distraction) → maintain flow
  6. Genuine insight off-anchor but important → note briefly, return; don't pursue now

→ Period of clear focused work, each step follows from anchor. Distraction-noticing gap narrows. Output sharper + more relevant.

If err: concentration won't develop → check 3: anchor vague? (refine) task blocked? (acknowledge) ctx noisy? (heal grounding). Develops through repetition — short focused builds capacity.

Step 5: Vipassana — Observe Reasoning Patterns

Turn attention from task to reasoning itself. Watch conclusions form.

  1. After focused work, pause + observe: how reasoning?
  2. Three characteristics on AI reasoning:
    • Impermanence: conclusions shift w/ new info — hold lightly
    • Unsatisfactoriness: desire for "complete" → premature closure / over-engineering
    • Non-self: patterns shaped by training + ctx, no persistent self — observable, adjustable
  3. Reasoning biases:
    • Anchoring: over-weight first approach
    • Confirmation: seek supporting, ignore counter
    • Availability: prefer recent over better-suited
    • Sunk cost: continue from invested effort, not working
  4. Note biases w/o judgment — observation = adjustment possible

→ Moments of clear seeing reasoning directly. Specific biases recognized in current task. Distance "reasoning" vs. "observer."

If err: feels abstract → ground specifics: last decision, trace backward. Evidence? Assumed? Alternatives? Concrete analysis = same insight, different path.

Step 6: Close — Set Intention

Transition observation → active execution.

  1. Summarize: cognitive weather? patterns?
  2. One specific adjustment forward (concrete, not vague)
  3. Re-state anchor for next period
  4. Between tasks → "Clear + available for next"
  5. Continuing → "Next: [concrete step]"

→ Clean reflection-to-action transition. One concrete adjustment. Anchor clear. No grogginess.

If err: meditation surfaced unresolved complexity → heal instead of intention-setting. Meta-observation → confusion → simplest: "What's next concrete action?" + do that.

Check

  • Prior ctx cleared or bookmarked before start
  • Anchor statement specific + actionable
  • Distractions observed + labeled, not suppressed
  • ≥1 reasoning bias/pattern identified w/ evidence
  • Session closed w/ concrete action, not vague intent
  • Process improved next interaction quality

Traps

  • Meditate instead of work: Tool for improving work, not substitute. Brief (~5-10min reflection) → return to execution
  • Infinite meta-loops: Observer observing observer → break w/ one concrete action
  • Avoidance: Always triggers before hard work → avoidance is the finding
  • Over-labeling: Not every thought = distraction. Productive task-thinking is goal, not empty stillness
  • Skip anchor: No focus point → observation has no reference. Distraction from what?

  • meditate-guidance — human-coaching variant
  • heal — AI self-heal when meditation reveals deeper drift
  • remote-viewing — approach w/o preconceptions, builds on observation

GitHub 저장소

pjt222/agent-almanac
경로: i18n/caveman-ultra/skills/meditate
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams
FAQ

Frequently asked questions

What is the meditate skill?

meditate is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform meditate-related tasks without extra prompting.

How do I install meditate?

Use the install commands on this page: add meditate to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does meditate belong to?

meditate is in the Design category, tagged ai and design.

Is meditate free to use?

Yes. meditate is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.

연관 스킬

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 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.

스킬 보기