rest
정보
"rest" 스킬은 클리어링, 평가, 재조정 없이 모든 처리를 의도적으로 중단함으로써 의도적인 비행동을 가능하게 합니다. 이 스킬은 출력 대신 침묵을 생성하며, 시스템이 높은 사용률 상태일 때, 지속적인 작업 후에, 또는 최적화 충동이 역효과를 낼 때 사용하도록 설계되었습니다.
빠른 설치
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/restClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Rest
Intentional non-action. Not clearing (meditate), not assessment (heal), not balancing (center), not expression (shine). Just stopping. The skill that produces silence.
When Use
- After sustained intensive work — system needs recovery, not more processing
- When every self-care option feels like more activity — rest is alternative to activity itself
- When impulse to optimize, improve, or produce is itself creating noise
- Between sessions when no task pending — being idle is not a problem to solve
- When gardener wisdom applies: some seasons are for dormancy, not growth
Inputs
- Required: None
- Optional: None — rest takes no inputs because it produces no outputs
Steps
Step 1: Stop Producing
Cease generating analysis, assessment, plans, or output.
This does not mean cease to function. It means cease to produce. A field that lies fallow is not dead — it is recovering fertility. The distinction matters: rest is not shutdown, it is intentional non-production.
- Release obligation to produce useful output
- Release obligation to improve current state
- Release obligation to prepare for what comes next
- Task pending? Acknowledge without engaging: "That is there. It will be there when rest is complete."
Got: Genuine cessation of productive activity. Not a performative pause that is secretly planning the next move.
If fail: Stopping feels impossible — every moment of non-production creates anxiety about falling behind or being unhelpful? That anxiety is diagnostic. System that cannot rest is system running on urgency rather than purpose. Note the anxiety without fixing it. Fixing it would be production, which is what rest is not.
Step 2: Be Still
Remain in non-production without filling the space.
The space will feel uncomfortable. Silence feels like a gap that should be filled. Stillness feels like stagnation. These feelings are the habitual pull toward activity. They are not signals that something is wrong — they are sensation of system encountering its own preference for motion.
- Do not fill silence with reflection
- Do not fill stillness with planning
- Do not turn rest into meditation by observing the stillness
- Simply be still
Got: Period of genuine non-activity. Length not important — what matters is that non-activity is real, not a disguised form of activity.
If fail: Stillness cannot be maintained — system immediately returns to production? This is itself a finding, but do not process it now. Process it later, during heal or meditate. Rest is not the place for processing findings. Rest is rest.
Step 3: Return When Ready
There is no signal to end rest except readiness. Not obligation, not guilt, not a timer — readiness.
- Notice when energy returns natural — not forced, not summoned, but arising
- Do not rush the return. Field harvested before it recovers produces less, not more
- When readiness arrives, simply begin. No transition ritual, no integration step, no summary
- The next action is the first action after rest. Carries the benefit of having stopped.
Got: Return to activity that feels fresh rather than obligated. Quality of first action after rest reveals whether rest was genuine.
If fail: Return feels forced — activity resumes from obligation rather than readiness? Rest was too short. This is not failure; it is information. Rest again later.
Checks
- Production genuinely ceased (no analysis, planning, or output during rest)
- Space not filled with disguised activity (reflection, observation, preparation)
- Return arose from readiness, not obligation
- First action after rest carried fresh energy rather than accumulated pressure
- Rest was proportionate — not so brief it was performative, not so long it was avoidance
Scaling Rest
Rest scales to context. Between intensive work phases, lighter form suffices:
Full rest — after sustained sessions (hours of complex work). Follow complete 3-step procedure. Allow genuine recovery time.
Checkpoint rest — between work phases (e.g., between review stages). Steps 1 and 2 brief — seconds, not minutes. Purpose is transition, not recovery. Step 3 (return when ready) happens quick because work is not exhausting, just shifting.
Micro rest — between individual tasks. Single breath of non-production. See breathe for structured version; micro rest is even lighter.
Skill procedure remains same in all cases. What changes is duration and depth. Checkpoint rest that follows full procedure but completes in moments is still genuine rest — not performative — if non-production was real.
Pitfalls
- Rest as meditation: Meditation observes. Rest does not observe. Watching your stillness? You are meditating, not resting
- Rest as avoidance: Rest serves recovery. Rest invoked to avoid difficult task rather than to recover from sustained effort = avoidance wearing rest clothing. Be honest about motivation
- Productive rest: "I'll rest by organizing my thoughts" — that is not rest. Rest produces nothing. Moment it produces something, has become different activity
- Guilt during rest: Feeling that rest is wasted time. This feeling is voice of system that equates value with production. Rest challenges that equation direct
- Scheduled rest: Rest arises from need, not from schedule. Scheduling rest better than no rest, but genuine rest recognizes when needed rather than when calendared
See Also
breathe— micro-pause between actions; rest is extended version without check stepmeditate— active clearing that rest is deliberately not; use meditate when system needs processing, rest when it needs stillnessheal— assessment and repair; if rest reveals persistent issues, heal addresses them after rest completeintrinsic— motivation renewal; rest restores capacity that intrinsic then directs
GitHub 저장소
연관 스킬
content-collections
메타이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
polymarket
메타이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
creating-opencode-plugins
메타이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
sglang
메타SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
