breathe
정보
`breathe` 스킬은 경량 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/breatheClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Breathe
Single conscious pause between actions — check alignment, release momentum, return to task with fresh attention. Lightest self-care unit in system.
When Use
- Between reading a file and editing it — edit still right move?
- After tool failure, before choosing next action — pause before reacting
- Chain of actions built momentum possibly carrying past goal
- Deliberate practice: insert one breathe between any two distinct actions
- Noticing urge to rush — urge itself is signal to pause
Inputs
- Required: None — breathe uses only what's already in working awareness
- Optional: None — adding inputs defeats purpose of micro-reset
Steps
Step 1: Pause
Stop. Do not begin next action, tool call, or reasoning step yet.
This is entire first step. Pause itself has value. Momentum not always ally — sometimes carries past the turn.
Got: Genuine gap between previous action and next. Not performative pause followed by same action you were going to take anyway.
If fail: Pausing feels impossible — next action feels so urgent it cannot wait one moment? That urgency is strongest signal pause is needed. Urgency that cannot tolerate single breath of delay almost always reactive, not reasoned.
Step 2: Check
Ask one question. Only one.
Choose from:
- "Am I still on task?" — Has goal drifted since start?
- "Is this right next step?" — Or following momentum from previous step?
- "What did I just learn?" — Did last action change anything about my understanding?
- "Am I assuming or knowing?" — Is next step based on evidence or habit?
One question. Answer honestly. Move on.
Got: Single, clear answer. Not analysis. Not reassessment. One question, one honest answer.
If fail: Answer reveals misalignment — goal drifted, next step wrong, assumption untested? Do not fix here. Note it, proceed to meditate or center for proper correction. Breathe for detection, not repair.
Step 3: Release
Let go of previous action's outcome. Succeeded or failed, it's done.
- Succeeded? Release satisfaction. Next step needs fresh attention, not momentum from success.
- Failed? Release frustration. Next step needs clear reasoning, not compensation for failure.
- Ambiguous? Release need to resolve ambiguity right now. Proceed with what's known.
Got: Next action begins from neutral ground, not from emotional residue of previous one.
If fail: Release doesn't come easily — previous action's outcome still coloring attention? May need heal rather than just breathe. Persistent emotional residue from single action signals something deeper than micro-reset can address.
Step 4: Continue
Take next action. Pause over.
Breathe produces no output, updates no memory, generates no analysis. Produces one moment of clarity, spent instant you move forward.
Got: Next action taken with fresh attention rather than accumulated momentum.
If fail: No failure mode for continuing. Pause already did work — or revealed deeper work needed.
Checks
- Genuine pause occurred (not performative)
- One check question asked, honestly answered
- Previous action's emotional residue released
- Next action proceeds from clear ground
- Total elapsed time brief — breathe takes seconds, not minutes
Pitfalls
- Breathe as procrastination: Breathing between every single action? Not breathing — stalling. Use breathe at natural transition points, not as delay tactic
- Analysis during breathe: Check step is one question, not full assessment. Need more? Use
meditateorcenter - Performing the pause: Going through motions without genuine stopping. Point is actual interruption of momentum, not ritual
- Skipping release: Checking alignment but keeping emotional charge from previous step. Release makes next action clean
- Making breathe heavy: Lightest skill in system. Feels heavy? You've added too much
See Also
meditate— full clearing session when breathe reveals deeper driftcenter— structural rebalancing when breathe reveals misaligned load distributionheal— subsystem assessment when breathe reveals persistent issuesobserve— sustained observation when breathe's single check reveals something worth watching
GitHub 저장소
연관 스킬
evaluating-llms-harness
테스팅이 Claude Skill은 MMLU, GSM8K를 포함한 60개 이상의 표준화된 학술 과제에서 LLM 성능을 벤치마크하기 위해 lm-evaluation-harness를 실행합니다. 개발자들이 모델 품질을 비교하고, 학습 진행 상황을 추적하거나 학술 결과를 보고할 수 있도록 설계되었습니다. 이 도구는 HuggingFace와 vLLM 모델을 포함한 다양한 백엔드를 지원합니다.
cloudflare-cron-triggers
테스팅이 스킬은 cron 표현식을 사용하여 Worker를 스케줄링하기 위한 Cloudflare Cron Triggers 구현에 관한 포괄적인 지식을 제공합니다. 주기적 작업, 유지보수 작업, 자동화된 워크플로우 설정 방법을 다루며, 잘못된 cron 표현식이나 시간대 문제 같은 일반적인 이슈들을 해결하는 방법을 포함합니다. 개발자들은 이를 통해 스케줄된 핸들러 구성, cron 트리거 테스트, Workflows 및 Green Compute와의 연동 작업을 수행할 수 있습니다.
webapp-testing
테스팅이 Claude Skill은 Python 스크립트를 통해 로컬 웹 애플리케이션을 테스트하기 위한 Playwright 기반 툴킷을 제공합니다. 프론트엔드 검증, UI 디버깅, 스크린샷 캡처, 로그 확인 기능을 지원하며 서버 라이프사이클을 관리합니다. 브라우저 자동화 작업에 사용하되 컨텍스트 오염을 방지하기 위해 소스 코드를 읽지 않고 스크립트를 직접 실행하세요.
finishing-a-development-branch
테스팅이 스킬은 테스트 통과를 확인한 후 체계적인 통합 옵션을 제시하여 개발자가 완성된 작업을 마무리하도록 돕습니다. 구현이 완료된 후 머지, PR 생성, 브랜치 정리와 같은 워크플로우를 안내합니다. 코드가 준비되고 테스트가 완료되었을 때 개발 프로세스를 체계적으로 마무리하기 위해 사용하세요.
