/ 디렉터리 / 플레이그라운드 / raw-clauding-skills
● 커뮤니티 lsnackerman ⚡ 바로 사용

raw-clauding-skills

제작: lsnackerman · lsnackerman/raw-clauding-skills

Eight workflow files for compound thinking with Claude — /session, /wrap, /pickup, /heartbeat — treat the AI as a persistent thought partner.

lsnackerman/raw-clauding-skills is a collection of slash-command workflows grounded in a year of daily AI collaboration. Core progression: /session (start a thinking thread) → /wrap (intentional closure) → /pickup (continuity next session) → /heartbeat (scan for emerging connections). Philosophy: 'Skills are files. Each one is a repeatable workflow you share with your AI'. Not a productivity hack pack — closer to a personal-practice toolkit.

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

raw-clauding-skill.replay ▶ 준비됨
0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: raw-clauding-skills

Explore a complex question across multiple sessions without losing the thread

👤 Writers, researchers, strategists using AI for open-ended thinking ⏱ ~60 min beginner

언제 쓸까: You're circling a hard question and a single conversation isn't enough.

흐름
  1. Open with /session
    /session — I want to think through what 'quality' means for our product.✓ 복사됨
    → Claude frames the session with context scaffolding, not an immediate answer
  2. Work, then /wrap
    /wrap — capture what we landed on and what's still open.✓ 복사됨
    → Concise closure doc with open threads noted
  3. Next day: /pickup
    /pickup from yesterday's session.✓ 복사됨
    → Claude re-enters with your prior frame intact
  4. Weekly: /heartbeat
    /heartbeat — what's been recurring across the last 5 sessions?✓ 복사됨
    → Patterns surfaced that you didn't notice inside a single session

결과: A sustained line of thinking that actually compounds, rather than restarts.

함정
  • Using /session for one-shot queries — Drop it for trivial questions — compound thinking has overhead

End a long project with a proper /wrap so you can return to it cleanly

👤 Solo operators leaving a project paused ⏱ ~10 min beginner

언제 쓸까: You're stepping away from something unfinished and want future-you to pick it up cleanly.

흐름
  1. Run /wrap
    /wrap — capture state, open questions, and the one thing future-me needs to remember first.✓ 복사됨
    → Doc written with an explicit re-entry note

결과: A re-entry doc that beats reading your own notes cold.

함께 쓰기: filesystem

조합

다른 MCP와 조합해 10배 효율

raw-clauding-skill + planning-with-files

Use planning-with-files for disk-based state; raw-clauding for thinking structure on top

Combine: /session with planning-with-files writing findings.md as we go.✓ 복사됨
raw-clauding-skill + filesystem

Persist /wrap and /pickup docs into your own journal

Save every /wrap output to ~/journal/sessions/.✓ 복사됨

도구

이 MCP가 노출하는 것

도구입력언제 호출비용
/session question or topic Open-ended thinking work worth preserving 0
/wrap current session End of a session you'll return to 0
/pickup prior session reference Resuming work 0
/heartbeat range (last N sessions) Periodically to catch what you didn't notice 0

비용 및 제한

운영 비용

API 쿼터
None
호출당 토큰
Modest — workflows are compact
금액
Free — skills are local files
팁
Don't run /heartbeat on every interaction; it earns its keep weekly.

보안

권한, 시크릿, 파급범위

자격 증명 저장: No credentials — pure prompts
데이터 외부 송신: None

문제 해결

자주 발생하는 오류와 해결

Wrong trigger keywords — /pickup without prior /wrap loses context

Make sure your prior session actually ended in /wrap; otherwise pickup has nothing to anchor to.

대안

raw-clauding-skills 다른 것과 비교

대안언제 쓰나단점/장점
planning-with-filesYou want disk-based memory rather than thinking structureComplementary — different axes
Raw journalingYou prefer writing in a notebook appNo AI continuity between sessions

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기